• 2 Posts
  • 59 Comments
Joined 3 years ago
cake
Cake day: July 17th, 2023

help-circle

  • One big reason why not to buy a Rqspberry Pi for Self Hosting is the price. If you want to run more heavy services (like jellyfin can be), you need the Pis with 8GB of RAM. Though those where already expensive before the sharp rise is RAM pricing. When you include a fitting power supply and a small cooler with fan (so that you don’t run into thermal throttle fast) you are probably already at like 110€ at least. For that money you can also get a used mini PC (those that companies use for their employees), that already has more power and offers better upgradebility (RAM, storage). Also for some services you might run into the problem, there is no version build for ARM devices (though that happens very rarely nowadays).

    Though with the RAM pricing problem every computing device gets more expensive. Just include such mini PCs into your comparison to make a good decision.



  • Visa free programms are not just a way to get in more tourists. They are often part of international treaties (which often contain way more things with bigger importance than overtourism) or bilateral agreements, which guarantee the same thing in the other country. If a country limits the entry of citizens from another country, that country probably will alao limit down its own visa free programm for citizens of the first country. The countries suffering from overtourism often don’t have the treaty freedom to so this or don’t want to limit their own citizens travels.

    So Visa agreements are mostly part of international politics. Changing that does change a lot more than just tourism, which is often not worth it.



  • Mhh, you are probably right. I’m really hesitant to invest more time into troubleshooting tailscale. My own tailscale connections at home are stable, and for troubleshooting at my family member I always have to drive and setup my notebook there.

    Maybe I could try to setup wireguard directly in the fritzbox router at my family member. That might need less maintenance as running tailscale in a docker container, as it would remove the wireguard connection out of the NAS itself.

    Opening a port directly gives me kind of an ick, because I don’t want to fiddle too much with the family members network. If something happens with it, I will be the one troubleshooting it, and I don’t need more work currently.


  • So Tailscale connection instability is not common? I don’t like debugging this, since the NAS is remote and I don’t have much time going to the family member again and again for this. It definitely is something on the remote site, since the tailscale connections at my home are stable.

    I will definitely have a look at Kopia. I was in search of a good open source backup solution, since borg also has its flaws. I will check it out, when I setup the remote NAS again (as I also want to put bigger disks in it)



  • A server is measured by its availability. To read content from it, it has to be available. While everyone could use a dedicated always-on device, thats not really the situation you are describing. So you would run the software on your phone/notebook/PC. Those are not always available on the internet.

    If you post something to your 50 recipients (as you stated in another comment), they can only read it, if both of you are online. For asynchronous communication (like a post typically is), that is a lot to ask. Especially, if you want to have features like comments, that all your recipients can see.

    If you move away from the typical social media principle, then you can have truly decentralized messengers. I think, that already exists.

    Another problem with any decentralized approach is how to handle content moderation. It is necessary, since humans are messy. The more decentralized a system is, the harder it becomes to moderate. For example: How would you stop CSAM to be proliferated through it? Or even stop it to being send to you? If the software has some automatic replication feature to enhance availability, then this problem gets worse. Lemmy has had its own attacks with CSAM being posted to many servers. That can get you into legal trouble very fast.






  • including those laid off, since some are still hoping to find jobs elsewhere at the WMF, and others are depending on severance pay

    Am I too european to understand this? If they “get jobs elsewhere at the WMF” this is not a layoff, is it? I know the US has nearly no worker protections, so maybe that makes it a layoff. Do they need to interview for these positions again?

    If this were something other than Community Tech, maybe I could convince myself it’s all just a coincidence. But the WMF has been on a generally upward trajectory at avoiding decisions that will piss off the entire community. “Don’t disband CommTech” might as well be the "don’t mess with the pancreas"of WMF governance. The only explanation for the WMF doing this—not just reörganizing but outright laying off the team—is that they are so determined to prevent the union from becoming official that they are willing to risk the massive community blowback (which, from a corporate-brain point of view, is a greater downside than the five people left jobless).

    That paragraph I don’t understand. Why is union busting the only explanation?

    From one of the comments of that Reddit thread:

    the union was apparently formed exactly 90 days prior to the layoff announcement; under california state law (where they are located) “a termination within 90 days of protected union activity creates a rebuttable presumption that the termination was illegal retaliation”

    I think that is an interesting detail here, though I have not bothered to go through the sources for this.








  • You don’t want the target site to have your identity (nor your age, only the information, that you are old enough). Though you also don’t want to tell the government, which age restricted sites you are using (imagine the government getting having a list of all your porn site usage).

    There are ways to do this, though the implementations in most countries don’t adhere to these requirements (either by giving your identity to the target site or the government collecting your usage data).

    I might remember that wrong, but I think I heard a proposal in germany, that would fit the requirements. Something about, that you can generate up to 30 cryptographically signed tokens (don’t know why the limit was included) from the government, that the target site can use to verify their age limit. No communication between the government and the site. Though I don’t know, if that proposal got any track.

    We will probably also see, that nearly all websites will need age verification, since there is a lot, that is not suitable for very young children. A bit older children and teenagers will also have to use that verification workflow quite often. Adults way more often. That is a lot of friction easily avoided with a VPN.

    And of course the governments would also need to block every site, that does not comply to the local regulations. Different worldviews make this impossible. A small blog about queer education in europe would need to implement age verification, because the US and russia hate queer people.

    It’s a big clusterfuck