@tiotasram interesting ideation topic.

Not sure if I have time to respond today, but just wanted to note that this aligns with the general interest and focus of Social experiences (SX) at https://coding.social which I elaborate on as a hobby, and perhaps one day my job.

The disadvantage of microblogging is how ephemeral it is, but the advantage is reach. Should you be interested you are welcome to share results on the social coding forum, which serves as a note-taking tool: https://discuss.coding.social

Also there's the fediverse-ideas repository on codeberg at: https://codeberg.org/fediverse/fediverse-ideas/issues

#SX #SocialCoding #SocialWeb #ActivityPub

@aslakr @leanderlindahl

🤔 Off-topic reformulation of the procedure in general terms.. In areas where PeerTube isn't post-facto interop leader itself, it should hope a reasonably broadly adopted #FEP consensus exists, or follow the post-facto leader in that particular application area and accept the upstream dependency to that part of the #ActivityPub specs the leader owns (and hopefully cares for, beyond their own needs, with good design and documentation).

@_elena @evan @Sascha

It’s not about features. It’s about culture.

#ActivityPub comes out of the #openweb tradition.

#Bluesky comes out of a split lineage - #openweb roots, shaped by #dotcons incentives, with an #encryptionist upbringing.

@_elena thank you for sharing the article.

The same considerations should be honestly made for the #ActivityPub fediverse as well. So we may address them in time. Not all is well. I am writing a blog post on open standards divergence and increasing unattractiveness of an ecosystem that hems itself into a straitjacket of narrow application areas, by the protocol decay we allow to fester. Combined with inadequate work methods to reconcile the tech debt that this incurs. We must go "back to standards" or have an ecosystem based on enabling technologies that are increasingly unattractive to adopt.

RE: https://mas.to/@Aubreader/116330793703168577

This article is a must read.

An excerpt: “Why would anyone fund an Atmosphere project if #Bluesky, with $100 million in the bank, might ship a competing feature at any moment? Why would a founder bet their career on this ecosystem? The presentation didn't just hurt Graze. It made the entire ecosystem look unfundable.”

Why do I keep bringing up this topic?

Because #ATproto is often put in the same category as #ActivityPub (“open protocols yay”) but I strongly disagree with that stance

@_elena thank you for sharing the article.

The same considerations should be honestly made for the #ActivityPub fediverse as well. So we may address them in time. Not all is well. I am writing a blog post on open standards divergence and increasing unattractiveness of an ecosystem that hems itself into a straitjacket of narrow application areas, by the protocol decay we allow to fester. Combined with inadequate work methods to reconcile the tech debt that this incurs. We must go "back to standards" or have an ecosystem based on enabling technologies that are increasingly unattractive to adopt.

RE: https://mas.to/@Aubreader/116330793703168577

This article is a must read.

An excerpt: “Why would anyone fund an Atmosphere project if #Bluesky, with $100 million in the bank, might ship a competing feature at any moment? Why would a founder bet their career on this ecosystem? The presentation didn't just hurt Graze. It made the entire ecosystem look unfundable.”

Why do I keep bringing up this topic?

Because #ATproto is often put in the same category as #ActivityPub (“open protocols yay”) but I strongly disagree with that stance

@nw @phanpy

Not direct suggestions, but lists..

https://delightful.coding.social

#ActivityPub #fediverse