🫧 socialcoding.. @smallcircles@social.coop
Public

:blobhyperthink:

The current fediverse is an evolutionary dead-end for 2 reasons:

1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay.

2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out.

Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with.

To avoid fedi to become less and less attractive to newcomers, we must now consider:

“Why do we want to grow the open social web, and for whom?” -- @benBen Werdmuller

coding.social/blog/shared-owne

Image depicting a sticky note that reads "Cocreate inclusive social networks on basis of shared ownership, that benefit humanity and society at large".

Shared responsible social web ownership

We strive for an inclusive social web that is by the people and for the people. But how do we guarantee equity and shared ownership?

coding.social · Social coding commons

0
0
2

If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116109447243110037 on your instance and quote it. (Note that quoting is not supported in Mastodon.)

🫧 socialcoding.. @smallcircles@social.coop
Public

@thisismissemEmelia

@reiver@reiver ⊼ (Charles) :batman: it is a good question. It is also a question that is formulated from the perspective on how we currently see the AS/AP fediverse.

> I've seen an ongoing debate between "Note" versus "Article" in / .
> When is something a "Note"‽
> When is something an "Article"‽

The question makes sense from the notion of what the current is. It makes less sense from the context of AS/AP as described in the protocol specs.

Background to my post is this observation: social.coop/@smallcircles/1161

Then the answer to when is something a Note or an Article is: Always. Note is Note in ActivityStreams and Article is Article.

The question that you would be asking, if only we had a fediverse that followed the original promise of the open standards, is:

> "When is something a Note or an Article in a Microblogging domain?"

For instance.. types you have in any domain depend on your model preferences. Could be anything that serves needs of a solution.

0
0
1
🫧 socialcoding.. @smallcircles@social.coop
Public

@evanEvan Prodromou

> it's ok if you haven't heard of a REST API.

Well, you be you. I consider this a 'typical Evan remark' by now, dripping with sarcasm. It is a weird fit for someone who want to lead the efforts, I'd say.

Ah well. What I am talking about is architecture and design, and all the things that allow people to easily form a clear mental picture on how things fit together, wrap their head around the fediverse.

A HTTP interface is a very low-level thing, and clearly but one of the many moving parts that play a role in based solution development.

Never defining this well, and having the documentation be scattered all across the fediverse in 1,001 random locations doesn't help. Meanwhile the dev talk that is going on for years remains very inefficient due to endless Babylonian speech confusion.

social.coop/@smallcircles/1161

@cwebberChristine Lemmer-Webber @steveSteve Bate

0
0
0