Category: IndieWeb
- Session 1: Mission briefing: 19 January 2023 at 16:00 GMT (Watch Live)
- Session 2: Verifying your progress: 23 February 2023 at 16:00 GMT (Watch Live)
- Session 3: 30 days until self-destruct: 23 March 2023 at 16:00 GMT (Watch Live)
Sign up on their server today to try things out: https://thismastodonwillexplo.de/
#MissionMastodon @reclaimhosting@reclaim.rocks @jimgroom@social.ds106.us @marendeepwell@social.ds106.us
A new year brings new calls for a return to personal blogging as an antidote to the toxic and extractive systems of social media.
Full RSS feeds for Mastodon Instances with OpenRSS
They can be particularly useful for small instances (aka communities) with slow posting velocity—you know, that instance you wanted to join for the local camaraderie, but having/maintaining/maintaining yet another Mastodon account wasn’t worth it, the hashtag discovery wasn’t going to cut it, and trying to follow all the people in the local community individually is irksome. Well OpenRSS.org might be able to cover you.
As an example, I wanted to follow what’s happening at toolsforthought.rocks/public/local so I added that slightly trimmed local timeline URL onto https://openrss.org/ and put it into my feed reader. After they wire things together for you a bit (presuming it’s one they’ve not seen/done before), voilà your RSS feed just starts working! Now I’m following ToolsForThought at: https://openrss.org/toolsforthought.rocks/public/local.
Since my personal website works with Mastodon and the Fediverse, this last part of more easily following groups of people in my social reader helps me complete the circle of reading, following, and responding in a more IndieWeb way. (Of course I wish that Mastodon 4.0 had not gone full js;dr, which would have allowed following them using Microformats mark up with much better fidelity. le sigh)
Details: https://indieweb.org/Template:slideshow
Example: https://indieweb.org/2018/Baltimore/Building_Blocks
Individual pages could also likely be done via transclusion thereby giving one the ability to create re-orderable versions.

#HappyNewwwYear #IndieWeb
Since you have other Fediverse accounts you’re using, you might be able to follow the same general pattern I’d documented with Twitter for threading comments between my site and Twitter: https://boffosocko.com/2018/07/02/threaded-conversations-between-wordpress-and-twitter/
Generally, you’d post on your site where it’s seen in the Fediverse via the ActivityPub plugin and/or optionally boosted by your native Mastodon account. Replies to your post (on Mastodon) show up on your site as comments and you reply to them there in your site’s comments section. Then you manually copy/paste the text of your reply from your website into your native Mastodon account and include the comment/reply permalink in that reply. If you’ve got Webmention set up with Brid.gy for Mastodon, replies to your replies on Mastodon should then make their way back to the proper threaded spot in your website’s comments section.
An example of this at work can be seen on my earlier mistake:
- The original post on my site;
- My own reply on my site;
- My manually copied reply on Mastodon;
- My Mastodon reply shows up on my site via Brid.gy;
- A like of that Mastodon reply shows up on my site (also courtesy of Brid.gy via Webmention).
Related, I’ve been playing around with mirroring my WP site as an instance with the ActivityPub plugin and have boosted posts with my more broadly followed mastodon.social account the same way you mentioned that you were doing with yours. Somehow I’m anecdotally finding that I get more responses/reactions with native posts that with these boosts. I’m curious what your experience has been with this strategy so far? I’m still just starting my experimentation here, but I do like the fact that I’m able to include richer presentation of wrapped links in my WordPress native posts which are seen in the Fediverse while Mastodon seems to strip them out or not allow them (see an example of this in the post above this reply).
I suspect that some version of this option I’ve done before will work, though I haven’t tried updating it recently: https://boffosocko.com/2018/07/02/threaded-conversations-between-wordpress-and-twitter/
Our friend @jimgroom@social.ds106.us has recently written up some details that get around the t.co shortener problems: https://bavatuesdays.com/archiving-twitter/
I’ve also heard that @darius@friend.camp is working on something for a public release soon: https://friend.camp/@darius/109521972924049369. He may still be looking for beta testers if you’re interested.
I’ve got lots of friends in a supportive online community who can help: https://indieweb.org