What’s stopping me from doing this? Here we go:

I’m going to start an instance and federate with everyone who will allow it, which is most instances including this one, I believe.

Then I’m going to feed all that data into my new website, called Open Lemmy Stats, where anyone can query the user data ive accumulated. The homepage will be ripe with insights, leaderboards and all kinds of data on prolific users.

Additionally, I’ll display a snapshot/profile of a random user by feeding that users data to GPT4 to make inferences about the user’s political affiliations and display the results.

Worst of all, I’m not going to out my instance for everyone to know it as the one to defederate. In fact, I’m spinning up a few instances that will host innocuous communities that I plan to mod and support to give my instances cover for their true purpose: redundant fediverse datastreams for my site, Open Lemmy Stats.

I’ll also have a store where anyone can buy my collected fediverse data for a handsome sum.

Just kidding I’m not doing any of this. But someone absolutely will or already is working on it. They’ll make a good bit of money too, I’d bet.

This is inspired by a recent post on youshouldknow@lemmy.world where someone highlighted what kind of data instance admins have access to, even for users not on their instance.

I wanted to share this to start a discussion that I find interesting. I’m interested in your thoughts, or to hear more on why this may or may not be possible and if it is, maybe some ideas how to fix that? because obviously such a site would be problematic, but no doubt popular for oh so many reasons.

Edit: typo, I called admins adminis. Corrected.

Edit 2: wanted to credit the post I was referencing from YSK, here it is - https://lemmy.world/post/1033769

  • ColonelPanic@lemmy.mlEnglish
    5·
    1 year ago

    I’m pretty sure there is no particular reason why it’s done this way. It’s just the easiest method to coomunicate upvotes across different servers. There are already a lot of ideas for doing it differently or more efficient (e.g. vote aggregation) but that requires a more sophisticated architecture:

    • Vote aggregation also makes faking votes much more efficient and requires different detection methods. Of course, a spam server can also invent users or votes but it’s a bit more complicated.
    • Aggregation in any form can be hard to implement because it should be flexible enough to reduce load but not increase delay or make tracking a consistent state even harder. Finding the right configuration will be difficult and go through a lot of trial and error. Should be easier though now that more people are working on the code.
    • Keep in mind that Lemmy should also be able to communicate with other services across the Fediverse like Mastodon via ActivityPub. I’m not sure if there is something in the standard for message aggregation yet. It’s definitely being discussed because Mastodon, Pixelfed and Peertube all have or went thorugh the same growth problems as Lemmy in terms of scaling, spam and security concerns. If there’s a good solution it will likely come through the AP standard.