Piero Bosio Social Web Site Personale

@hongminhee Authenticity matters. When I see slop I usually just ignore it, because reading it is like watching paint dry, and I think I am not alone in that.
You're basically the only person with whom I continue to communicate despite all of this.

@hongminhee

I'm writing this in English.

Do you, though? Your writing style was different in the past, so I am pretty sure that you now machine-translate, or perhaps use an LLM writing assistant.

To be honest, the non-slop version of you was much better.

@PortaFed

I have a couple of comments regarding the spec https://codeberg.org/portafed/portafed/src/branch/main/portafed-spec/spec.md

It contains a comparison with FEP-ef61, but it is not quite correct:

- FEP-ef61 identity is not actor-rooted. The closest equivalent of FEP-ef61 identity in normal ActivityPub is a server with a domain name. A single FEP-ef61 authority can manage multiple actor documents.
- FEP-ef61 does not lack a migration flow. Strictly speaking, it doesn't need one, because data is not attached to a server and can be continuously synchronized between multiple servers. But a more familiar migration flow is also possible via outbox export-import.

@lutindiscret

@vincent

curl -H 'Accept: application/ld+json; profile="https://www.w3.org/ns/activitystreams"' https://hacker.makeup/users/lorendb/statuses/47287792000

This returns an HTML document and status 500:

<h2 class="text-danger">An error occurred while processing your request.</h2>

    <p>
        <strong>Request ID:</strong> <code>00-d3d74c2ccd32f9ea714faa9aaa1cec25-5b77500b4a1fa1b9-01</code>
    </p>

@vincent It doesn't work for me. Every time my server attempts to fetch an announced post, hacker.makeup returns 500.

@smallcircles @eyeinthesky I like SocialHub and hope that it will remain online. But I haven't heard anything from its current admin for several months

In previous years, I published two "fediverse tech roadmap" posts:

- Fediverse tech roadmap 2024
- Fediverse tech roadmap 2025

However, I didn't publish such post this year because not much has happened in 2025. Many problems I talked about require complex solutions, but unfortunately proposed solutions are often very limited or lead to centralization. Or worse, there is no solution but only an imitation of work. I don't want to write about that.

I saw a thread today where ATProto ecosystem was compared to #ActivityPub. Things are happening in the Atmosphere, but not in Fediverse. MAU graphs are flat. What's going on?

There are multiple factors at play, but I think fake activity may be the biggest contributor. Trivial developments presented as breakthroughs. Features that already exist somewhere in Fediverse presented as new inventions. Vaporware. Specs written by people who have no idea how to implement them. Working groups that do nothing but meetings.

Real work is ignored, competent developers see that and quit.

We need to fix this.

For my part, I will continue to document #Fediverse development at @weekinfediverse. But this newsletter doesn't have much impact.

@jupiter_rowland What about OpenWebAuth? I thought it works as @oblomov describes

@hongminhee I don't know about Mobilizon but @linos considers adding related features to the Events FEP

https://codeberg.org/linos/fep/issues/18

@dyne The future is federated. Because we can have cryptographic identities in the Fediverse:

https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

@liaizon

No Friendica and Lemmy and Piefed do not have what is needed implemented yet.

What they don't have?

@julian There are several dozens of actively maintained ActivityPub implementations, I think it is not difficult to find two implementers among them, especially if they will be paid to implement a proposed change / extension (as we have seen with the E2EE proposal).

@slyborg @evan @connected-places @fediversereport @ArneBab @alexchapman

@slyborg @fediversereport

if there are other players of similar size in the committee to counterbalance a large player

Some of us knew that capture through W3C is only a matter of time, so we put a lot of effort to establish an alternative standardization process for Fediverse:

https://codeberg.org/fediverse/fep

@phnt @liaizon Maybe it can show quotes created on other platforms, but it doesn't allow creating quotes.

@liaizon Mastodon requires some kind of complicated "approval stamp" before showing a preview of a post. Most fedi developers ignore that

Mastodon got a working implementation of a thread collection (context). I'm adding it to the list of implementations in FEP-f228: https://codeberg.org/fediverse/fep/pulls/745

#fep_f228

RE: https://mastodon.social/users/MastodonEngineering/statuses/115854312836282687

Sucks, right, because on the theadiverse, you're not actually able to do that so easily.

Sounds like an unnecessary limitation of threadiverse software. Why limit a post to only one community? That doesn't make any sense.

The person who made the post with multiple mentions clearly did it intentionally, and I would do the same because for every topic I am interested in there are 4-5 groups on different servers.

Every mentioned person gets addressed

In most cases, this is what a user wants. Some platforms support silent mentions, though (Friendica, if I remember correctly).

hashtag / community tag soup

I think this should be viewed as a moderation problem, not a protocol problem. If you don't want to see mention soup, just limit the number of mentions per post on your instance.

@apps What kind of bridge?

Like this one? https://codeberg.org/silverpill/activity-connect

@morph Yes, I think convergence is possible.

@apps

@morph @apps I am open for a collaboration, but their implementation might be too different from what I am building. It may use Mastodon API instead of ActivityPub for client-server interactions