rknuu
Just your run of the mill dev and data scientist.
Banner credit: wanella
- 14 Posts
- 48 Comments
It’s also worth noting the statistics are only for what you consumed. My profile at beehaw shows very different numbers than yours
Lemmy.ninja: 2 posts, 26 comments Beehaw: 14 posts, 72 comments
Yep, but its only the Metadata. I can’t log in to your instance, but because your instance has consumed content from beehaw from my account I’m listed.
8·1 year agoThis is where the fediverse is both powerful and a bit of a challenge to moderate. The best way to deal with these things is to be vigilant in sharing information that supports the contrary; since there’s no real way to filter out bad information unilaterally (and even if so, I’d find that to be a dangerous precedence as who constitutes “good” and “bad” across the federated instances).
While the post was quite toxic towards the admins, the opinion of the user was done in what I see as exasperation at the situation without necessarily understanding the logic of these choices made for the beehaw instance as a whole; so there’s an opportunity to redirect them to a different path or understanding. I’m aware that there are likely several others who share this opinion and may learn from this (just taking a moment to review some of the kbin.socal and lemmy.world threads on this subject shows this as a common concern). Moderation and intervention is more about systemic patterns of an individual’s behavior that clashes with a community’s ethos. Following the ethos of our admins, we take a measured response based on history and engagement.
As for now, things appear to have resolved through disengagement, so mission accomplished: we got the information out there and addressed their concern (and possibly inform other lurkers and the various instances that federate with us on this point).
I don’t know why, but this article made me think of blind drive, the game
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.
7·1 year agoOn a semifrequent basis, we open up a thread to see what interest are present. We just had another round recently:
Hey people, we’re trying to keep things tidy at beehaws technology community 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
There was an unfortunate email glitch where if your username was already present in the instance, it would silently deny your application, and the beehaw admins would be none the wiser. See https://beehaw.org/post/562922
Additionally, there has been some issues with the beehaw’s email provider that has recently been fixed and the backlog has started to decrease. See https://beehaw.org/post/604680
Can you explain what you mean by bad experience? I can see how the experience on beehaw would be different from other instances, but what is explicitly bad about it?
- The account registration process exists to weed out bots. We’re not the only ones to implement this kind of sign up. An essay really isn’t required, unless you misunderstood the purpose of the sign up.
- We haven’t left the fediverse, posts and comments to and from beehaw still flow to the vast majority of instances, and we do wish to rejoin these two specific instances at a later date once we have the right processes and tools to work though the problems we encountered.
- If the admins were cocky or snobby, they would have defederated without any form of announcement or transparency on what was being done and why.
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
This is also correct, and we’re hoping we can do so sooner rather than later. 😉
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.
We’re open by default because we have the belief that you have a right to demonstrate you can be a good actor. @Gaywallet@beehaw.org details this in the philosophy of our community.
Trust me when I say defederation was the last choice on the radar for this situation.
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
There are a few other reasons I know of:
- Archive.org links tend to pass paywall sites, so it provides opportunity to view Covent without that hiccup.
- Digital sustainability is really hard. Many links have a short lifespan, or articles are “evergreen” and end up changing from when the post was made. This creates a snapshot to prevent both these issues.
- Prevents the “hug of death”, when an unsuspecting site goes from 1k visitors a day to 500k. Not all sites are resilient to that kind of traffic shaping.
Agree that it does bypass the good sites, but some have concerns over these points.
That said, you’re placing your faith in your archive site to stay up and continue to function.
Also, ML is just statistics and calculus.