Fresh and most up to date kinoite installation last week, based on fedora 39. The problem is not Linux, it’s proprietary codecs and Firefox’ hesitation to enable hardware decoding on Linux by default. It’s not difficult to get it to work but it simply does not work out of the box.
Linux, browsers, and hardware accelerated videos on the web don’t go along well out of the box. Which is a total shame.
Weird, I’ve never had problems over the past 15 years or so and I’ve been using VPS servers exclusively. Maybe my providers were reputable enough.
I realize my evidence is only anecdotal, but that’s why I started “in my experience”. Also, common blacklists are checked by the services I mentioned.
In my experience, this is nothing more than an urban legend at this point. There are great standards, like DMARC, DKIM, SPF, proper reverse DNS and more, that are much more reliable and are actually used by major mail servers. Pick a free service that scans the publicly visible parts of your email server and one that accepts an email that you send to them and generates a report. Make sure all checks are green. After an initial day of two of getting it right, I’ve never had trouble with any provider accepting mail and the ongoing maintenance is very low.
Milage may vary with an unknown domain and large email volumes or suspicious contents, though.
The Tesla truck is already there and just needs to be built at scale.
Full self driving has been fully achieved in 2017 and will reach end consumers next year (as claimed by Tesla every single year since then).
It is desirable that SpaceX rockets fail hard instead of succeeding in their missions.
Musk has truly mastered this principle and only now are people getting impatient. Most investors still regard him as too big to fail. Either Elon will be able to present sufficient success in the next few years or that bubble will burst very violently. He has almost used up the good will he has built up over years (earned our not).
Exactly this. This procedure is so common that you need to take care in situations where you don’t want the headers, as some tools set them per default.
I believe not. The question states “keywords” so it seems they want to try combinations of words they commonly used. And it makes a huge difference if the script can try one password per second or dozens/hundreds/more.
While it might be close to good enough for casual scripts, it is much better to use existing tools for performance critical applications, such as brute forcing passwords.
Everyone keeps saying that but I just can’t see it. The only time my mails were rejected was because I didn’t know what I was doing at the beginning of my journey. Now, whenever I changed my stack or did some major updates the past 20 years or so, I just go to 2-3 sites that analyze my mail server from the outside and tell me if there is anything wrong. The free tier is always more than enough. Just make sure there is at least one service in the list where you send an email to a generated mailbox and have it analyzed. Just looking at the mail server is not enough to find all potential configuration issues.
I aim at a100% score. It’s time consuming the first time around but later it’s just a breeze.
Wireguard is very lightweight and it just works. No overly complex setup, tools, matching protocols, algorithms, versions, etc. It just works and it’s simple UDP traffic. It’s the first self hosted VPN that I actually love and that works on all my machines, mobiles, VMs with just a config file to fine tune what should go over the line.
Yes, I agree. This use case likely wasn’t considered when the law was written. We’ll see how things turn out in the future because at some point we will have enough very knowledgeable people regarding GDPR in the community who are willing and even keen on steering the project in the right direction towards compliance.
Most of your points seem to be spot on from what I understand as well. However, I believe that the GDPR requirements can and should be baked into Lemmy itself. This would prevent the fragmentation you mentioned. A guarantee of removing user data as requested while federated plus a guarantee to remove stale user data while defederated since requests won’t get through in that case. That would “just” leave the list of processors. This one can be very tricky because you are not just sharing data with your home instance and their federated instances but also with the federated instances of those federated instances. The home instance has no way of learning about the 2nd degree federation. I have no idea how to get the network of data sharing GDPR compliant and I think this is the mich more complicated part that your proposal also suffers from.
Almost everything has been mentioned already so I just stick with the unusual: I host a private MediaWiki instance for note taking in my pen and paper rounds. It’s amazing once the other players got a bit more comfortable how to use it well regarding templates, categories and articles. My only regret is that I didn’t set up new instances per gaming group.
And whoever is way up his ass, is also a racist climate change denier. (Or has that changed in the last decade or so that I wouldn’t watch these shows?)