@scott I hope this mention works, as I failed to fetch your original post.

Progress for a FEP static site is being made, see here on SocialHub

Good morning Fediverse.

I think I came across a good example, why ActivityPub C2S is bad. Consider wanting to display an actor profile. Like mine. You will probably want to display if you are already following me or not or well if you requested to follow me and I didn't react.

To do this with C2S is complicated. One can work around its limitations. However, that's homework to understand how C2S is awful. For this homework problem, please consider at least 2 clients. Second part, a client without permanent storage.

See cattle_grid#147 for how something that has processing capabilities can get around it.

Good morning Fediverse.

It will soon be a criminal offense to set your Twitter account on fire. So please migrate to the Fediverse to post hot stuff or if you are hot. 🔥 Also if neither applies to you. We are welcoming. 🤩

The division of C2S and S2S feels to me like some people wrote it in this way because it's nice to read. Describe a server to server protocol by talking about what happens

• if a client sends a message to the server and the server then sends it to the next one
• and if a server receives a message from another server

I can see myself doing that. Then the genius manager decision happened: We can call this two protocols and claim twice the fame.

eggsarecheapenough.social your fedarated platform to get your egg free recipes.

Good morning Fediverse.

Business idea: Blockchain based egg substitutes.

You buy the coin. You get a recipe to make an egg free cake. We trust you to buy a new coin every time you use the recipe. Truth demands it.

I think that's one of the problems with how the Fediverse is currently designed on a technological level:

The number of reusable parts is fairly low. This means a lot of stuff keeps getting reinvented.

Simple answer: That's just how I understand the Fediverse works.

Complicated answer: I can imagine a reimplementation / respecification of the Fediverse, that mostly works by references, e.g. stores URIs. Then the content of an object is always fetched from the remote server instead of being passed along in a POST. Such a network would be able to take full advantage of transport layer caching, i.e. would probably generate a fraction of the traffic the current Fediverse does.

There are a lot of disclaimers one needs to attach to the complicated answer. The body of a POST request is fairly small. Authentication might have to be done with HEAD requests, etc...

The thing about storage duration is that it is a question that it is not related to HTTP. It is something that happens after transport.

In particular, one should consider that how long a post is stored depends on the situation. I would find it completely ok if your and rimu's server store the posts forever. They are necessary to make sense of your content.

The situation is different from someone who just follows me, and doesn't reply. Their interaction ended with reading. Thus they don't have a need to reference the post in the future.

Please note: These are thoughts. I do not have a good model on how storage duration should be determined.

AFAIK, ActivityPub is not an extension of HTTP. In particular, claiming that a Fediverse application should act like a HTTP cache (like described by RFC 9111 ) is odd. I like my layers to be separate. I dislike the conflation of everything the ActivityPub specification does. I wouldn't be surprised if somebody finds a sentence indicating, one must wear pants to use ActivityPub, in it.

Furthermore, I would claim that the HTTP Post request received in an inbox is discarded almost immediately in most applications. They discard the Create activity (maybe do some validation), and only keep some parts of the object. So no caching occurs on this level.

All in all, I would call this part of ActivityPub plain wrong. It's not even misleading.

Good morning Fediverse.

We still don't have a properties on ActivityPub activities and objects to indicate how long they can be cached in your ActivityPub Store.

Good morning Fediverse.

I wish there was a sign up with Fediverse. Even if you had to then click "Verify you are a cow".

Good morning Fediverse.

ActivityPub describes a platform with both a client and server part.

Challenge accepted: Undoing a Retweet is called to UnTruth.

We all have our naming schemes. First you add utils. Then you add helpers. Then tools. Then mystery. Then utils2. Then horror.

And some people claim naming is hard.

Good morning Fediverse.

If you like polling, let me introduce you to RSS.

I asked deepseek "is 37 prime?". It's reasoning includes that 2 and 3 are the only primes less or equal to 6.

Good morning Fediverse.

I'd like seamlessly working technology. You shouldn't really need to know if you are on the Fedi or not.

Hello #Mastodon!

#cow #switzerland #moo

Good morning Fediverse.

Just a side note, I'm quite happy with how roboherd works now. It's pretty much what I want to be able to build automated posting tools.