@netdivermag good to hear from you! https://indieweb.org/ (@indiewebcamp) has kept the independent torch lit. We remember independentsday(.)org: https://indieweb.org/Independents_Day Let's chat https://chat.indieweb.org/ via Slack, Matrix, or IRC rather than this silo

About three weeks ago I got auto-linked hashtags working on my posts. The biggest challenge was picking a tag space to link my hashtags. The second biggest challenge was figuring out how to get my linked hashtags to work when my posts were federated into Mastodon instances, and have them rewrite those links into instance-local tag page links. We need a term for such locally rewritten linked hashtags, perhaps “federated hashtags”. While typical personal sites link a hashtag to a tag page that only displays personal posts, I wanted to link to something more like a tag aggregation page that also displayed similar posts from others. The tag pages on Mastodon instances do a good job of this, showing tagged posts from any user on that instance, and tagged posts from any user followed by any user on that instance. I reviewed my hashtags since the start of 2023, checked their pages on indieweb.social and found that the posts displayed were all on topic, and surprisingly free of tag spam (perhaps for now). I chose https://indieweb.social/tags/ for my tag space (which is a 404 if you click it, where it really should display a tags page listing popular or recent tags or a tag cloud). Combining a hashtag like #100DaysOfIndieWeb with a tag space produces a link to a tag page like: https://indieweb.social/tags/100DaysOfIndieWeb. The other interesting thing about hashtag links is how they’re rewritten when a post is displayed on another Mastodon instance, to link to the tag page local to that instance. This linked-hashtag-portability is underspecified unfortunately (it could probably use its own portable markup specification, or at least a best practice for h-entry publishing). How it works in Mastodon is non-obvious enough that there’s a 4+ year old Bridgy Fed issue on the subject! * https://github.com/snarfed/bridgy-fed/issues/45 With a bunch of research and experiment contributions from several folks in the issue, @snarfed.org (@schnarfed) did eventually figure out how to get Bridgy Fed to federate hashtags in posts into Mastodon instances so they would rewrite hashtag links into instance-local hashtag pages: * https://github.com/snarfed/bridgy-fed/issues/45#issuecomment-1468962400 Thus even though I’m using the indieweb.social tag space on the hashtag links in my original post, if you are reading this post on Mastodon, you should see a hashtag like #IndieWeb link to your local instance’s tag page for IndieWeb, and my post should show up on that page. From testing a few other instances tag pages, this is now working, e.g. these tag pages: * https://indieweb.social/tags/100DaysofIndieWeb (as expected) * https://xoxo.zone/tags/100DaysOfIndieWeb * https://mozilla.social/tags/100DaysofIndieWeb display the #MozFest post^1 I published right after implementing linked hashtags (and any subsequent 100DaysofIndieWeb posts). I did go back and send Webmentions to BridgyFed to send ActivityPub updates for all my past #100DaysofIndieWeb posts, however only a few of them showed up in those tag pages. It’s unclear why a few did and most didn’t, or why there are inconsistencies across instances. More to explore and debug. Federated hashtags definitely need their own specification, because currently they barely interoperate when published, and even then require Mastodon-implementation-specific knowledge to function. The good news is that several of us now have linked hashtags on our personal sites display and link as expected when our posts are federated across Mastodon instances, using a variety of different pieces of software to make it all work. This is day 36 of #100DaysOfIndieWeb #100Days ← Day 35: https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb → 🔮 Glossary h-entry https://microformats.org/wiki/h-entry hashtag https://indieweb.org/hashtags tag aggregation https://indieweb.org/tag_aggregation tag page https://indieweb.org/tag_page tags page https://indieweb.org/tags_page References ^1 https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb

Warn if event or Etherpad link already archived

itter https://twitter.com/softwarejameson/status/1643660118201106433

Watching #MozFest session Dialogues & Debates: Making the Fediverse^1 and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance^2, starting with limited sign-ups. I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos. There are many #Mozillians with #fediverse addresses you can follow: * https://wiki.mozilla.org/Mastodon Several of these folks also have their own #IndieWeb sites. It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site. One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before migrating to either self-hosting Mastodon (or an easier to run alternative like microblog.pub^3, not to be confused with micro.blog^4), or ideally directly using their own site, blog etc. to connect to the fediverse^5. Do you have an @-@ address and want to use your own site instead? If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place. Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/dev This is day 35 of #100DaysOfIndieWeb #100Days ← Day 34: https://tantek.com/2023/072/t1/blog-as-if-ai-trained-posts → 🔮 ^1 https://schedule.mozillafestival.org/session/UEEGYL-1 ^2 https://mozilla.social/ ^3 https://indieweb.org/microblog.pub ^4 https://indieweb.org/micro.blog ^5 https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb

https://github.com/olfek https://github.com/cavac neither of your comments provided any new technical information on this specification and are out of scope for this repo. If you want to vent, please use your own blog to do so. Please re-read the CONTRIBUTING guide https://github.com/mozilla/standards-positions/blob/main/CONTRIBUTING.md before making any further comments on any issue in the repo. All of the comments made on this issue in this year were out of scope, and none of them provided any new technical information about the specification so I am locking this issue accordingly.

Blog as if there’s an #AI being trained^1 to be you based on your blog posts. And what if it was trained on your Universal Outbox^2? #IndieWeb #OpenAI #ChatGPT This is day 34 of #100DaysOfIndieWeb #100Days ← Day 33: https://tantek.com/2023/051/t1/five-years-ago-w3c-social-web → 🔮 ^1 https://indieweb.org/OpenAI#IndieWeb_Examples ^2 https://tantek.com/2023/044/t1/unified-sent-box-universal-outbox