#microdotblog — Public Fediverse posts

Since ​@[email protected] seems unable (or unwilling) to understand that many users desire the #FediVerse to be a place where opt-in is the normal and expected implementation for features such as #relays I propose that #fedidevelopers take up this call.

The problem: the implementation of relays lacks sufficient user-based controls. While users may (at least on platforms such as GotoSocial) add relays they desire to have their content sent to, there are no user based controls over relays configured at the instance level.

The current implementation appears to have unintended, and unconsidered consequences associated with it.

Ban evasion can likely be achieved through chaining relays together. We have already seen the unintended consequence of a relay following tags.pub leading to content being relayed non-consensually.

Something that has not been considered is potential damages to users in regions where political, social, or religious beliefs are sensitive topics need to maintain tight controls over where their content is sent. This is a case where the handling and relaying of posts needs to be 100 percent bulletproof.

The Solution: all platforms in the Fediverse should implement instance level relays in the following manner:

1. Instance level relays are disabled for all users on that instance.
2. User settings provide a list of the relays provided at the instance level.
   1. Users can opt to leave the relay(s) disabled, or
   2. They can choose to enable the relays they trust their content being sent to.

Through this implementation we avoid clunky workarounds like adding hashtags to profiles. Also, we make this feature more discoverable for new users who are unfamiliar with the conventions of the FediVerse.

I am unfamiliar with the #FEP submission process and requirements. Anyone willing to work with me on this, I would like to see this brought forth as a FEP.

#fedideveloperverse #fedideveloper #mastodon #gotosocial #misskeyworld #misskey #pixelfed #microdotblog #pleroma #sharkeydev
@alice @admin @gotosocial @Gargron

Since ​@[email protected] seems unable (or unwilling) to understand that many users desire the #FediVerse to be a place where opt-in is the normal and expected implementation for features such as #relays I propose that #fedidevelopers take up this call.

The problem: the implementation of relays lacks sufficient user-based controls. While users may (at least on platforms such as GotoSocial) add relays they desire to have their content sent to, there are no user based controls over relays configured at the instance level.

The current implementation appears to have unintended, and unconsidered consequences associated with it.

Ban evasion can likely be achieved through chaining relays together. We have already seen the unintended consequence of a relay following tags.pub leading to content being relayed non-consensually.

Something that has not been considered is potential damages to users in regions where political, social, or religious beliefs are sensitive topics need to maintain tight controls over where their content is sent. This is a case where the handling and relaying of posts needs to be 100 percent bulletproof.

The Solution: all platforms in the Fediverse should implement instance level relays in the following manner:

1. Instance level relays are disabled for all users on that instance.
2. User settings provide a list of the relays provided at the instance level.
   1. Users can opt to leave the relay(s) disabled, or
   2. They can choose to enable the relays they trust their content being sent to.

Through this implementation we avoid clunky workarounds like adding hashtags to profiles. Also, we make this feature more discoverable for new users who are unfamiliar with the conventions of the FediVerse.

I am unfamiliar with the #FEP submission process and requirements. Anyone willing to work with me on this, I would like to see this brought forth as a FEP.

#fedideveloperverse #fedideveloper #mastodon #gotosocial #misskeyworld #misskey #pixelfed #microdotblog #pleroma #sharkeydev
@alice @admin @gotosocial @Gargron

Since ​@[email protected] seems unable (or unwilling) to understand that many users desire the #FediVerse to be a place where opt-in is the normal and expected implementation for features such as #relays I propose that #fedidevelopers take up this call.

The problem: the implementation of relays lacks sufficient user-based controls. While users may (at least on platforms such as GotoSocial) add relays they desire to have their content sent to, there are no user based controls over relays configured at the instance level.

The current implementation appears to have unintended, and unconsidered consequences associated with it.

Ban evasion can likely be achieved through chaining relays together. We have already seen the unintended consequence of a relay following tags.pub leading to content being relayed non-consensually.

Something that has not been considered is potential damages to users in regions where political, social, or religious beliefs are sensitive topics need to maintain tight controls over where their content is sent. This is a case where the handling and relaying of posts needs to be 100 percent bulletproof.

The Solution: all platforms in the Fediverse should implement instance level relays in the following manner:

1. Instance level relays are disabled for all users on that instance.
2. User settings provide a list of the relays provided at the instance level.
   1. Users can opt to leave the relay(s) disabled, or
   2. They can choose to enable the relays they trust their content being sent to.

Through this implementation we avoid clunky workarounds like adding hashtags to profiles. Also, we make this feature more discoverable for new users who are unfamiliar with the conventions of the FediVerse.

I am unfamiliar with the #FEP submission process and requirements. Anyone willing to work with me on this, I would like to see this brought forth as a FEP.

#fedideveloperverse #fedideveloper #mastodon #gotosocial #misskeyworld #misskey #pixelfed #microdotblog #pleroma #sharkeydev
@alice @admin @gotosocial @Gargron

Since ​@[email protected] seems unable (or unwilling) to understand that many users desire the #FediVerse to be a place where opt-in is the normal and expected implementation for features such as #relays I propose that #fedidevelopers take up this call.

The problem: the implementation of relays lacks sufficient user-based controls. While users may (at least on platforms such as GotoSocial) add relays they desire to have their content sent to, there are no user based controls over relays configured at the instance level.

The current implementation appears to have unintended, and unconsidered consequences associated with it.

Ban evasion can likely be achieved through chaining relays together. We have already seen the unintended consequence of a relay following tags.pub leading to content being relayed non-consensually.

Something that has not been considered is potential damages to users in regions where political, social, or religious beliefs are sensitive topics need to maintain tight controls over where their content is sent. This is a case where the handling and relaying of posts needs to be 100 percent bulletproof.

The Solution: all platforms in the Fediverse should implement instance level relays in the following manner:

1. Instance level relays are disabled for all users on that instance.
2. User settings provide a list of the relays provided at the instance level.
   1. Users can opt to leave the relay(s) disabled, or
   2. They can choose to enable the relays they trust their content being sent to.

Through this implementation we avoid clunky workarounds like adding hashtags to profiles. Also, we make this feature more discoverable for new users who are unfamiliar with the conventions of the FediVerse.

I am unfamiliar with the #FEP submission process and requirements. Anyone willing to work with me on this, I would like to see this brought forth as a FEP.

#fedideveloperverse #fedideveloper #mastodon #gotosocial #misskeyworld #misskey #pixelfed #microdotblog #pleroma #sharkeydev
@alice @admin @gotosocial @Gargron

Since ​@[email protected] seems unable (or unwilling) to understand that many users desire the #FediVerse to be a place where opt-in is the normal and expected implementation for features such as #relays I propose that #fedidevelopers take up this call.

The problem: the implementation of relays lacks sufficient user-based controls. While users may (at least on platforms such as GotoSocial) add relays they desire to have their content sent to, there are no user based controls over relays configured at the instance level.

The current implementation appears to have unintended, and unconsidered consequences associated with it.

Ban evasion can likely be achieved through chaining relays together. We have already seen the unintended consequence of a relay following tags.pub leading to content being relayed non-consensually.

Something that has not been considered is potential damages to users in regions where political, social, or religious beliefs are sensitive topics need to maintain tight controls over where their content is sent. This is a case where the handling and relaying of posts needs to be 100 percent bulletproof.

The Solution: all platforms in the Fediverse should implement instance level relays in the following manner:

1. Instance level relays are disabled for all users on that instance.
2. User settings provide a list of the relays provided at the instance level.
   1. Users can opt to leave the relay(s) disabled, or
   2. They can choose to enable the relays they trust their content being sent to.

Through this implementation we avoid clunky workarounds like adding hashtags to profiles. Also, we make this feature more discoverable for new users who are unfamiliar with the conventions of the FediVerse.

I am unfamiliar with the #FEP submission process and requirements. Anyone willing to work with me on this, I would like to see this brought forth as a FEP.

#fedideveloperverse #fedideveloper #mastodon #gotosocial #misskeyworld #misskey #pixelfed #microdotblog #pleroma #sharkeydev
@alice @admin @gotosocial @Gargron

Competing against #Pixelfed was not enough as @threads now seeks to dominate the podcast arena.

👉🏾 #Threads Launches New Feature to Attract Podcast Fans https://www.entrepreneur.com/business-news/threads-launches-new-feature-to-attract-podcast-fans/501240

This is a good sign for podcasting #Fediverse apps like @Castopod, #WordPress (as well as @wordpressdotcom), @ghost, #MicroDotBlog, @peertube, etcetera, as it means more people are interested in listening to & creating podcasts.

I think professional podcasters will opt to use their own sites instead of relying on #Meta.

Competing against #Pixelfed was not enough as @threads now seeks to dominate the podcast arena.

👉🏾 #Threads Launches New Feature to Attract Podcast Fans https://www.entrepreneur.com/business-news/threads-launches-new-feature-to-attract-podcast-fans/501240

This is a good sign for podcasting #Fediverse apps like @Castopod, #WordPress (as well as @wordpressdotcom), @ghost, #MicroDotBlog, @peertube, etcetera, as it means more people are interested in listening to & creating podcasts.

I think professional podcasters will opt to use their own sites instead of relying on #Meta.

Competing against #Pixelfed was not enough as @threads now seeks to dominate the podcast arena.

👉🏾 #Threads Launches New Feature to Attract Podcast Fans https://www.entrepreneur.com/business-news/threads-launches-new-feature-to-attract-podcast-fans/501240

This is a good sign for podcasting #Fediverse apps like @Castopod, #WordPress (as well as @wordpressdotcom), @ghost, #MicroDotBlog, @peertube, etcetera, as it means more people are interested in listening to & creating podcasts.

I think professional podcasters will opt to use their own sites instead of relying on #Meta.

Competing against #Pixelfed was not enough as @threads now seeks to dominate the podcast arena.

👉🏾 #Threads Launches New Feature to Attract Podcast Fans https://www.entrepreneur.com/business-news/threads-launches-new-feature-to-attract-podcast-fans/501240

This is a good sign for podcasting #Fediverse apps like @Castopod, #WordPress (as well as @wordpressdotcom), @ghost, #MicroDotBlog, @peertube, etcetera, as it means more people are interested in listening to & creating podcasts.

I think professional podcasters will opt to use their own sites instead of relying on #Meta.

Competing against #Pixelfed was not enough as @threads now seeks to dominate the podcast arena.

👉🏾 #Threads Launches New Feature to Attract Podcast Fans https://www.entrepreneur.com/business-news/threads-launches-new-feature-to-attract-podcast-fans/501240

This is a good sign for podcasting #Fediverse apps like @Castopod, #WordPress (as well as @wordpressdotcom), @ghost, #MicroDotBlog, @peertube, etcetera, as it means more people are interested in listening to & creating podcasts.

I think professional podcasters will opt to use their own sites instead of relying on #Meta.

New on my site: a nostr relay for myself. whilst I don’t use it much, it’s cool to have my own personal backup of posts on an “experimental” protocol… and it’s super lightweight. and migrating my #microdotblog posts from j4ck.xyz → posts.j4ck.xyz!

New on my site: a nostr relay for myself. whilst I don’t use it much, it’s cool to have my own personal backup of posts on an “experimental” protocol… and it’s super lightweight. and migrating my #microdotblog posts from j4ck.xyz → posts.j4ck.xyz!

I am increasingly using #Microdotblog to publish out across Bluesky, Mastodon, Threads and other places. And using #surfsocial to browse content from the same, in one UX – plus blogs, plus podcasts, plus RSS. Open Social Web FTW!
https://about.surf.social

I am increasingly using #Microdotblog to publish out across Bluesky, Mastodon, Threads and other places. And using #surfsocial to browse content from the same, in one UX – plus blogs, plus podcasts, plus RSS. Open Social Web FTW!
https://about.surf.social

I am increasingly using #Microdotblog to publish out across Bluesky, Mastodon, Threads and other places. And using #surfsocial to browse content from the same, in one UX – plus blogs, plus podcasts, plus RSS. Open Social Web FTW!
https://about.surf.social

I am increasingly using #Microdotblog to publish out across Bluesky, Mastodon, Threads and other places. And using #surfsocial to browse content from the same, in one UX – plus blogs, plus podcasts, plus RSS. Open Social Web FTW!
https://about.surf.social

I am increasingly using #Microdotblog to publish out across Bluesky, Mastodon, Threads and other places. And using #surfsocial to browse content from the same, in one UX – plus blogs, plus podcasts, plus RSS. Open Social Web FTW!
https://about.surf.social

@manton - Is supporting App Passwords on the roadmap for #Microdotblog for your BlueSky cross-posting support?

@manton - Is supporting App Passwords on the roadmap for #Microdotblog for your BlueSky cross-posting support?

@manton - Is supporting App Passwords on the roadmap for #Microdotblog for your BlueSky cross-posting support?

@manton - Is supporting App Passwords on the roadmap for #Microdotblog for your BlueSky cross-posting support?

@manton - Is supporting App Passwords on the roadmap for #Microdotblog for your BlueSky cross-posting support?

Achievement of the weekend was refining my rss feed to show micro posts as titleless posts in the micro. blog timeline. Had it working last night, but fully rebuilt it today as I broke something with my final tweaks last night. #indieweb #microdotblog

https://lee-perry.co.uk/microfeed/2025-05-11-micro

Achievement of the weekend was refining my rss feed to show micro posts as titleless posts in the micro. blog timeline. Had it working last night, but fully rebuilt it today as I broke something with my final tweaks last night. #indieweb #microdotblog

https://lee-perry.co.uk/microfeed/2025-05-11-micro

Achievement of the weekend was refining my rss feed to show micro posts as titleless posts in the micro. blog timeline. Had it working last night, but fully rebuilt it today as I broke something with my final tweaks last night. #indieweb #microdotblog

https://lee-perry.co.uk/microfeed/2025-05-11-micro

Achievement of the weekend was refining my rss feed to show micro posts as titleless posts in the micro. blog timeline. Had it working last night, but fully rebuilt it today as I broke something with my final tweaks last night. #indieweb #microdotblog

https://lee-perry.co.uk/microfeed/2025-05-11-micro

. @manton talking about micro.blog at the Developer Meetup at the Fediverse House

#DeSo #Fediverse #FediverseHouse #FediverseHouse2025 #MicroDotBlog

. @manton talking about micro.blog at the Developer Meetup at the Fediverse House

#DeSo #Fediverse #FediverseHouse #FediverseHouse2025 #MicroDotBlog

. @manton talking about micro.blog at the Developer Meetup at the Fediverse House

#DeSo #Fediverse #FediverseHouse #FediverseHouse2025 #MicroDotBlog

. @manton talking about micro.blog at the Developer Meetup at the Fediverse House

#DeSo #Fediverse #FediverseHouse #FediverseHouse2025 #MicroDotBlog

. @manton talking about micro.blog at the Developer Meetup at the Fediverse House

#DeSo #Fediverse #FediverseHouse #FediverseHouse2025 #MicroDotBlog

What’s even cooler about this migration from #Instagram to Pixelfed is that I can use their APIs to auto crosspost from my micro.blog page to my “Instagram” (Pixelfed) account, yet it still stays on my site! #microblog #microdotblog

What’s even cooler about this migration from #Instagram to Pixelfed is that I can use their APIs to auto crosspost from my micro.blog page to my “Instagram” (Pixelfed) account, yet it still stays on my site! #microblog #microdotblog

What’s even cooler about this migration from #Instagram to Pixelfed is that I can use their APIs to auto crosspost from my micro.blog page to my “Instagram” (Pixelfed) account, yet it still stays on my site! #microblog #microdotblog

What’s even cooler about this migration from #Instagram to Pixelfed is that I can use their APIs to auto crosspost from my micro.blog page to my “Instagram” (Pixelfed) account, yet it still stays on my site! #microblog #microdotblog

damn i can't lie, wish #microdotblog was free. looks pretty nice.
oh well.

damn i can't lie, wish #microdotblog was free. looks pretty nice.
oh well.

damn i can't lie, wish #microdotblog was free. looks pretty nice.
oh well.

damn i can't lie, wish #microdotblog was free. looks pretty nice.
oh well.

damn i can't lie, wish #microdotblog was free. looks pretty nice.
oh well.

Does anyone know of a survey that has been sent to node owners about their hosting experiences? Is anyone taking the pulse of the fediverse to identify issues, software requests and/or feature requests? Or is this all self reported?

#fediverse #mastodon #lemmy #peertube #misskey #microdotblog

Does anyone know of a survey that has been sent to node owners about their hosting experiences? Is anyone taking the pulse of the fediverse to identify issues, software requests and/or feature requests? Or is this all self reported?

#fediverse #mastodon #lemmy #peertube #misskey #microdotblog

Does anyone know of a survey that has been sent to node owners about their hosting experiences? Is anyone taking the pulse of the fediverse to identify issues, software requests and/or feature requests? Or is this all self reported?

#fediverse #mastodon #lemmy #peertube #misskey #microdotblog

Does anyone know of a survey that has been sent to node owners about their hosting experiences? Is anyone taking the pulse of the fediverse to identify issues, software requests and/or feature requests? Or is this all self reported?

#fediverse #mastodon #lemmy #peertube #misskey #microdotblog

Does anyone know of a survey that has been sent to node owners about their hosting experiences? Is anyone taking the pulse of the fediverse to identify issues, software requests and/or feature requests? Or is this all self reported?

#fediverse #mastodon #lemmy #peertube #misskey #microdotblog

Det finns förstås en hel del medier som har konton på någon instans i Fediversum och som postar länkar till deras nyheter. Kanske framförallt i Tyskland och USA. Men svenska medier finns det inte många. Ännu färre svenska medier har låtit sin sajt bli en instans i Fediversum trots att många använder publiceringsverktyg som faktiskt gör det lätt att bli […]

https://blog.zaramis.se/2024/07/27/medier-och-publiceringsverktyg-i-fediversum/

Fediversum består av en mängd olika instanser och användare som kan kommunicera med varandra oberoende av vilken instans de använder. Olika instanser kan ha en mängd olika programvaror, varje instans kan ha en egen eller så kan många instanser har samma.

https://blog.zaramis.se/2024/07/26/centraliserad-social-media-i-fediversum/

@manton I was here checking the FediDB website for an article and I noticed that #Microdotblog is number 6 in the Monthly Active Users list. Wow, that's something to celebrate. Congrats!

https://fedidb.org/software?page=1

@manton I was here checking the FediDB website for an article and I noticed that #Microdotblog is number 6 in the Monthly Active Users list. Wow, that's something to celebrate. Congrats!

https://fedidb.org/software?page=1

@manton I was here checking the FediDB website for an article and I noticed that #Microdotblog is number 6 in the Monthly Active Users list. Wow, that's something to celebrate. Congrats!

https://fedidb.org/software?page=1

@manton I was here checking the FediDB website for an article and I noticed that #Microdotblog is number 6 in the Monthly Active Users list. Wow, that's something to celebrate. Congrats!

https://fedidb.org/software?page=1

@manton I was here checking the FediDB website for an article and I noticed that #Microdotblog is number 6 in the Monthly Active Users list. Wow, that's something to celebrate. Congrats!

https://fedidb.org/software?page=1

can’t do much with it, but I can get #microdotblog to show up in #Fedicat

can’t do much with it, but I can get #microdotblog to show up in #Fedicat

can’t do much with it, but I can get #microdotblog to show up in #Fedicat

can’t do much with it, but I can get #microdotblog to show up in #Fedicat

@buttondown @J12t

Cool! Will check it out!

Strongly advise that you look at how the unofficial plugin for Ghost, and also separately how #MicroDotBlog who also offer newsletters (but only free ones) handles their ActivtyPub integration.

https://forum.ghost.org/t/i-wrote-a-mastodon-fediverse-activitypub-integration-for-ghost/37819

https://help.micro.blog/t/mastodon-and-activitypub/95

@buttondown @J12t

Cool! Will check it out!

Strongly advise that you look at how the unofficial plugin for Ghost, and also separately how #MicroDotBlog who also offer newsletters (but only free ones) handles their ActivtyPub integration.

https://forum.ghost.org/t/i-wrote-a-mastodon-fediverse-activitypub-integration-for-ghost/37819

https://help.micro.blog/t/mastodon-and-activitypub/95

@buttondown @J12t

Cool! Will check it out!

Strongly advise that you look at how the unofficial plugin for Ghost, and also separately how #MicroDotBlog who also offer newsletters (but only free ones) handles their ActivtyPub integration.

https://forum.ghost.org/t/i-wrote-a-mastodon-fediverse-activitypub-integration-for-ghost/37819

https://help.micro.blog/t/mastodon-and-activitypub/95

@buttondown @J12t

Cool! Will check it out!

Strongly advise that you look at how the unofficial plugin for Ghost, and also separately how #MicroDotBlog who also offer newsletters (but only free ones) handles their ActivtyPub integration.

https://forum.ghost.org/t/i-wrote-a-mastodon-fediverse-activitypub-integration-for-ghost/37819

https://help.micro.blog/t/mastodon-and-activitypub/95