#bridgyfed — Public Fediverse posts

#Bluesky non se la passa benissimo dopo il boom iniziale ma c'è un aspetto che continua a renderlo interessante: è basato su un protocollo aperto e può dialogare con #Mastodon e il #Fediverso.

Per chi vuole sperimentare questa apertura, esiste #BridgyFed, che permette di collegare un account Bluesky al Fediverso: https://fed.brid.gy/

👉 Seguite @bsky.brid.gy su Mastodon e seguite le istruzioni per attivare il bridge!

Rilanciato nel gruppo fediverso seguibile qui: @fediverso

#Bluesky non se la passa benissimo dopo il boom iniziale ma c'è un aspetto che continua a renderlo interessante: è basato su un protocollo aperto e può dialogare con #Mastodon e il #Fediverso.

Per chi vuole sperimentare questa apertura, esiste #BridgyFed, che permette di collegare un account Bluesky al Fediverso: https://fed.brid.gy/

👉 Seguite @bsky.brid.gy su Mastodon e seguite le istruzioni per attivare il bridge!

Rilanciato nel gruppo fediverso seguibile qui: @fediverso

#Bluesky non se la passa benissimo dopo il boom iniziale ma c'è un aspetto che continua a renderlo interessante: è basato su un protocollo aperto e può dialogare con #Mastodon e il #Fediverso.

Per chi vuole sperimentare questa apertura, esiste #BridgyFed, che permette di collegare un account Bluesky al Fediverso: https://fed.brid.gy/

👉 Seguite @bsky.brid.gy su Mastodon e seguite le istruzioni per attivare il bridge!

Rilanciato nel gruppo fediverso seguibile qui: @fediverso

#Bluesky non se la passa benissimo dopo il boom iniziale ma c'è un aspetto che continua a renderlo interessante: è basato su un protocollo aperto e può dialogare con #Mastodon e il #Fediverso.

Per chi vuole sperimentare questa apertura, esiste #BridgyFed, che permette di collegare un account Bluesky al Fediverso: https://fed.brid.gy/

👉 Seguite @bsky.brid.gy su Mastodon e seguite le istruzioni per attivare il bridge!

Rilanciato nel gruppo fediverso seguibile qui: @fediverso

#Bluesky non se la passa benissimo dopo il boom iniziale ma c'è un aspetto che continua a renderlo interessante: è basato su un protocollo aperto e può dialogare con #Mastodon e il #Fediverso.

Per chi vuole sperimentare questa apertura, esiste #BridgyFed, che permette di collegare un account Bluesky al Fediverso: https://fed.brid.gy/

👉 Seguite @bsky.brid.gy su Mastodon e seguite le istruzioni per attivare il bridge!

Rilanciato nel gruppo fediverso seguibile qui: @fediverso

#BridgyFed is a decentralized #socialnetwork bridge

https://fed.brid.gy/docs

#BridgyFed is a decentralized #socialnetwork bridge

https://fed.brid.gy/docs

#BridgyFed is a decentralized #socialnetwork bridge

https://fed.brid.gy/docs

#BridgyFed is a decentralized #socialnetwork bridge

https://fed.brid.gy/docs

#BridgyFed is a decentralized #socialnetwork bridge

https://fed.brid.gy/docs

I’d like to know if anyone here uses Bridgy to follow Bluesky accounts. I’ve been trying it for a few days now, but I can’t seem to find any of my Bsky friends on Bridgy/Mastodon. I’ve checked our instance-moderated accounts, and it appears that Bridgy profiles are working fine.

#fediverse #bluesky #mastodon #bridgyfed

I’d like to know if anyone here uses Bridgy to follow Bluesky accounts. I’ve been trying it for a few days now, but I can’t seem to find any of my Bsky friends on Bridgy/Mastodon. I’ve checked our instance-moderated accounts, and it appears that Bridgy profiles are working fine.

#fediverse #bluesky #mastodon #bridgyfed

I’d like to know if anyone here uses Bridgy to follow Bluesky accounts. I’ve been trying it for a few days now, but I can’t seem to find any of my Bsky friends on Bridgy/Mastodon. I’ve checked our instance-moderated accounts, and it appears that Bridgy profiles are working fine.

#fediverse #bluesky #mastodon #bridgyfed

I’d like to know if anyone here uses Bridgy to follow Bluesky accounts. I’ve been trying it for a few days now, but I can’t seem to find any of my Bsky friends on Bridgy/Mastodon. I’ve checked our instance-moderated accounts, and it appears that Bridgy profiles are working fine.

#fediverse #bluesky #mastodon #bridgyfed

I’d like to know if anyone here uses Bridgy to follow Bluesky accounts. I’ve been trying it for a few days now, but I can’t seem to find any of my Bsky friends on Bridgy/Mastodon. I’ve checked our instance-moderated accounts, and it appears that Bridgy profiles are working fine.

#fediverse #bluesky #mastodon #bridgyfed

This might be crazy but... I don't need my old exploded host's fediverse export to restore my past posts and media...

It was bridged via #bridgyFed so #slurp can fetch *that* and then import to my #selfHosted #goToSocial

This might be crazy but... I don't need my old exploded host's fediverse export to restore my past posts and media...

It was bridged via #bridgyFed so #slurp can fetch *that* and then import to my #selfHosted #goToSocial

This might be crazy but... I don't need my old exploded host's fediverse export to restore my past posts and media...

It was bridged via #bridgyFed so #slurp can fetch *that* and then import to my #selfHosted #goToSocial

My fedi originating posts with images consistently do not display the images on bsky. Is this for everyone or just me?

#bridgy #bridgyfed

My fedi originating posts with images consistently do not display the images on bsky. Is this for everyone or just me?

#bridgy #bridgyfed

My fedi originating posts with images consistently do not display the images on bsky. Is this for everyone or just me?

#bridgy #bridgyfed

My fedi originating posts with images consistently do not display the images on bsky. Is this for everyone or just me?

#bridgy #bridgyfed

My fedi originating posts with images consistently do not display the images on bsky. Is this for everyone or just me?

#bridgy #bridgyfed

先日からBridgy Fedで非ブリッジアカウントから返信があった時のDM通知に、その返信の投稿者名と本文も含まれるようになったのよ。
で、その後初めて返信があって実際にその通知が届いたんだけど、良い感じ！やっぱり本文が含まれていると便利で良いね！

以前はDM通知が届いたときに既に該当の返信が削除されていると誰だったのかも分からないし「なんだったの？」ってなることがあったけど、これなら少なくとも誰からどんな内容の返信があったのかが分かる。

#bridgyfed

先日からBridgy Fedで非ブリッジアカウントから返信があった時のDM通知に、その返信の投稿者名と本文も含まれるようになったのよ。
で、その後初めて返信があって実際にその通知が届いたんだけど、良い感じ！やっぱり本文が含まれていると便利で良いね！

以前はDM通知が届いたときに既に該当の返信が削除されていると誰だったのかも分からないし「なんだったの？」ってなることがあったけど、これなら少なくとも誰からどんな内容の返信があったのかが分かる。

#bridgyfed

先日からBridgy Fedで非ブリッジアカウントから返信があった時のDM通知に、その返信の投稿者名と本文も含まれるようになったのよ。
で、その後初めて返信があって実際にその通知が届いたんだけど、良い感じ！やっぱり本文が含まれていると便利で良いね！

以前はDM通知が届いたときに既に該当の返信が削除されていると誰だったのかも分からないし「なんだったの？」ってなることがあったけど、これなら少なくとも誰からどんな内容の返信があったのかが分かる。

#bridgyfed

Spero di non avere fatto troppi errori comunque...

Questa è la mia configurazione su Firefox per ridurre le frizioni nell'utilizzo di Bridgy Fed lato Fediverso.

Cosa fa:

1) Da Phanpy, mi avvisa visivamente se supero i 300 caratteri, così evito, nei limiti del possibile, che il post venga troncato e convertito in un link su Bluesky.
(Se posso ridurre bene, se no, come in questo caso, pazienza)

2) Apre i singoli post su Skyview, mostrando il thread completo anche con le risposte di account non federati.
3) Apre i profili su Bluesky Viewer, bypassando il blocco per gli utenti non autenticati del sito ufficiale e mostrando non solo i post originali ma anche i reply.
(Amici su bluesky, è tutto pubblico)

Come si installa:

Installa queste estensioni su Firefox:

Redirector -> https://addons.mozilla.org/it/firefox/addon/redirector/
Tampermonkey -> https://addons.mozilla.org/it/firefox/addon/tampermonkey/

Scarica questi due file

https://www.sironi.xyz/LucaSironi.fediverse.redirector.Redirector.json
https://www.sironi.xyz/LucaSironi.fediverse.tampermonkey.zip

Configurazione:

1) Importa le regole su Redirector:

Clicca sull'icona di Redirector -> Edit Redirects -> Pulsante "Import" in fondo e seleziona il file .json scaricato.

(per quanto riguarda blueskyviewer passa l'handle tramite URL, anche se il sito putroppo non lo gestisce)

2) Importa gli script su Tampermonkey:

Clicca sull'icona di Tampermonkey -> Pannello di controllo -> Scheda "Utilità" in alto -> Sezione "Importa" -> Scegli il file .zip scaricato e clicca Importa.

(uno script e' l'avviso visivo per i 300 caratteri, l'altro recupera l'handle modificato dalla url , lo scrive nel riquadro e avvia la ricerca)

#Fediverse #Mastodon #Bluesky #bridgyfed

Spero di non avere fatto troppi errori comunque...

Questa è la mia configurazione su Firefox per ridurre le frizioni nell'utilizzo di Bridgy Fed lato Fediverso.

Cosa fa:

1) Da Phanpy, mi avvisa visivamente se supero i 300 caratteri, così evito, nei limiti del possibile, che il post venga troncato e convertito in un link su Bluesky.
(Se posso ridurre bene, se no, come in questo caso, pazienza)

2) Apre i singoli post su Skyview, mostrando il thread completo anche con le risposte di account non federati.
3) Apre i profili su Bluesky Viewer, bypassando il blocco per gli utenti non autenticati del sito ufficiale e mostrando non solo i post originali ma anche i reply.
(Amici su bluesky, è tutto pubblico)

Come si installa:

Installa queste estensioni su Firefox:

Redirector -> https://addons.mozilla.org/it/firefox/addon/redirector/
Tampermonkey -> https://addons.mozilla.org/it/firefox/addon/tampermonkey/

Scarica questi due file

https://www.sironi.xyz/LucaSironi.fediverse.redirector.Redirector.json
https://www.sironi.xyz/LucaSironi.fediverse.tampermonkey.zip

Configurazione:

1) Importa le regole su Redirector:

Clicca sull'icona di Redirector -> Edit Redirects -> Pulsante "Import" in fondo e seleziona il file .json scaricato.

(per quanto riguarda blueskyviewer passa l'handle tramite URL, anche se il sito putroppo non lo gestisce)

2) Importa gli script su Tampermonkey:

Clicca sull'icona di Tampermonkey -> Pannello di controllo -> Scheda "Utilità" in alto -> Sezione "Importa" -> Scegli il file .zip scaricato e clicca Importa.

(uno script e' l'avviso visivo per i 300 caratteri, l'altro recupera l'handle modificato dalla url , lo scrive nel riquadro e avvia la ricerca)

#Fediverse #Mastodon #Bluesky #bridgyfed

Spero di non avere fatto troppi errori comunque...

Questa è la mia configurazione su Firefox per ridurre le frizioni nell'utilizzo di Bridgy Fed lato Fediverso.

Cosa fa:

1) Da Phanpy, mi avvisa visivamente se supero i 300 caratteri, così evito, nei limiti del possibile, che il post venga troncato e convertito in un link su Bluesky.
(Se posso ridurre bene, se no, come in questo caso, pazienza)

2) Apre i singoli post su Skyview, mostrando il thread completo anche con le risposte di account non federati.
3) Apre i profili su Bluesky Viewer, bypassando il blocco per gli utenti non autenticati del sito ufficiale e mostrando non solo i post originali ma anche i reply.
(Amici su bluesky, è tutto pubblico)

Come si installa:

Installa queste estensioni su Firefox:

Redirector -> https://addons.mozilla.org/it/firefox/addon/redirector/
Tampermonkey -> https://addons.mozilla.org/it/firefox/addon/tampermonkey/

Scarica questi due file

https://www.sironi.xyz/LucaSironi.fediverse.redirector.Redirector.json
https://www.sironi.xyz/LucaSironi.fediverse.tampermonkey.zip

Configurazione:

1) Importa le regole su Redirector:

Clicca sull'icona di Redirector -> Edit Redirects -> Pulsante "Import" in fondo e seleziona il file .json scaricato.

(per quanto riguarda blueskyviewer passa l'handle tramite URL, anche se il sito putroppo non lo gestisce)

2) Importa gli script su Tampermonkey:

Clicca sull'icona di Tampermonkey -> Pannello di controllo -> Scheda "Utilità" in alto -> Sezione "Importa" -> Scegli il file .zip scaricato e clicca Importa.

(uno script e' l'avviso visivo per i 300 caratteri, l'altro recupera l'handle modificato dalla url , lo scrive nel riquadro e avvia la ricerca)

#Fediverse #Mastodon #Bluesky #bridgyfed

Spero di non avere fatto troppi errori comunque...

Questa è la mia configurazione su Firefox per ridurre le frizioni nell'utilizzo di Bridgy Fed lato Fediverso.

Cosa fa:

1) Da Phanpy, mi avvisa visivamente se supero i 300 caratteri, così evito, nei limiti del possibile, che il post venga troncato e convertito in un link su Bluesky.
(Se posso ridurre bene, se no, come in questo caso, pazienza)

2) Apre i singoli post su Skyview, mostrando il thread completo anche con le risposte di account non federati.
3) Apre i profili su Bluesky Viewer, bypassando il blocco per gli utenti non autenticati del sito ufficiale e mostrando non solo i post originali ma anche i reply.
(Amici su bluesky, è tutto pubblico)

Come si installa:

Installa queste estensioni su Firefox:

Redirector -> https://addons.mozilla.org/it/firefox/addon/redirector/
Tampermonkey -> https://addons.mozilla.org/it/firefox/addon/tampermonkey/

Scarica questi due file

https://www.sironi.xyz/LucaSironi.fediverse.redirector.Redirector.json
https://www.sironi.xyz/LucaSironi.fediverse.tampermonkey.zip

Configurazione:

1) Importa le regole su Redirector:

Clicca sull'icona di Redirector -> Edit Redirects -> Pulsante "Import" in fondo e seleziona il file .json scaricato.

(per quanto riguarda blueskyviewer passa l'handle tramite URL, anche se il sito putroppo non lo gestisce)

2) Importa gli script su Tampermonkey:

Clicca sull'icona di Tampermonkey -> Pannello di controllo -> Scheda "Utilità" in alto -> Sezione "Importa" -> Scegli il file .zip scaricato e clicca Importa.

(uno script e' l'avviso visivo per i 300 caratteri, l'altro recupera l'handle modificato dalla url , lo scrive nel riquadro e avvia la ricerca)

#Fediverse #Mastodon #Bluesky #bridgyfed

Spero di non avere fatto troppi errori comunque...

Questa è la mia configurazione su Firefox per ridurre le frizioni nell'utilizzo di Bridgy Fed lato Fediverso.

Cosa fa:

1) Da Phanpy, mi avvisa visivamente se supero i 300 caratteri, così evito, nei limiti del possibile, che il post venga troncato e convertito in un link su Bluesky.
(Se posso ridurre bene, se no, come in questo caso, pazienza)

2) Apre i singoli post su Skyview, mostrando il thread completo anche con le risposte di account non federati.
3) Apre i profili su Bluesky Viewer, bypassando il blocco per gli utenti non autenticati del sito ufficiale e mostrando non solo i post originali ma anche i reply.
(Amici su bluesky, è tutto pubblico)

Come si installa:

Installa queste estensioni su Firefox:

Redirector -> https://addons.mozilla.org/it/firefox/addon/redirector/
Tampermonkey -> https://addons.mozilla.org/it/firefox/addon/tampermonkey/

Scarica questi due file

https://www.sironi.xyz/LucaSironi.fediverse.redirector.Redirector.json
https://www.sironi.xyz/LucaSironi.fediverse.tampermonkey.zip

Configurazione:

1) Importa le regole su Redirector:

Clicca sull'icona di Redirector -> Edit Redirects -> Pulsante "Import" in fondo e seleziona il file .json scaricato.

(per quanto riguarda blueskyviewer passa l'handle tramite URL, anche se il sito putroppo non lo gestisce)

2) Importa gli script su Tampermonkey:

Clicca sull'icona di Tampermonkey -> Pannello di controllo -> Scheda "Utilità" in alto -> Sezione "Importa" -> Scegli il file .zip scaricato e clicca Importa.

(uno script e' l'avviso visivo per i 300 caratteri, l'altro recupera l'handle modificato dalla url , lo scrive nel riquadro e avvia la ricerca)

#Fediverse #Mastodon #Bluesky #bridgyfed

@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 🙂

@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 🙂

@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 🙂

@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 🙂

@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

@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

@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 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 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.

https://bsky.app/profile/thebobster420.bsky.social/post/3mqh2sgdfy22a
https://bsky.app/profile/thebobster420.bsky.social/post/3mqh6pl5pfh23

また同じ利用者から謎の絡みがあったので、Bridgy Fed の画面で「block」してみた。しかしブロック済みアカウントのリストがないのでよく分からない。

当該利用者の投稿は、挑発というより意味不明の域に入っていた。「トロール」なのかな。

#BridgyFed

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.

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 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.