I have an idea for an ActivityPub project. I'm getting distracted from my original projects again ​:neofox_googly_shocked:​
(I think the chain now is Wyvern Ref -> Areon Ref -> Isometric Map Generator -> Corveon Ref -> Spooky Avatar -> Birb Emojis -> ActivityPub project)

@volpeon The Wyvern Ref -> Areon Ref -> Isometric Map Generator -> Corveon Ref -> Spooky Avatar -> Birb Emojis -> ActivityPub project pipeline

I have an idea for an ActivityPub project. I'm getting distracted from my original projects again ​:neofox_googly_shocked:​
(I think the chain now is Wyvern Ref -> Areon Ref -> Isometric Map Generator -> Corveon Ref -> Spooky Avatar -> Birb Emojis -> ActivityPub project)

So here's the idea I'm brainstorming. It's very rough so don't expect perfection right off the bat, please.

What if we had something like PDSes here, too? A server which hosts all of your data, i.e. the AP objects and activities that are generated whenever you interact with the network. Instances wouldn't hold your identity; instead when you register on an instance you tell it about your PDS and then the instance uses that as the database for all your stuff.

What would this solve?
- You could be part of multiple communities (instances) with a single identity. This is more natural with how things work everywhere else.
- You could move instances and not lose anything provided they handle AP activities the same way.
- Instance admins would be still be able to kick you off their instance, so moderation remains intact.
- You would be protected against situations like an instance going offline all of a sudden because all your data would be with you.
- Activities point to the PDS server instead of the instance, so moving somewhere else wouldn't require updating databases in all peers via a Move activity.

Caveat:
- You would still be fucked if the PDS goes offline.

There's a shitload of more things to consider, and I'm also not perfectly knowledgeable about AP so I may have the wrong idea about some things. But I feel this would be a path worth pursuing.
These are just some quick thoughts. I'm begging you to not get hung up on details. This happens so often when I share ideas like these and it's killing me every time.

So here's the idea I'm brainstorming. It's very rough so don't expect perfection right off the bat, please.

What if we had something like PDSes here, too? A server which hosts all of your data, i.e. the AP objects and activities that are generated whenever you interact with the network. Instances wouldn't hold your identity; instead when you register on an instance you tell it about your PDS and then the instance uses that as the database for all your stuff.

What would this solve?
- You could be part of multiple communities (instances) with a single identity. This is more natural with how things work everywhere else.
- You could move instances and not lose anything provided they handle AP activities the same way.
- Instance admins would be still be able to kick you off their instance, so moderation remains intact.
- You would be protected against situations like an instance going offline all of a sudden because all your data would be with you.
- Activities point to the PDS server instead of the instance, so moving somewhere else wouldn't require updating databases in all peers via a Move activity.

Caveat:
- You would still be fucked if the PDS goes offline.

There's a shitload of more things to consider, and I'm also not perfectly knowledgeable about AP so I may have the wrong idea about some things. But I feel this would be a path worth pursuing.
These are just some quick thoughts. I'm begging you to not get hung up on details. This happens so often when I share ideas like these and it's killing me every time.

So here's the idea I'm brainstorming. It's very rough so don't expect perfection right off the bat, please.

What if we had something like PDSes here, too? A server which hosts all of your data, i.e. the AP objects and activities that are generated whenever you interact with the network. Instances wouldn't hold your identity; instead when you register on an instance you tell it about your PDS and then the instance uses that as the database for all your stuff.

What would this solve?
- You could be part of multiple communities (instances) with a single identity. This is more natural with how things work everywhere else.
- You could move instances and not lose anything provided they handle AP activities the same way.
- Instance admins would be still be able to kick you off their instance, so moderation remains intact.
- You would be protected against situations like an instance going offline all of a sudden because all your data would be with you.
- Activities point to the PDS server instead of the instance, so moving somewhere else wouldn't require updating databases in all peers via a Move activity.

Caveat:
- You would still be fucked if the PDS goes offline.

There's a shitload of more things to consider, and I'm also not perfectly knowledgeable about AP so I may have the wrong idea about some things. But I feel this would be a path worth pursuing.
These are just some quick thoughts. I'm begging you to not get hung up on details. This happens so often when I share ideas like these and it's killing me every time.

@volpeon i mean isn't that just how AT&bsky works?

i think my least favourite thing about AT is how the AppView can impose its own limitations on what data it will show, but you can just skip the AppView and ask the PDS directly which will give you all the data without any restriction, yknow the whole reason private accounts don't exist on bsky

i think a more ideal approach would be for a PDS equivalent to only respond to a nominated instance, and any request for user data would be forwarded to that instance which will be able to enforce authfetch, private accounts etc

So here's the idea I'm brainstorming. It's very rough so don't expect perfection right off the bat, please.

What if we had something like PDSes here, too? A server which hosts all of your data, i.e. the AP objects and activities that are generated whenever you interact with the network. Instances wouldn't hold your identity; instead when you register on an instance you tell it about your PDS and then the instance uses that as the database for all your stuff.

What would this solve?
- You could be part of multiple communities (instances) with a single identity. This is more natural with how things work everywhere else.
- You could move instances and not lose anything provided they handle AP activities the same way.
- Instance admins would be still be able to kick you off their instance, so moderation remains intact.
- You would be protected against situations like an instance going offline all of a sudden because all your data would be with you.
- Activities point to the PDS server instead of the instance, so moving somewhere else wouldn't require updating databases in all peers via a Move activity.

Caveat:
- You would still be fucked if the PDS goes offline.

There's a shitload of more things to consider, and I'm also not perfectly knowledgeable about AP so I may have the wrong idea about some things. But I feel this would be a path worth pursuing.
These are just some quick thoughts. I'm begging you to not get hung up on details. This happens so often when I share ideas like these and it's killing me every time.

@volpeon https://activitypods.org is a thing

So here's the idea I'm brainstorming. It's very rough so don't expect perfection right off the bat, please.

What if we had something like PDSes here, too? A server which hosts all of your data, i.e. the AP objects and activities that are generated whenever you interact with the network. Instances wouldn't hold your identity; instead when you register on an instance you tell it about your PDS and then the instance uses that as the database for all your stuff.

What would this solve?
- You could be part of multiple communities (instances) with a single identity. This is more natural with how things work everywhere else.
- You could move instances and not lose anything provided they handle AP activities the same way.
- Instance admins would be still be able to kick you off their instance, so moderation remains intact.
- You would be protected against situations like an instance going offline all of a sudden because all your data would be with you.
- Activities point to the PDS server instead of the instance, so moving somewhere else wouldn't require updating databases in all peers via a Move activity.

Caveat:
- You would still be fucked if the PDS goes offline.

There's a shitload of more things to consider, and I'm also not perfectly knowledgeable about AP so I may have the wrong idea about some things. But I feel this would be a path worth pursuing.
These are just some quick thoughts. I'm begging you to not get hung up on details. This happens so often when I share ideas like these and it's killing me every time.

@volpeon there's already https://activitypods.org/ (not very good), portable objects and C2S FEPs (not very good) and kopper's ois (link somewhere on codeberg)

@volpeon https://codeberg.org/outpost/ois there was also another project similar to ois, but i don't remember what that was

@tay

i mean isn't that just how AT&bsky works?

i think a more ideal approach would be for a PDS equivalent to only respond to a nominated instance, and any request for user data would be forwarded to that instance which will be able to enforce authfetch, private accounts etc

So here's the idea I'm brainstorming. It's very rough so don't expect perfection right off the bat, please.

What if we had something like PDSes here, too? A server which hosts all of your data, i.e. the AP objects and activities that are generated whenever you interact with the network. Instances wouldn't hold your identity; instead when you register on an instance you tell it about your PDS and then the instance uses that as the database for all your stuff.

What would this solve?
- You could be part of multiple communities (instances) with a single identity. This is more natural with how things work everywhere else.
- You could move instances and not lose anything provided they handle AP activities the same way.
- Instance admins would be still be able to kick you off their instance, so moderation remains intact.
- You would be protected against situations like an instance going offline all of a sudden because all your data would be with you.
- Activities point to the PDS server instead of the instance, so moving somewhere else wouldn't require updating databases in all peers via a Move activity.

Caveat:
- You would still be fucked if the PDS goes offline.

There's a shitload of more things to consider, and I'm also not perfectly knowledgeable about AP so I may have the wrong idea about some things. But I feel this would be a path worth pursuing.
These are just some quick thoughts. I'm begging you to not get hung up on details. This happens so often when I share ideas like these and it's killing me every time.

So here's the idea I'm brainstorming. It's very rough so don't expect perfection right off the bat, please.

What if we had something like PDSes here, too? A server which hosts all of your data, i.e. the AP objects and activities that are generated whenever you interact with the network. Instances wouldn't hold your identity; instead when you register on an instance you tell it about your PDS and then the instance uses that as the database for all your stuff.

What would this solve?
- You could be part of multiple communities (instances) with a single identity. This is more natural with how things work everywhere else.
- You could move instances and not lose anything provided they handle AP activities the same way.
- Instance admins would be still be able to kick you off their instance, so moderation remains intact.
- You would be protected against situations like an instance going offline all of a sudden because all your data would be with you.
- Activities point to the PDS server instead of the instance, so moving somewhere else wouldn't require updating databases in all peers via a Move activity.

Caveat:
- You would still be fucked if the PDS goes offline.

There's a shitload of more things to consider, and I'm also not perfectly knowledgeable about AP so I may have the wrong idea about some things. But I feel this would be a path worth pursuing.
These are just some quick thoughts. I'm begging you to not get hung up on details. This happens so often when I share ideas like these and it's killing me every time.

So here's the idea I'm brainstorming. It's very rough so don't expect perfection right off the bat, please.

What if we had something like PDSes here, too? A server which hosts all of your data, i.e. the AP objects and activities that are generated whenever you interact with the network. Instances wouldn't hold your identity; instead when you register on an instance you tell it about your PDS and then the instance uses that as the database for all your stuff.

What would this solve?
- You could be part of multiple communities (instances) with a single identity. This is more natural with how things work everywhere else.
- You could move instances and not lose anything provided they handle AP activities the same way.
- Instance admins would be still be able to kick you off their instance, so moderation remains intact.
- You would be protected against situations like an instance going offline all of a sudden because all your data would be with you.
- Activities point to the PDS server instead of the instance, so moving somewhere else wouldn't require updating databases in all peers via a Move activity.

Caveat:
- You would still be fucked if the PDS goes offline.

There's a shitload of more things to consider, and I'm also not perfectly knowledgeable about AP so I may have the wrong idea about some things. But I feel this would be a path worth pursuing.
These are just some quick thoughts. I'm begging you to not get hung up on details. This happens so often when I share ideas like these and it's killing me every time.

So here's the idea I'm brainstorming. It's very rough so don't expect perfection right off the bat, please.

What if we had something like PDSes here, too? A server which hosts all of your data, i.e. the AP objects and activities that are generated whenever you interact with the network. Instances wouldn't hold your identity; instead when you register on an instance you tell it about your PDS and then the instance uses that as the database for all your stuff.

What would this solve?
- You could be part of multiple communities (instances) with a single identity. This is more natural with how things work everywhere else.
- You could move instances and not lose anything provided they handle AP activities the same way.
- Instance admins would be still be able to kick you off their instance, so moderation remains intact.
- You would be protected against situations like an instance going offline all of a sudden because all your data would be with you.
- Activities point to the PDS server instead of the instance, so moving somewhere else wouldn't require updating databases in all peers via a Move activity.

Caveat:
- You would still be fucked if the PDS goes offline.

There's a shitload of more things to consider, and I'm also not perfectly knowledgeable about AP so I may have the wrong idea about some things. But I feel this would be a path worth pursuing.
These are just some quick thoughts. I'm begging you to not get hung up on details. This happens so often when I share ideas like these and it's killing me every time.

@volpeon@icy.wyvern.rip I guess another advantage of this is that pure PDSes are somewhat less expensive/involved to host than a full instance? Since they'd only be concerned with their own data and not handling AP requests, traffic, etc from a ton of other servers.

@volpeon@icy.wyvern.rip The year is 2030. Bsky continues deteriorating. Every day somebody posts there that "mastodon is too hard because I have to pick and instance and PDS, whatever that is"