#bridgyfed — Public Fediverse posts

@baileytownsend

hello !
I'm the one asking everyone to enable the #bridgyfed even on secondary accounts, because my ideal world is to discuss with people regardless of where they come from, and double accounts break the flow 🙂

@ajhalili2006

Maybe they will start to sell instant access to VDL posts 😀

Anyway, I wonder, I'm just a #bridgyfed guy (which I think is the best we could do, to constantly push good #fediverse narrative there), how's going eurosky in terms of user stats, new users, active users, migrated users.
It would be great if we can se them outperform that other thing

@aral @_elena @eurosky.social

@ajhalili2006

Maybe they will start to sell instant access to VDL posts 😀

Anyway, I wonder, I'm just a #bridgyfed guy (which I think is the best we could do, to constantly push good #fediverse narrative there), how's going eurosky in terms of user stats, new users, active users, migrated users.
It would be great if we can se them outperform that other thing

@aral @_elena @eurosky.social

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.

I was perhaps too subtle in trying to get Bridgy Fed to recognize my timestamps. All subtlety has been removed.

I was confused why Bridgy Fed always pushes my posts to Mastodon as midnight UTC. Turns out that on my post page, I have a dt-published element but it was date only. I added the time in so with any luck this will come in with the correct time.

I was perhaps too subtle in trying to get Bridgy Fed to recognize my timestamps. All subtlety has been removed.

I was confused why Bridgy Fed always pushes my posts to Mastodon as midnight UTC. Turns out that on my post page, I have a dt-published element but it was date only. I added the time in so with any luck this will come in with the correct time.

@evilgeniuschronicles.org I'd love to figure out why #bridgyfed thinks every post is happening at 00:00 in GMT. That post which pushed minutes ago says it is 23 hours old. I guess I need to dig through the docs to figure out where it picks up the time.

@evilgeniuschronicles.org I'd love to figure out why #bridgyfed thinks every post is happening at 00:00 in GMT. That post which pushed minutes ago says it is 23 hours old. I guess I need to dig through the docs to figure out where it picks up the time.

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

One thing about using #BridgyFed is there are still a lot of people on Bluesky who use whataboutism in respect to the #GazaGenocide. It's nice that we don't have much of that on this side of the bridge.

One thing about using #BridgyFed is there are still a lot of people on Bluesky who use whataboutism in respect to the #GazaGenocide. It's nice that we don't have much of that on this side of the bridge.

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

@snarfed.org Sorry to bother, but when a Bluesky user starts following the bridge, how long on average does it take for them to become visible on Mastodon? I've asked someone to follow the bridge two hours ago now and they're still not visible.

As per FAQ on the #Bridgyfed website it should take "a few minutes". Is there some outage?

@snarfed.org Sorry to bother, but when a Bluesky user starts following the bridge, how long on average does it take for them to become visible on Mastodon? I've asked someone to follow the bridge two hours ago now and they're still not visible.

As per FAQ on the #Bridgyfed website it should take "a few minutes". Is there some outage?

We tend to block followbots and bridges that aren't #FediBuzz or #BridgyFed for this reason (and reduplication, storage is expensive yo).

We tend to block followbots and bridges that aren't #FediBuzz or #BridgyFed for this reason (and reduplication, storage is expensive yo).

私が報告した、Bridgy Fedで非ブリッジアカウントとの会話が続けられない件（返信の返信に対する通知が来ない）に、「now」ラベルが付いた！（対応優先度が高い状態）
私の他にも同様の現象になっているとコメントしてくれた人がいたからかな。ありがたい。

DM notifs for responses to replies sent from web UI
https://github.com/snarfed/bridgy-fed/issues/2481

#bridgyfed #まったり部

Bridgy Fedの非ブリッジアカウントから返信があったときのDM通知に、返信内容と返信者情報を含める案のイシューが開発者さんから投稿されていた。そうなったら嬉しいなぁ。

Include actual reply contents and author in DM notifs
https://github.com/snarfed/bridgy-fed/issues/2541

#bridgyfed #まったり部

Is there a Thing to help me follow who I followed from #Bluesky via #Bridgyfed or whatever?

I set up the bridge but I don't even know who from Blue sky bridged, let alone follow 'em.

Is there a Thing to help me follow who I followed from #Bluesky via #Bridgyfed or whatever?

I set up the bridge but I don't even know who from Blue sky bridged, let alone follow 'em.

#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 🙏

@eurosky.social

that and enable #bridgyfed also !

As sketchy competitors appears in the atmosphere, I was thinking that would be cool, if people joining @eurosky.social could follow by default the #bridgyfed
​
@quillmatiq
@sebastian.eurosky.social

#bluesky #bridgyfed #eurosky

(non c'e' ragione di non attivare il #bridgyfed che già siamo pochi, se ci dividiamo in parrocchie non raggiungiamo neanche il 3% ...)

ブリッジ復活した。

#bridgyfed

Blueskyへのブリッジ止まってる？

#bridgyfed