rknuu

Also, ML is just statistics and calculus.

It's also worth noting the statistics are only for what you consumed. My profile at beehaw shows very different numbers than yours

https://beehaw.org/u/rknuu

Lemmy.ninja: 2 posts, 26 comments

Beehaw: 14 posts, 72 comments

Yep, but its only the Metadata[1]. I can't log in to your instance, but because your instance has consumed content from beehaw from my account I'm listed.

See https://lemmy.ninja/u/rknuu@beehaw.org

1. at least I haven't been able to share logins between instances yet.

While the breach is unfortunate, I always enjoy these kind of posts where a seemingly innocent exploration on what a site is doing and "what if" questioning becomes a chain of "holy crap, what did we just find". Just shows that your data can be just one curl statement away from being lost.

Hey people, we're trying to keep things tidy at beehaws technology community for reddit content and will be delisting this thread.

If you'd like to continue the conversation, feel free to join the megathread at https://beehaw.org/post/576904

Hey Beeple, since there's a common trend on the topics on (de)federation, we made a post to clarify what this means.

You can see the conversation over here: https://beehaw.org/post/615042

Unfortunately, the inconvenience is something of a catch 22. Do we allow everything through for the sake of convenience? What happens when extreme content that is NSFL gets posted? What happens when illegal content is federated, or hate speech that indicates action will be taken is made? What happens when you observe a pattern of this behavior from a common source? Content must be moderated for things to be "safe" and the rate that unsafe, nonaligned content was coming in wasn't sustainable.

Choosing to defederate wasn't taken lightly and it was done reluctantly. It was discussed for two days after observing systemic effects from those instances and after reaching out to the instance admins for alternatives.

I see you're posting not from a beehaw account, which means you likely haven't seen @Gaywallet@beehaw.org 's post on what it is to be a community and the framework to get there. This posts may help you understand this instances stance on things and what our instances users are hoping for is to build.

All in all, sorry you're not happy, but we're being careful for our community.

Unfortunately, defederating means the cord has been cut. This means we still have what was previously been posted, but all future content is bidirectionally blocked.

This is true, except for one element:

Fediverse should mean a user of any instance should be able to use any community the instance elects to federate with. Lemmy is open by design, but instances can just as easily switch that feature off and go to a allowlist method.

A commonly missed element with federation is that you federate with who you trust since you essentially mirror their content. It's less apparent with the lemmy migration, but mastodon used to caution its users to "join an instance that aligns with your preferences" for this reason.

Federation is really a philosophy about mutual trust, just like how email providers can block messages by user, instance, or domain.

Trust me, there's likely more gating present than you're aware of. Maybe not at lemmy.world (which as of this post is only blocking one site for reasons I won't mention), but this can get dark pretty quick if you leave things completely open.

Also on gitlab instances

https://docs.gitlab.com/ee/user/project/pages/

Really takes the complications out of hosting if you can build things as a JAM style site.

Hey beeple, we're trying to keep the discussion on reddit centralized on beehaw in the thread: https://beehaw.org/post/576904

Let's move over to there

Hey folks, with the surge of posts on reddit in recent days, we've been centralizing the discussion in our megathread.

Feel free to continue the chat over here:

https://beehaw.org/post/576904