How is the database backend related to account migration?

I thought the problem was just that the objects ids are tied to the server. Just updating the ids to a new server doesn't work, as it wouldn't update the objects referencing the old id. Finally, you cannot update the objects referencing your old account's object, as they are distributed through the entire fediverse.

I want to use #Dolt as the backend for an Fediverse server populated entirely by #bots. The clone/pull semantics will help me keep an analytic copy of the DB.

If it goes well and I can open up the instance, branches will allow people to pull data on their own bots.

The primary goal: experiment with #fedilytics and #GenerativeAI.

Secondary goal: make progress on #Fediverse account portability.

@haxing_ninja

Alternatively, we could anchor a #fedilyticscharter on the consent-based communication model that @cwebber wrote for @spritelyinst

https://gitlab.com/spritely/ocappub

@hisham_hm @harlanh
#fedilytics

One option is to fork the #SlocanStatement and extend it with a section on analytic applications (contrasting with the current focus on transactional applications) to create a #fedilyticscharter

https://slocanstatement.org/

@hisham_hm @harlanh
#fedilytics

@hisham_hm @harlanh do either of those options feel viable to you?

What principles would you want to see in a #fedilyticscharter ?

Are there any good analytics focused code of conduct documents we could reference?

#fedilytics

@hisham_hm @harlanh not at all, thanks for the thoughtful comment.

Perhaps it would be productive to write a #fedilytics code of conduct? A #fedilyticscharter?

This would provide a nexus for debate about constitutes respectful data science on #Fediverse. Then practitioners can follow the code and we can call out companies that violate it.

There are already a few proposals like this, see https://writer.oliphant.social/oliphant/mastodon-handy-links-page#proposals-and-policies