That headline reads like it’s a planned annual event. :(
As a policy, it’s bullshit. But here are the relevant sources:
https://en.wikipedia.org/wiki/Never_trust_anyone_over_30#“Don’t_trust_anyone_over_30”
This seems like a good candidate for a bookmarklet that would append the (site:…) parts to an existing DuckDuckGo search result URL. Then you could just do a normal search followed by clicking the bookmarklet.
“some people use” ≠ “everybody wants to use”
(And are you sincerely suggesting WhatsApp, which is run by one of the largest and most aggressive privacy invaders the world has ever known, as a privacy friendly application? I would suggest re-thinking that position if you want to be taken seriously.)
but you have no direct connection from this resource to harm you claim it causes?
The connection is very clear, because you can see what domains are on the list.
So you’re lumping this resource into a bucket with other resources that were malicious
You’re saying a dev using this list […] needs to convert their FOSS use-case to yours?
[…] the argument I feel you’re making.
Please stop putting words in my mouth. As you seem to be arguing in bad faith, I’m done with this conversation.
You’re getting into very sketchy territory by saying a dev who is using a public GitHub repo to solve their problems needs to take it down
No, I don’t believe I said any such thing. Since you mention it, though, I think taking this list down and removing the false positives before bringing it back up would be the responsible thing to do.
In the interest of specifics, can you point to where this specific list has done harm?
I know from personal experience and investigation (both as a user and on the admin side) that there are now many cases of privacy-focused email addresses being rejected, or even worse, accepted and then silently black-holed, due to the domains being inappropriately added to lists like this one. I don’t know of a place where people report such cases so they can be documented in aggregate, but if I find one, I’ll be sure to bookmark it in case your question comes up again in the future.
Off the top of my head, taxi services lack:
I think most (maybe all) of this could be solved by something like a clearinghouse for taxi rides, effectively federating the various taxi services in an area, with a web app available for hailing.
Signal gets some things right, but others wrong, such as phone numbers and centralized architecture. As such, it doesn’t fit the “everybody wants to use” part.
That’s not what this specific list is for.
Yet it has a lot of legitimate domains, and has had them for years.
Regardless of whether the maintainer is malicious or just irresponsible, his list is doing harm.
Do services count? Because in that case, ride-hailing. A replacement for services like Uber and Lyft.
They rejects them because it is an abuse prevention mechanism.
An “abuse prevention mechanism” that punishes legitimate users is a badly designed mechanism. It’s a lot like police racial profiling.
You can solve captcha and register without any additional information
Nobody said anything about registering.
Devs can use them to block DISPOSABLE mails, not PRIVACY legitimate emails.
That’s what they claim, but in practice, they seldom distinguish between the two.
The article explains what it means. If there’s something about the explanation that you don’t understand, maybe you could ask specifically about that?
Ironically, when I tried setting a ProtonMail account recovery email address, they rejected it because it was on a list like this one. I hope Proton gets off this blacklist, but I also think they should practice what they preach.
It’s not just Protonmail.
Blacklists like these aggressively and unapologetically collect all privacy-focused email domains they find, including simple forwarding and tagging services. With more and more sites using these lists to reject or black-hole email addresses, it has become difficult to protect one’s self from spam and cross-site account tracking.
Dear web developers, please don’t use these lists. Well-intended or not, they are privacy and user-hostile.
That GPU is indeed new, and I don’t have one, but I think the amdgpu driver has supported it since kernel 6.4 or 6.5. Any distro offering that and recent AMD firmware will probably work. (You could also manually install the firmware files if you change your mind about fiddling and want a specific distro that hasn’t caught up yet.)
I don’t generally recommend specific distros, since people’s needs and preferences vary so widely. However, I would probably try Linux Mint (and the KDE Plasma desktop because I dislike Gtk) if I were in your position. Mint gets a lot of praise for being an easy distro based on the good parts of Ubuntu. It also maintains a Debian edition (LMDE), which I think is a good insurance policy in case Ubuntu ever goes off the rails and becomes unsuitable as a base for Mint.
If you find yourself struggling to choose, remember that you’re not married to whatever distro you try first. If you run into a problem that’s not easily solved, you can always switch.
Civ 4: Baba Yetu
Changing the subject away from Debian’s gaming performance is a strange tactic, but since you’ve shifted to mocking the name of the distribution, Debian Stable’s name comes from this sense of the word:
stable 3 of 3 adjective
1b : not changing or fluctuating : unvarying
I would expect someone so familiar with “all 3 and beyond” of the Debian distros to know that.
To indulge your sophistry, though, practically all operating systems have released broken packages at some point. Debian Stable has a well-earned reputation for doing it less than others. Even with kernel Backports. Trying to scare people away from it is a disservice to the community.
There’s clear performance differences between 6.1 and 6.6.3
As already stated, kernel 6.5 is available on Debian Stable.
Ofc, you can install newer kernels, you could install kernel 6.6.0 if you wanted, but you’d be going outside of the stable repo to do it which kinda defeats the entire purpose of Debian Stable.
No, it does not. Stable Backports exist for exactly this reason.
Not to mention that mixing and matching packages can lead to problems in the future. Like accidently using the wrong dkms driver version on the wrong kernel version.
I don’t know how you might have managed to do those things, but no, installing the Stable Backports kernel would not cause either of them.
Please stop spreading falsehoods.
Good riddance.