Yeah, I’m just split between that or an odroid hc4. I wouldn’t even need to buy a case for it.
SDET
Yeah, I’m just split between that or an odroid hc4. I wouldn’t even need to buy a case for it.
What model pi? How responsive do you find it?
I’m also in the market for this.
I’m considering setting up a raspberry pi4 nas, and would love to hear pros and cons from people with experience on the matter.
I assume there are faster solutions, but I think it should meet my needs well
Wow thanks for such a verbose post.
That’s given me a lot to chew on
The tools are lacking, as you said.
This post is not about how things should be. It’s not about how things might be one day. It’s about how they are right now
I have absolutely seen some highly upvoted pillars of salt over there.
The intent of Beehaw appears to be giving people a safe place that they can return to, but they can venture out just as well. That ideal does not mesh with an allowlist. The goal doesn’t appear to be to curate a specific experience, it is to block bad actors from harassing Beehaw’s users on Beehaw’s hosted communities.
With this in mind, I think it absolutely does make sense for lemmy to include permissions that restrict what foreign users can do vs what local users can
There exists no means to be private without defederating from literally every other instance.
Sure, and I should’ve been more clear and said people need to understand what the Fediverse is.
This is, ultimately, about what federation means and how this platform operates. Its deficiencies, and the way things work currently to address those deficiencies. What I have posted is just as true for kbin as it is for lemmy.
When/if refederation happens, the comments lost to the abyss will stay lost to the abyss. The source of truth will not update based on the past updates of a formerly defederated instance to my understanding
People need to understand what lemmy is. This is not monolithic social media like facebook or reddit. People need to understand that, or the mismatch between how they think it works and how it actually works is going to cause a lot of mental anguish that could be avoided.
As they say in software development, 8 hours of debugging can save you from one hour of reading the manual.
When a Lemmy.World user posts to a Beehaw community right now, it updates the cached community that Lemmy.World stores. Beehaw has defederated with them, so the “source of truth” (hosted by Beehaw) never updates. The source of truth is what updates other federated instances. As a result, someone on startrek.website, for example, will not see posts made by lemmy.world users to beehaw communities. The only people who can see what lemmy.world users post to beehaw right now are other lemmy.world users.
It’s not my intent to determine how things “should” work.
This is how things DO currently work.
I don’t think that assertion is based in reality. A server has to be hosted somewhere, and admins will generally choose to uphold those local regulations for the sake of their instance’s own longevity. Federation has never meant that you communicate with literally every other instance. This isn’t Tor where nodes pass along communications that don’t directly involve themselves.
This isn’t handwringing, though I can understand why it might come off that way. This is simply mulling over how things “actually work” in the fediverse as opposed to how people believe it works. I believe that many people have a fundamental misunderstanding of what this software is and how it works. This is an educational issue that we have an opportunity to begin sorting out
In addition, my scenario of instance users subscribing to illegal content will still be valid even with moderation tools. The only way to stop that currently is defederation with instances hosting illegal content.
The answer to your question is yes