@rysiek @erosdiscordia @homegrown @Gargron

Imho there'ss dangerous underestimation of what FB / TW are capable of. All this public activity is not reflecting of their internal strategies. They won't show their cards until they're ready and can move fast. With their weight they can force themselves into prime positions. The battle won't be getting community consent, but tech molochs between themselves fighting it out.

Bluesky talks hybrid decentralization. They may just expand to that sector.

@leah I love it.

Made a post to our humane tech forum:

https://community.humanetech.com/t/educate-about-privacy-aspects-of-google-chrome-via-this-comic/5375

@hbenjamin @clacke @feditips

FYI @jonatasbaldin also maintains the #delightful libre hosting list.

Via the delighful club, see: https://delightful.club/delightful-libre-hosters/

@amolith @jalcine

Maybe some more interesting resources: https://codeberg.org/teaserbot-labs/delightful-funding/issues/1

@datatitian thank you, that is good to know. Need to to update @activitypub group then. And I will also edit the #ActivityPub application watchlist to reflect this change.

https://git.feneas.org/feneas/fediverse/-/wikis/watchlist-for-activitypub-apps

Hi there @datatitian

A question on #Guppe. The site appears to be down since 8 October. Is there an issue with the server, or is it discontinued?

https://github.com/wmurphyrd/guppe/issues/41

@clacke @stux @dajbelshaw @underlap

Yes, that would be good, except that they react while you - due to the char limit - are still typing the follow-up that gives the proper context.

@clacke @stux @dajbelshaw @underlap

Diagram of a super-forked discussion..

@clacke @stux @dajbelshaw @underlap

My experience is that once you have fork, then people jump in without reading the other forks. Discussions can become quite involved to manage if they branch out in big ways. I had an example some time ago where I had, I think, about 47 forks on my first toot.

@clacke @stux @dajbelshaw @underlap

I don't know about differences with other apps.

Some discussions, and often the better ones have replies in rather quick succession. If there'd be 5 min. intervals between posts there'd be much more likelihood for a discussion to be forked.

But maybe this is not how it works.. just not really clear to me.

@dajbelshaw @underlap @stux

Is there another place where there's a good functional description of the feature? I clicked through a bunch of issues and PR's, but..

Is there's a 5 min. waiting time before it is actually sent? Making back and forth much slower. Or are they directly federated, but because they are so recent, people will notice a malicious edit?

@SetecAstronomy @neauoire @theruran

I call this efficiency :D

@LibreSolutionsNetwork

Thanks. @jonatasbaldin did include that one, but with the name "librehosters". See https://codeberg.org/jonatasbaldin/delightful-libre-hosters#groups-of-libre-hosters

@fdroidorg

Oh oh, seeing the results I hope the next major release won't be a Termux-based CLI 😜

@jerger do you mean Clojure the language? Wouldn't have thought. Do you have a link, or was this just in jest? :)

@Zergling_man @ademalsasa @feneas

I saw in the annoucement:

"Due to recent lack of activity within the association, issues maintaining the current services and lack of new committee members wanting to step up, the members of Federated Networks Association ry (Feneas) have decided to dissolve the association."

Which is a summary of the causes, but not a retrospective that is helpful to other similar initiatives or future ones that want to follow up.

But maybe I missed other announcements.

@ademalsasa it is very sad that this happened, of course.

I wonder if @feneas will publish a kind of retrospective as to why they came to the current point.

Is it just that people didn't want to donate/fund enough? Or were there too many competing organizations, is the federated universe too fragmented? Did it require too much time to do advocacy for #Feneas on ongoing basis? Were they positioned well enough for people to understand how they fit into the #Fediverse landscape?

@rysiek it is not community hosting that I am most concerned about, when it comes to fedi.

It is grassroots-community-based open standard specs and the evolution thereof.

Here Moxie has a point. After AS/AP became W3C recommendations, there's been very little in terms of follow-up. Interop mostly involves looking in foreign codebases and trying to find a good expertised dev to explain the undocumented details.

And with every new app + custom choices, the interop landscape becomes more complex

@maswan @eaon @meejah @TerryHancock @rysiek

I also wrote on that in this other thread:

https://mastodon.social/@humanetech/107587010613415692