TheFederatedPipe

joined 4 months ago
sorted by: new top controversial old
Shouldn't all ActivityPub servers implement all objects and leave it to the client? in c/fediverse@lemmy.world
[–] TheFederatedPipe@fedia.io 2 points 1 week ago

That is a fair point, and I don't have the answer. Maybe use technics that @peertube@framapiaf.org uses like torrenting (or another way of decentralized storage), I guess you could use a cdn/object bucket?

Shouldn't all ActivityPub servers implement all objects and leave it to the client? in c/fediverse@lemmy.world
[–] TheFederatedPipe@fedia.io 12 points 1 week ago (1 children)

Mbin is so cool, it's what I'm using.

Shouldn't all ActivityPub servers implement all objects and leave it to the client? in c/fediverse@lemmy.world
[–] TheFederatedPipe@fedia.io 3 points 1 week ago

Agree with the article, same idea. Despite the opinions each one of us may have regardless #nostr and #bluesky, they have cool ideas we could borrow.

Shouldn't all ActivityPub servers implement all objects and leave it to the client? in c/fediverse@lemmy.world
[–] TheFederatedPipe@fedia.io 4 points 1 week ago (2 children)

I haven't developed anything with #ActivityPub, but have read a little bit of the spec. I would love to hear the take from developers making use of it.

(Sorry for the mention in any case)

@silverpill@mitra.social

@hongminhee@fosstodon.org

@dansup@mastodon.social

@thisismissem@hachyderm.io

58
Shouldn't all ActivityPub servers implement all objects and leave it to the client? (fedia.io)
 

Wouldn't that be better? Let me see if I can explain what I mean. Here on the fediverse each server is kind of restricted to what the user can post.

@Mastodon@mastodon.social is for notes

@pixelfed@pixelfed.social for photos (wouldn't be surprised if it used a note too)

Lemmy only for article objects.

Peertube for videos.

You get the idea.

This way of developing the #fediverse where each server only receive one kind of the objects accepted by #ActivityPub makes it more fragmented it, right? A server should send and receive all kinds of objects and should be up to the client to how to processes those objects.

If an user wants an Instagram-like app just create an account on any service and use and app with that UI, of lager they wanted to see more kinds of objects they should just use another client that supports Note, Article, etc. with the same account on the same server.

Ideally all server should have a shared API.

This fixes #fragmentation, the need to have multiple accounts if you are into multiple kinds of objects/content.

Lemmy User Feedback and Improvement Thread: Share Your Complaints, Suggestions, and Ideas in c/fediverse@lemmy.world
[–] TheFederatedPipe@fedia.io 2 points 1 month ago

Yeah, it sucks. But I think that at a certain point it will need to happen if we want to make ActivityPub better with better portability.

Lemmy User Feedback and Improvement Thread: Share Your Complaints, Suggestions, and Ideas in c/fediverse@lemmy.world
[–] TheFederatedPipe@fedia.io 1 points 1 month ago (2 children)

I think there's a FEP that could (or fixes) this. To my understanding ID can be any URI, so there are better ways. I guess it's hard because it would brake a lot of stuff or how mastodon is build.

ActivityPods 2.0 is out! in c/fediverse@lemmy.world
[–] TheFederatedPipe@fedia.io 10 points 1 month ago

For a second I thought the ActivityPub specification got updated.

When is a new update to ActivityPub coming? in c/fediverse@lemmy.world
[–] TheFederatedPipe@fedia.io 13 points 4 months ago* (last edited 4 months ago)

Literally one of the reason for the existence of this thread.

43
When is a new update to ActivityPub coming? (fedia.io)
 

I'm trying to learn more about the protocol, and after years of being around in the fediverse there's obviously areas where the protocol could improve. I was reading some of the fep documents and there are really good proposals. How long for these to be part of the protocol? Last update was 2018.