I'd argue it's not a defeatist attitude, since they included the proper solution. To "need new laws". And that's how we generally do it. We disallow companies ripping off people, despite that maybe providing a better profit margin. We force water parks to implement some minimum standards to prevent accidents, despite not caring about safety would cost them less. I'd argue it's the same here. Just blaming it on the user isn't the proper thing to do. It just doesn't work for the general audience. Yes, you could do the water park inspection yourself, everyone could do some research which one is safe... And following that analogy everyone could get educated and use cash and GrapheneOS. But it's not the correct approach to the issue as a whole. And it doesn't really work.
h3ndrik
It kind of ties into their argument that it's more complex than that. And I'd agree. People always want simple answers to complex truths. Could very well be the case that you can't say if Brave is "the best" without analyzing the threat scenario. Or even after doing that you end up with a list of both pros and cons.
I think this is the issue here. OP is mixing content copyright with the GDPR. But the GDPR regulates personal data, not copyright on text. And that's what Reddit is trying to sell, the content of posts, not their user's personal data... So the GDPR doesn't apply to that. Hence Reddit say they aren't violating anything, because the copyright is in the ToS.
I think that's also my issue with the original letter. It wants to sound official and legalese, but it confuses several things. Intellectual property, copyright and privacy /data protection laws. I don't think the author(s) understand the GDPR. It includes a definition what personal data is. And the letter is mostly talking about something unrelated. Also there are additional requirements. For example identifiability. And they also fail to address any of that... I also don't like some of the things Reddit does, but I think this is just not a well reasoned argument. If I were in customer support or a lawyer, I'd brush it off, too.
Ah, that makes more sense. But the GDPR also doesn't regulate the actual content. It is about personal data. You can revoke consent processing that. But that doesn't necessarily touch copyright and the content of some text you licensed to someone. I think copyright is seperate. I mean it's a bit more complicated, there is some overlap...
Is that an EULA? I thought that was for buying software? I mean I'm pretty sure we have other forms of contracts here in the EU?! Like Terms of service.
Is that a known fact about Reddit's terms of service / "EULA", or something you made up?
And some EULA's are valid in the EU. Just not the American ones that you get to read after you bought something.
They're not infringing on your copyright, because you agreed to the following:
[...] you grant Reddit the following license to use that Content: When Your Content is created with or submitted to the Services, you grant us a worldwide, royalty-free, perpetual, irrevocable, non-exclusive, transferable, and sublicensable license to use, copy, modify, adapt, prepare derivative works of, distribute, store, perform, and display Your Content and any name, username, voice, or likeness provided in connection with Your Content in all media formats and channels now known or later developed anywhere in the world. This license includes the right for us to make Your Content available for syndication, broadcast, distribution, or publication by other companies, organizations, or individuals who partner with Reddit. You also agree that we may remove metadata associated with Your Content, and you irrevocably waive any claims and assertions of moral rights or attribution with respect to Your Content.
Maybe check for loose screws, that's one of the most common issues. And your Slicer settings, maybe it isn't saving or restoring the Bed Levelling data.
The answer is to create a short script that periodically queries the load, makes a decision and then triggers a reboot. Run it with a SystemD service and give it privileges to do the reboot. Useful languages for the script would be bash or python.
It's a silly way to handle it. You're probably quicker and better off solving the actual issue. Because it's not normal having this happen. Have a look at the logs, or install a monitoring software like netdata to get to the root of this. It's probably some software you installed that is looping, or having a memory leak and then swapping and hogging the IO until OOM kicks in. All of that will show up in the logs. And you'll see the memory graphs slowly rising in netdata if it's a leak.
journalctl -b -1 shows you messages from the previous boot. (To debug after you've pressed reset.) You can use a pastebin service to ask for more help if you can't make sense of the output.
Other solutions: Some server boards have dedicated hardware, a watchdog to detect something similar to that.
You can solder a microcontroller (an ESP32 with wifi) to the reset button and program that to be a watchdog.
Edit: But in my experience it's most of the times a similar amount of effort to either delve down and solve the underlying problem entirely and at once. Or writing scripts around it and putting a band-aid on it. But with that the issue is still there, and you're bound to spend additional time with it once side-effects and quirks become obvious.
And it's very centralized approach. IMHO typing in handles is a good approach for a decentralized platform. Also scanning QR codes on a conference instead of exchanging business cards. You don't need a seperate website for that. And noone wants to browse lemmyverse on a conference just to add someone (the issue they're obviously trying to solve with that.)
That article is a lot of words to say Mastodon now shows a QR code next to the handle.
Thanks! At the time of writing, I wasn't aware of the existence of piefed and sublinks. I read some of the Piefed blog posts today. Seems the author has some really good ideas how to address the shortcomings of the current approach. (Or what I view as shortcomings.) Splitting NSFW and NSFL is a really good start. Implementing better moderation tools is also a regularly requested feature. And judging by the other articles they mention, the project is closer aligned to my vision of a welcoming and inclusive platform. I'll definitely keep an eye on it. Hope it approaches a usable state soon.
I guess I have my answer, here. I'll wait until Piefed comes along and then use that. I'm somewhat optimistic about their claims. And if not, they included extensibility.
Haha, fool me once....
Fool me thrice and dabble in crypto...
(...And I'll use LibreWolf instead)