#bridgyfed — Public Fediverse posts

I have now achieved full loop where I can publish blog posts and podcast episodes at will, have them build via the Forgejo action and push to Mastodon via the same avenue. It occurs me that I have restored full POSSE to this blog.

There was a time maybe 15 or more years ago when that was a big thing. At the time, my online presence was spread amongst Twitter, Facebook, FriendFeed et al. At some point, I thought "Fuck all of them. My own stuff should be at the center of this." That was around the time I leard the concept of POSSE - Publish on your Own Site, Syndicate Everywhere.

Various mechanisms achieved that syndication. With the late lamented FriendFeed (the best of them all) it was built in. There were various IFTTT type rules that did the posting at times. I also had some WordPress plugin that I paid for until the point it became so ineffective that it hurt my heart to give them money.

Today it is really just the fediverse and here. The only other social media I touch with a ten foot pole is LinkedIn and that only seldom and only grudgingly. I certainly don't use it enough that I care too much about an automatic solution. I can copy and paste in the rare instances where I care to post there.

POSSE is less of a political statement today than it was in the Web 2.0 era. Considering my Mastodon server runs in a docker container under my full control it is less of a freedom fight and more a matter of convenience.

I still have an interest in the political and technical ramifications of POSSE so I'm fine reclaiming that as applicable to this blog. For someone who owns their own server, I suppose that could be the OS in POSSE from which everything syndicates.

At the very least, this new posting infrastructure has relit a long cold fireplace of interest in blogging and freeform writing. That seems like a flame worth fanning.

I have now achieved full loop where I can publish blog posts and podcast episodes at will, have them build via the Forgejo action and push to Mastodon via the same avenue. It occurs me that I have restored full POSSE to this blog.

There was a time maybe 15 or more years ago when that was a big thing. At the time, my online presence was spread amongst Twitter, Facebook, FriendFeed et al. At some point, I thought "Fuck all of them. My own stuff should be at the center of this." That was around the time I leard the concept of POSSE - Publish on your Own Site, Syndicate Everywhere.

Various mechanisms achieved that syndication. With the late lamented FriendFeed (the best of them all) it was built in. There were various IFTTT type rules that did the posting at times. I also had some WordPress plugin that I paid for until the point it became so ineffective that it hurt my heart to give them money.

Today it is really just the fediverse and here. The only other social media I touch with a ten foot pole is LinkedIn and that only seldom and only grudgingly. I certainly don't use it enough that I care too much about an automatic solution. I can copy and paste in the rare instances where I care to post there.

POSSE is less of a political statement today than it was in the Web 2.0 era. Considering my Mastodon server runs in a docker container under my full control it is less of a freedom fight and more a matter of convenience.

I still have an interest in the political and technical ramifications of POSSE so I'm fine reclaiming that as applicable to this blog. For someone who owns their own server, I suppose that could be the OS in POSSE from which everything syndicates.

At the very least, this new posting infrastructure has relit a long cold fireplace of interest in blogging and freeform writing. That seems like a flame worth fanning.

I've been struggling with the timestamps as these posts appear in the Fediverse, mainly Mastodon as pushed by Bridgy Fed. I've been fiddling with the time as it appears in these individual post pages. Nothing I did seemed to affect it.

In frustration I followed a chain of links that ended me up at the Microformats.org page about dates and times. Turns out that all the date and time changes I was making on the visible page had nothing to do with it. I do have the visible display wrapped in an HTML <time> tag. That tag has a datetime field, and in that I had only the date and no time whatsoever.

From Microformats:

if the element is a del, ins, or time element, then use the element's datetime attribute value if present, otherwise its inner-text.

So I guess that is that. I've been frustrated with Bridgy Fed but turns out as it so often is, the problem was me.

I've been struggling with the timestamps as these posts appear in the Fediverse, mainly Mastodon as pushed by Bridgy Fed. I've been fiddling with the time as it appears in these individual post pages. Nothing I did seemed to affect it.

In frustration I followed a chain of links that ended me up at the Microformats.org page about dates and times. Turns out that all the date and time changes I was making on the visible page had nothing to do with it. I do have the visible display wrapped in an HTML <time> tag. That tag has a datetime field, and in that I had only the date and no time whatsoever.

From Microformats:

if the element is a del, ins, or time element, then use the element's datetime attribute value if present, otherwise its inner-text.

So I guess that is that. I've been frustrated with Bridgy Fed but turns out as it so often is, the problem was me.

I've been struggling with the timestamps as these posts appear in the Fediverse, mainly Mastodon as pushed by Bridgy Fed. I've been fiddling with the time as it appears in these individual post pages. Nothing I did seemed to affect it.

In frustration I followed a chain of links that ended me up at the Microformats.org page about dates and times. Turns out that all the date and time changes I was making on the visible page had nothing to do with it. I do have the visible display wrapped in an HTML <time> tag. That tag has a datetime field, and in that I had only the date and no time whatsoever.

From Microformats:

if the element is a del, ins, or time element, then use the element's datetime attribute value if present, otherwise its inner-text.

So I guess that is that. I've been frustrated with Bridgy Fed but turns out as it so often is, the problem was me.

I've been struggling with the timestamps as these posts appear in the Fediverse, mainly Mastodon as pushed by Bridgy Fed. I've been fiddling with the time as it appears in these individual post pages. Nothing I did seemed to affect it.

In frustration I followed a chain of links that ended me up at the Microformats.org page about dates and times. Turns out that all the date and time changes I was making on the visible page had nothing to do with it. I do have the visible display wrapped in an HTML <time> tag. That tag has a datetime field, and in that I had only the date and no time whatsoever.

From Microformats:

if the element is a del, ins, or time element, then use the element's datetime attribute value if present, otherwise its inner-text.

So I guess that is that. I've been frustrated with Bridgy Fed but turns out as it so often is, the problem was me.

I've been struggling with the timestamps as these posts appear in the Fediverse, mainly Mastodon as pushed by Bridgy Fed. I've been fiddling with the time as it appears in these individual post pages. Nothing I did seemed to affect it.

In frustration I followed a chain of links that ended me up at the Microformats.org page about dates and times. Turns out that all the date and time changes I was making on the visible page had nothing to do with it. I do have the visible display wrapped in an HTML <time> tag. That tag has a datetime field, and in that I had only the date and no time whatsoever.

From Microformats:

if the element is a del, ins, or time element, then use the element's datetime attribute value if present, otherwise its inner-text.

So I guess that is that. I've been frustrated with Bridgy Fed but turns out as it so often is, the problem was me.

This is a test of my full loop for creating Eleventy blog posts remotely using Forgejo and actions. I am sitting at my kitchen table with my phone and a Bluetooth keyboard pretending I am remote. Fun stuff.

I've long had a node script that creates new Eleventy posts by setting up the date file structure and creating the template Markdown file. The problem when remotely authoring is that I had no good way to run that in a mobile situation. The best I had was to remote in to my laptop which was suboptimal.

I spent my Friday evening hard partying by modifying that script to also take a JSON file for input with the title and date rather than asking for those via the console. Either way, it slugifies the title and you end up with the proper stuff. Now when I'm on the road I can modify the JSON and on commit, an action will run the script and create the blog post.

That's how I created this post. Now I am writing and when I am done this should build, push to the blog and also push to Mastodon via Bridgy Fed. If you see this in either place, then yay I guess. Concept proven.

This is a test of my full loop for creating Eleventy blog posts remotely using Forgejo and actions. I am sitting at my kitchen table with my phone and a Bluetooth keyboard pretending I am remote. Fun stuff.

I've long had a node script that creates new Eleventy posts by setting up the date file structure and creating the template Markdown file. The problem when remotely authoring is that I had no good way to run that in a mobile situation. The best I had was to remote in to my laptop which was suboptimal.

I spent my Friday evening hard partying by modifying that script to also take a JSON file for input with the title and date rather than asking for those via the console. Either way, it slugifies the title and you end up with the proper stuff. Now when I'm on the road I can modify the JSON and on commit, an action will run the script and create the blog post.

That's how I created this post. Now I am writing and when I am done this should build, push to the blog and also push to Mastodon via Bridgy Fed. If you see this in either place, then yay I guess. Concept proven.

This is a test of my full loop for creating Eleventy blog posts remotely using Forgejo and actions. I am sitting at my kitchen table with my phone and a Bluetooth keyboard pretending I am remote. Fun stuff.

I've long had a node script that creates new Eleventy posts by setting up the date file structure and creating the template Markdown file. The problem when remotely authoring is that I had no good way to run that in a mobile situation. The best I had was to remote in to my laptop which was suboptimal.

I spent my Friday evening hard partying by modifying that script to also take a JSON file for input with the title and date rather than asking for those via the console. Either way, it slugifies the title and you end up with the proper stuff. Now when I'm on the road I can modify the JSON and on commit, an action will run the script and create the blog post.

That's how I created this post. Now I am writing and when I am done this should build, push to the blog and also push to Mastodon via Bridgy Fed. If you see this in either place, then yay I guess. Concept proven.

This is a test of my full loop for creating Eleventy blog posts remotely using Forgejo and actions. I am sitting at my kitchen table with my phone and a Bluetooth keyboard pretending I am remote. Fun stuff.

I've long had a node script that creates new Eleventy posts by setting up the date file structure and creating the template Markdown file. The problem when remotely authoring is that I had no good way to run that in a mobile situation. The best I had was to remote in to my laptop which was suboptimal.

I spent my Friday evening hard partying by modifying that script to also take a JSON file for input with the title and date rather than asking for those via the console. Either way, it slugifies the title and you end up with the proper stuff. Now when I'm on the road I can modify the JSON and on commit, an action will run the script and create the blog post.

That's how I created this post. Now I am writing and when I am done this should build, push to the blog and also push to Mastodon via Bridgy Fed. If you see this in either place, then yay I guess. Concept proven.

This is a test of my full loop for creating Eleventy blog posts remotely using Forgejo and actions. I am sitting at my kitchen table with my phone and a Bluetooth keyboard pretending I am remote. Fun stuff.

I've long had a node script that creates new Eleventy posts by setting up the date file structure and creating the template Markdown file. The problem when remotely authoring is that I had no good way to run that in a mobile situation. The best I had was to remote in to my laptop which was suboptimal.

I spent my Friday evening hard partying by modifying that script to also take a JSON file for input with the title and date rather than asking for those via the console. Either way, it slugifies the title and you end up with the proper stuff. Now when I'm on the road I can modify the JSON and on commit, an action will run the script and create the blog post.

That's how I created this post. Now I am writing and when I am done this should build, push to the blog and also push to Mastodon via Bridgy Fed. If you see this in either place, then yay I guess. Concept proven.

I have closed the gap on one of the last pieces of getting my #11ty blog on the #fediverse. I now have the thing building in my self-hosted #Forgejo instance via actions all the way through to rsync'ing the files to my server box. The one missing piece was having to manually ping #BridgyFed to get it to appear.

I gutted out a bash script to extract the URL of the most recent item in my RSS feed and to use that in the curl command to Bridgy Fed. Originally it was going to do this indiscriminately on every build because Eleventy doesn't have a built-in way to know if you built something new. However, thinking a little I realized I can save the RSS from the site right before I push the current build. If the most recent link in the new feed is different than the old feed, hit Bridgy fed with it.

This really matters when I'm scheduling posts ahead (like the podcast episode for earlier today.) When I'm not around to do the manual curl command either I do it much later or forget and do it not at all. This way, it will happen every time there is a new post pushed with or without me being present.

https://evilgeniuschronicles.org/

#eleventy

I have closed the gap on one of the last pieces of getting my #11ty blog on the #fediverse. I now have the thing building in my self-hosted #Forgejo instance via actions all the way through to rsync'ing the files to my server box. The one missing piece was having to manually ping #BridgyFed to get it to appear.

I gutted out a bash script to extract the URL of the most recent item in my RSS feed and to use that in the curl command to Bridgy Fed. Originally it was going to do this indiscriminately on every build because Eleventy doesn't have a built-in way to know if you built something new. However, thinking a little I realized I can save the RSS from the site right before I push the current build. If the most recent link in the new feed is different than the old feed, hit Bridgy fed with it.

This really matters when I'm scheduling posts ahead (like the podcast episode for earlier today.) When I'm not around to do the manual curl command either I do it much later or forget and do it not at all. This way, it will happen every time there is a new post pushed with or without me being present.

https://evilgeniuschronicles.org/

#eleventy

I have closed the gap on one of the last pieces of getting my #11ty blog on the #fediverse. I now have the thing building in my self-hosted #Forgejo instance via actions all the way through to rsync'ing the files to my server box. The one missing piece was having to manually ping #BridgyFed to get it to appear.

I gutted out a bash script to extract the URL of the most recent item in my RSS feed and to use that in the curl command to Bridgy Fed. Originally it was going to do this indiscriminately on every build because Eleventy doesn't have a built-in way to know if you built something new. However, thinking a little I realized I can save the RSS from the site right before I push the current build. If the most recent link in the new feed is different than the old feed, hit Bridgy fed with it.

This really matters when I'm scheduling posts ahead (like the podcast episode for earlier today.) When I'm not around to do the manual curl command either I do it much later or forget and do it not at all. This way, it will happen every time there is a new post pushed with or without me being present.

https://evilgeniuschronicles.org/

#eleventy

I have closed the gap on one of the last pieces of getting my #11ty blog on the #fediverse. I now have the thing building in my self-hosted #Forgejo instance via actions all the way through to rsync'ing the files to my server box. The one missing piece was having to manually ping #BridgyFed to get it to appear.

I gutted out a bash script to extract the URL of the most recent item in my RSS feed and to use that in the curl command to Bridgy Fed. Originally it was going to do this indiscriminately on every build because Eleventy doesn't have a built-in way to know if you built something new. However, thinking a little I realized I can save the RSS from the site right before I push the current build. If the most recent link in the new feed is different than the old feed, hit Bridgy fed with it.

This really matters when I'm scheduling posts ahead (like the podcast episode for earlier today.) When I'm not around to do the manual curl command either I do it much later or forget and do it not at all. This way, it will happen every time there is a new post pushed with or without me being present.

https://evilgeniuschronicles.org/

#eleventy

I have closed the gap on one of the last pieces of getting my #11ty blog on the #fediverse. I now have the thing building in my self-hosted #Forgejo instance via actions all the way through to rsync'ing the files to my server box. The one missing piece was having to manually ping #BridgyFed to get it to appear.

I gutted out a bash script to extract the URL of the most recent item in my RSS feed and to use that in the curl command to Bridgy Fed. Originally it was going to do this indiscriminately on every build because Eleventy doesn't have a built-in way to know if you built something new. However, thinking a little I realized I can save the RSS from the site right before I push the current build. If the most recent link in the new feed is different than the old feed, hit Bridgy fed with it.

This really matters when I'm scheduling posts ahead (like the podcast episode for earlier today.) When I'm not around to do the manual curl command either I do it much later or forget and do it not at all. This way, it will happen every time there is a new post pushed with or without me being present.

https://evilgeniuschronicles.org/

#eleventy

RE: https://chaos.social/@joergi/116852270118901982

EDIT: Oops, nope, this is actually for migrating your bridged account on the other network *out* of Bridgy. I misunderstood the purpose of this feature, and Bridgy won't have any control over the account once you migrate it away - but it's still cool that you can migrate a bridged account out and take it over if you want to! Apologies for the mistake.

Original Post: Cool! #BridgyFed now gives you the option to choose what #PDS your #Bluesky mirror account will live on! Bridged users already live on Bridgy's independent PDS, but it's damn awesome that they now give you the choice to move your data to whichever PDS you want!

#FediBridge #ATmosphere #Fediverse

RE: https://chaos.social/@joergi/116852270118901982

EDIT: Oops, nope, this is actually for migrating your bridged account on the other network *out* of Bridgy. I misunderstood the purpose of this feature, and Bridgy won't have any control over the account once you migrate it away - but it's still cool that you can migrate a bridged account out and take it over if you want to! Apologies for the mistake.

Original Post: Cool! #BridgyFed now gives you the option to choose what #PDS your #Bluesky mirror account will live on! Bridged users already live on Bridgy's independent PDS, but it's damn awesome that they now give you the choice to move your data to whichever PDS you want!

#FediBridge #ATmosphere #Fediverse

People who use #Bluesky & #Bridgy, follow bridged accounts from Bluesky, or just like the idea of bridging the two worlds: what could I show here? https://blue.mackuba.eu/directory/fedi

I have this list and can also get a list of bridged Bluesky accounts in the other direction. I could show there some stats per instance, search/filter by name, what else?

#BridgyFed #BlueskyBridge

People who use #Bluesky & #Bridgy, follow bridged accounts from Bluesky, or just like the idea of bridging the two worlds: what could I show here? https://blue.mackuba.eu/directory/fedi

I have this list and can also get a list of bridged Bluesky accounts in the other direction. I could show there some stats per instance, search/filter by name, what else?

#BridgyFed #BlueskyBridge

#ATProtocol #Bluesky #ActivityPub #Fediverse #Interoperability #Selfhosted #FediverseDev #OpenProtocols #BridgyFed

Looking for something that probably doesn't exist yet, but maybe someone here knows better.

I self-host both a Mastodon instance and a Bluesky PDS and I'd love to actually connect the two rather than just run them in parallel. Not a cross-poster. I mean real bridging: cross-protocol replies, likes, timelines, notifications, where an interaction on one side actually shows up as a native interaction on the other.

Is there anything out there that gets close to this for a self-hosted setup? I know Bridgy Fed exists, but from what I can tell it doesn't cover the full interaction surface and isn't really designed around self-hosted PDS + self-hosted Mastodon as the starting point.

Happy to hear about anything, experimental, WIP, half-broken. Just curious what the landscape looks like right now.

Boosts appreciated 🙏

#ATProtocol #Bluesky #ActivityPub #Fediverse #Interoperability #Selfhosted #FediverseDev #OpenProtocols #BridgyFed

Looking for something that probably doesn't exist yet, but maybe someone here knows better.

I self-host both a Mastodon instance and a Bluesky PDS and I'd love to actually connect the two rather than just run them in parallel. Not a cross-poster. I mean real bridging: cross-protocol replies, likes, timelines, notifications, where an interaction on one side actually shows up as a native interaction on the other.

Is there anything out there that gets close to this for a self-hosted setup? I know Bridgy Fed exists, but from what I can tell it doesn't cover the full interaction surface and isn't really designed around self-hosted PDS + self-hosted Mastodon as the starting point.

Happy to hear about anything, experimental, WIP, half-broken. Just curious what the landscape looks like right now.

Boosts appreciated 🙏

Eu nem sei de onde eu achei o #fediverse, so sei que pirei! 😜 Achei o maximo, fiz varias contas, muitas mesmo. #pixelfed , #llemmy, #mastodon, #friendica, #pieFed, #Kbin, #threads, #mbin. Fiz ponte no #BridgyFed, usei varios aplicativos pra turbinar tudo e, agora, to achando o maximo o #surf web

Eu nem sei de onde eu achei o #fediverse, so sei que pirei! 😜 Achei o maximo, fiz varias contas, muitas mesmo. #pixelfed , #llemmy, #mastodon, #friendica, #pieFed, #Kbin, #threads, #mbin. Fiz ponte no #BridgyFed, usei varios aplicativos pra turbinar tudo e, agora, to achando o maximo o #surf web

Eu nem sei de onde eu achei o #fediverse, so sei que pirei! 😜 Achei o maximo, fiz varias contas, muitas mesmo. #pixelfed , #llemmy, #mastodon, #friendica, #pieFed, #Kbin, #threads, #mbin. Fiz ponte no #BridgyFed, usei varios aplicativos pra turbinar tudo e, agora, to achando o maximo o #surf web

Eu nem sei de onde eu achei o #fediverse, so sei que pirei! 😜 Achei o maximo, fiz varias contas, muitas mesmo. #pixelfed , #llemmy, #mastodon, #friendica, #pieFed, #Kbin, #threads, #mbin. Fiz ponte no #BridgyFed, usei varios aplicativos pra turbinar tudo e, agora, to achando o maximo o #surf web

Eu nem sei de onde eu achei o #fediverse, so sei que pirei! 😜 Achei o maximo, fiz varias contas, muitas mesmo. #pixelfed , #llemmy, #mastodon, #friendica, #pieFed, #Kbin, #threads, #mbin. Fiz ponte no #BridgyFed, usei varios aplicativos pra turbinar tudo e, agora, to achando o maximo o #surf

Eu nem sei de onde eu achei o #fediverse, so sei que pirei! 😜 Achei o maximo, fiz varias contas, muitas mesmo. #pixelfed , #llemmy, #mastodon, #friendica, #pieFed, #Kbin, #threads, #mbin. Fiz ponte no #BridgyFed, usei varios aplicativos pra turbinar tudo e, agora, to achando o maximo o #surf

Eu nem sei de onde eu achei o #fediverse, so sei que pirei! 😜 Achei o maximo, fiz varias contas, muitas mesmo. #pixelfed , #llemmy, #mastodon, #friendica, #pieFed, #Kbin, #threads, #mbin. Fiz ponte no #BridgyFed, usei varios aplicativos pra turbinar tudo e, agora, to achando o maximo o #surf

Eu nem sei de onde eu achei o #fediverse, so sei que pirei! 😜 Achei o maximo, fiz varias contas, muitas mesmo. #pixelfed , #llemmy, #mastodon, #friendica, #pieFed, #Kbin, #threads, #mbin. Fiz ponte no #BridgyFed, usei varios aplicativos pra turbinar tudo e, agora, to achando o maximo o #surf

I'm so excited for this next year on the #Fediverse.

And the more I learn, the more I think #BridgyFed is going to become a foundational part of our network.

I just posted my first messages from #Emissary across Bridgy to my account on BlueSky.

I still have some things to fix (on my end, not theirs) but it worked.

IT WORKED.

NGL, I feel a little like Morpheus right now. And just think of what it will mean for every account set up on #Bandwagon...

I'm so excited for this next year on the #Fediverse.

And the more I learn, the more I think #BridgyFed is going to become a foundational part of our network.

I just posted my first messages from #Emissary across Bridgy to my account on BlueSky.

I still have some things to fix (on my end, not theirs) but it worked.

IT WORKED.

NGL, I feel a little like Morpheus right now. And just think of what it will mean for every account set up on #Bandwagon...

#Bounce is built on the work of #BridgyFed, which makes your #Bluesky posts visible on #Mastodon and vice versa. Using Bounce will bridge your accounts, in case you haven’t already set up Bridgy Fed. Then, Bounce can move your account from Bluesky to Mastodon by shifting personal data servers and utilizing the native “move” functionality that ActivityPub and AT Protocol have in common.
“Folks on Bluesky will likely never even know you’ve #Bounced to Mastodon.”"

https://www.theverge.com/news/678928/bounce-bluesky-mastodon-bridgy-fed-tool-followers

#Bounce is built on the work of #BridgyFed, which makes your #Bluesky posts visible on #Mastodon and vice versa. Using Bounce will bridge your accounts, in case you haven’t already set up Bridgy Fed. Then, Bounce can move your account from Bluesky to Mastodon by shifting personal data servers and utilizing the native “move” functionality that ActivityPub and AT Protocol have in common.
“Folks on Bluesky will likely never even know you’ve #Bounced to Mastodon.”"

https://www.theverge.com/news/678928/bounce-bluesky-mastodon-bridgy-fed-tool-followers

#HolosDiscover currently blocks #Bluesky accounts bridged via #BridgyFed, because AT Protocol has no equivalent to the indexable flag.
The bridge is opt-in, but bridged users cannot signal refusal of third-party indexing.
Standard opt-out mechanisms remain functional: block @HolosDiscover, #nobot or #noindex in bio, mention with "unfollow".

What's your opinion?

#HolosDiscover currently blocks #Bluesky accounts bridged via #BridgyFed, because AT Protocol has no equivalent to the indexable flag.
The bridge is opt-in, but bridged users cannot signal refusal of third-party indexing.
Standard opt-out mechanisms remain functional: block @HolosDiscover, #nobot or #noindex in bio, mention with "unfollow".

What's your opinion?

#HolosDiscover currently blocks #Bluesky accounts bridged via #BridgyFed, because AT Protocol has no equivalent to the indexable flag.
The bridge is opt-in, but bridged users cannot signal refusal of third-party indexing.
Standard opt-out mechanisms remain functional: block @HolosDiscover, #nobot or #noindex in bio, mention with "unfollow".

What's your opinion?

#HolosDiscover currently blocks #Bluesky accounts bridged via #BridgyFed, because AT Protocol has no equivalent to the indexable flag.
The bridge is opt-in, but bridged users cannot signal refusal of third-party indexing.
Standard opt-out mechanisms remain functional: block @HolosDiscover, #nobot or #noindex in bio, mention with "unfollow".

What's your opinion?

#HolosDiscover currently blocks #Bluesky accounts bridged via #BridgyFed, because AT Protocol has no equivalent to the indexable flag.
The bridge is opt-in, but bridged users cannot signal refusal of third-party indexing.
Standard opt-out mechanisms remain functional: block @HolosDiscover, #nobot or #noindex in bio, mention with "unfollow".

What's your opinion?

"Yeah. So the, I think we are at a bit over 130,000 total bridged accounts on BridgyFed right now, which is good."

That's kind of impressive.

https://openchannels.fm/connecting-decentralized-social-networks-and-rethinking-interoperability/

#fediverse #bridgy #BridgyFed

"Yeah. So the, I think we are at a bit over 130,000 total bridged accounts on BridgyFed right now, which is good."

That's kind of impressive.

https://openchannels.fm/connecting-decentralized-social-networks-and-rethinking-interoperability/

#fediverse #bridgy #BridgyFed

RE: https://socialwebfoundation.org/2026/03/17/introducing-tags-pub/

This seems to be a week for new weird projects. I followed the thing that enables this and also enabled it for my #FediBridge version of my blog. We'll see how it goes. Since the webmentions and boosts go back to the website that might be busy. I might have to figure out if #BridgyFed can mute a user.

RE: https://socialwebfoundation.org/2026/03/17/introducing-tags-pub/

This seems to be a week for new weird projects. I followed the thing that enables this and also enabled it for my #FediBridge version of my blog. We'll see how it goes. Since the webmentions and boosts go back to the website that might be busy. I might have to figure out if #BridgyFed can mute a user.

Now that I have self-hosted Forgejo actions building this blog and transferring it to the host, almost everything is great. The one pebble in the shoe of my transition has been the tags.

I refactored them recently to take out the spaces and wordcase them in both views and pages to make it more friendly to pushing to the fediverse. The only problem with that is that in the process of Bridge Fed ... bridging to the fed all the tags would get congolomerated into one great big concatenated mess. I have been lamenting this.

Tonight I really dug down into my Eleventy templates. I realized that the "p-category" class was assigned to a div and that div wrapped all the tags. It was not being assigned one by one but only one was assigned and it encompassed all of them. So maybe garbage in garbage out?

I wrapped each individual tag with a span and gave each a "p-category" class. This is the first post being pushed since that change. If you see this on Mastodon or other fediverse clients and it has a bunch of individual tags, then succcess. If not, then I guess I will just start pulling my hair out.

Now that I have self-hosted Forgejo actions building this blog and transferring it to the host, almost everything is great. The one pebble in the shoe of my transition has been the tags.

I refactored them recently to take out the spaces and wordcase them in both views and pages to make it more friendly to pushing to the fediverse. The only problem with that is that in the process of Bridge Fed ... bridging to the fed all the tags would get congolomerated into one great big concatenated mess. I have been lamenting this.

Tonight I really dug down into my Eleventy templates. I realized that the "p-category" class was assigned to a div and that div wrapped all the tags. It was not being assigned one by one but only one was assigned and it encompassed all of them. So maybe garbage in garbage out?

I wrapped each individual tag with a span and gave each a "p-category" class. This is the first post being pushed since that change. If you see this on Mastodon or other fediverse clients and it has a bunch of individual tags, then succcess. If not, then I guess I will just start pulling my hair out.

Now that I have self-hosted Forgejo actions building this blog and transferring it to the host, almost everything is great. The one pebble in the shoe of my transition has been the tags.

I refactored them recently to take out the spaces and wordcase them in both views and pages to make it more friendly to pushing to the fediverse. The only problem with that is that in the process of Bridge Fed ... bridging to the fed all the tags would get congolomerated into one great big concatenated mess. I have been lamenting this.

Tonight I really dug down into my Eleventy templates. I realized that the "p-category" class was assigned to a div and that div wrapped all the tags. It was not being assigned one by one but only one was assigned and it encompassed all of them. So maybe garbage in garbage out?

I wrapped each individual tag with a span and gave each a "p-category" class. This is the first post being pushed since that change. If you see this on Mastodon or other fediverse clients and it has a bunch of individual tags, then succcess. If not, then I guess I will just start pulling my hair out.

Now that I have self-hosted Forgejo actions building this blog and transferring it to the host, almost everything is great. The one pebble in the shoe of my transition has been the tags.

I refactored them recently to take out the spaces and wordcase them in both views and pages to make it more friendly to pushing to the fediverse. The only problem with that is that in the process of Bridge Fed ... bridging to the fed all the tags would get congolomerated into one great big concatenated mess. I have been lamenting this.

Tonight I really dug down into my Eleventy templates. I realized that the "p-category" class was assigned to a div and that div wrapped all the tags. It was not being assigned one by one but only one was assigned and it encompassed all of them. So maybe garbage in garbage out?

I wrapped each individual tag with a span and gave each a "p-category" class. This is the first post being pushed since that change. If you see this on Mastodon or other fediverse clients and it has a bunch of individual tags, then succcess. If not, then I guess I will just start pulling my hair out.