Perhaps the only way to get rid of them for sure is to require a CAPTCHA before all posts. That has its own issues though.
Perhaps the only way to get rid of them for sure is to require a CAPTCHA before all posts. That has its own issues though.
For what it’s worth, English Wikipedia editors reached a consensus to deprecate (ban) it for unrealiability last year: https://en.wikipedia.org/wiki/Wikipedia:Reliable_sources/Noticeboard/Archive_424#RFC:_The_Cradle
The following notes are present:
The Cradle is an online magazine focusing on West Asia/Middle East-related topics. It was deprecated in the 2024 RfC due to a history of publishing conspiracy theories and wide referencing of other deprecated sources while doing so. Editors consider The Cradle to have a poor reputation for fact-checking.
Because I am a developer and I have also been a sysadmin, and I really do not care. Yes, the format is good but I’m not particularly excited for it.
And I suppose sysadmins and application developers are not people?
My argument is not “we have a current standard”, it’s “people don’t give enough of a shit to change”.
I think this might sound like a weird thing to say, but technical superiority isn’t enough to make a convincing argument for adoption. There are plenty of things that are undeniably superior but yet the case for adoption is weak, mostly because (but not solely because) it would be difficult to adopt.
As an example, the French Republican Calendar (and the reformed calendar with 13 months) are both evidently superior to the Gregorian Calendar in terms of regularity but there is no case to argue for their adoption when the Gregorian calendar works well enough.
Another example—metric time. Also proposed as part of the metric system around the same time as it was just gaining ground, 100 seconds in a minute and 100 minutes in an hour definitely makes more sense than 60, but it would be ridiculous to say that we should devote resources into switching to it.
Final example—arithmetic in a dozenal (base-twelve) system is undeniably better than in decimal, but it would definitely not be worth the hassle to switch.
For similar reasons, I don’t find the case for JPEG XL compelling. Yes, it’s better in every metric, but when the difference comes down to a measly one or two megabytes compared to PNG and WEBP, most people really just don’t care enough. That isn’t to say that I think it’s worthless, and I do think there are valid use cases, but I doubt it will unseat PNG on the Internet.
What’s wrong with PNG?
Agreed. I managed to get my grandpa onto Linux using Mint on his old computer. He said the interface resembled classic Windows and was up and running in less than five minutes. I just had to show him how to use the software manager and that’s it.
This wouldn’t even be dumb if it weren’t for the fact that diamonds have practically no significant resale value.
At least if you buy something like a gold ring, you’ll know that it will be worth at least the melt value of the gold later on.
I have a script running that uses the Namecheap API to automatically get wildcard certs from Let’s Encrypt. I didn’t pay a dime for this. Did something change?
Nothing wrong with Boost Mobile, or any other discount telecom provider either. It’s not like the phone signals taste different lmao
It’s just a hallmark of “I bought the cheapest domain name TLD available”.
That’s not necessarily bad if all you need is something to get the job done, but there is a stereotype associated with it.
Then you can get permanent access for 165 USD (one-off payment)
The scenario you described would not be breaking in.
Terms and conditions being agreed to are not relevant for this purpose. An exposed API is one that is welcome to be exploited. If you’re not requiring an API key, you’re essentially saying “This API is free for anyone to use” for security purposes, regardless of what you say in the terms and conditions.
Of course it’s stealing. But they didn’t break in.
Hacking = breaking in
Data breach = stealing stuff
I’m not talking out of my arse here either. I don’t work in security specifically but I’ve got a CS degree as well and it contradicts my understanding of how those terms are generally used. This is an open API endpoint, equivalent to leaving the garage door open.
But the distinction is usually unimportant. A security hole is a security hole regardless of what you call it.
I’m not someone who works on the practical side of security, but as a computer scientist, I do not agree that it is “hacking”. That contradicts my understanding of “hack” versus other types of exploits, but you are correct that the distinction is generally not that important. A security problem is a security problem regardless what it’s called
It is a vulnerability, but exploiting that vulnerability is not generally considered by security experts to be “hacking” in the usual meaning of that term in academic settings. Using an open or exposed API, even one with a sign that says “don’t abuse me”, is generally not considered hacking.
Please provide a link to whatever source claims this.
I hold a computer science degree and this contradicts the definition of “hack” versus “exploit” used in academic settings.
I love the Internet Archive but they are pretty clearly legally in the wrong here.
Not morally, mind. I support open access to knowledge. But they very clearly broke copyright law here.