In any case, I really hope they return. There is the username, of course, but it is a nice touch to have a mostly unique simplistic avatar for those who don't supply their own profile picture.
---
Update: It looks like the Identicons might be back.
475 karma · joined February 24, 2024
In any case, I really hope they return. There is the username, of course, but it is a nice touch to have a mostly unique simplistic avatar for those who don't supply their own profile picture.
---
Update: It looks like the Identicons might be back.
Both seem to regularly face laptops and GPUs respectively that have BGAs shorted out by leaking liquid metal.
(Note: I have paid for fonts before and wouldn't hesitate to buy a coding font if it fit my preferences)
If the reply was along the lines of "This is a new firmware check to curb fraud related to undisclosed aftermarket RAM upgrades with potentially unreliable chips." - I'd be fine with it, but basically just coming out to gaslight the user about the issue leaves a very sour taste in my mouth. In the end, they had to come clean anyway, big surprise.
I say this as someone who has been loving Pis despite their price for the straightforward and reliable long-term software support. Not gonna pretent like I'll never buy a Pi again, but it's another strike moving me to explore other options in the future.
[1] https://radar.cloudflare.com/domains/domain/web.archive.org
But it's not? This was published between the two posts about archive.today: https://gyrovague.com/2025/02/23/anatomy-of-a-boarding-pass-...
I know there are a number of headers used to control cross-site access to websites, and the linked blog post shows archive.today's denial-of-service script sending random queries to the site's search function. Shouldn't there be a way to prevent those from running when they're requested from within a third-party site?
Regardless, another user reports the attack is still ongoing[1], so this isn't a discussion that's going to happen about archive.today anytime soon.
The current situation is due to Cloudflare flagging archive.today's domains for malicious activity, Cloudflare actually still resolves the domains on their normal 1.1.1.1 DNS, but 1.1.1.2 ("No Malware") now refuses. Exactly why they decided to flag their domains now, over a month after the denial-of-service accusations came out, is unclear, maybe someone here has more information.
Ditto for their other domains like archive.is and archive.ph
Example DoH request:
$ curl -s "https://1.1.1.2/dns-query?name=archive.is&type=A" -H "accept: application/dns-json"
{"Status":0,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"archive.is","type":1}],"Answer":[{"name":"archive.is","type":1,"TTL":60,"data":"0.0.0.0"}],"Comment":["EDE(16): Censored"]}
---
Relevant HN discussions:
https://news.ycombinator.com/item?id=46843805 "Archive.today is directing a DDoS attack against my blog"
https://news.ycombinator.com/item?id=47092006 "Wikipedia deprecates Archive.today, starts removing archive links"
https://news.ycombinator.com/item?id=46624740 "Ask HN: Weird archive.today behavior?" - Post about the script used to execute the denial-of-service attack
Wikipedia page on deprecating and replacing archive.today links:
https://en.wikipedia.org/wiki/Wikipedia:Archive.today_guidan...
There are some shortcomings, like a bug where it doesn't remember the last selected ISO if its filename is too long, files also need to be fully sequential. These might be fixed in their newer models (the 2531 is fairly old).
Nonetheless, a platform for AI videos with an audience looking for them, rather than the horrible "boomer-slop" that is prevalent on other social media, is welcome in my eyes.
The law[1] is worded like this:
> (1) Mit einer Funkanlage (§ 3 Absatz 1 Nummer 1 des Funkanlagengesetzes) dürfen nur solche Nachrichten abgehört oder in vergleichbarer Weise zur Kenntnis genommen werden, die für den Betreiber der Funkanlage, für Funkamateure im Sinne des § 2 Nummer 1 des Amateurfunkgesetzes, für die Allgemeinheit oder für einen unbestimmten Personenkreis bestimmt sind.
The law basically says that you may only listen to (or take note of in comparable way[2]) messages that are:
1. For you, the operator
2. For amateur radio operators according to the Amateurfunkgesetz
3. For the general public
4. For an indeterminate group of persons (I think that's an accurate translation?)
For me, a big question regarding aviation and marine traffic monitoring is what "unbestimmten Personenkreis"/"indeterminate group of persons" actually means. Since "die Allgemeinheit"/"the general public" is listed separately, I'd assume it's a distinct group from that, and to me the previous commenter's "meant for any member of the public who happens to be flying a plane nearby" sounds like it could fit that description. I'd argue, for example, that police radio is for a "determinate" group of persons, police officers and dispatchers working for the government, whereas aviation and maritime traffic is an "indeterminate" group of people, people working for all sorts of airlines, shipping companies, recreational pilots/boaters, who happen to be around the same area.
If anyone has any links to cases where this law was tried in relation to aviation or maritime communications, please share them, I have been struggling to figure out where to look for this stuff, on top of that, the law was also renamed or moved around, which makes it extra confusing.
[1] https://dejure.org/gesetze/TDDDG/5.html
[2] Might be related to this weird ruling, where a judge in a case about some ADS-B receiver decided that it was ok because rendering the position of aircraft wasn't "listening to" (as in, literally hearing) the traffic: https://openjur.de/u/130555.html - This decision is probably moot now, due the addition of "take note of in comparable way". The judge briefly mentions that actually listening to the traffic could be violating the law, but I am not sure if this point was ever properly litigated.
Edit:
"Apple A17 Pro Chip Hardware Flaw?" - https://news.ycombinator.com/item?id=45160947
"iOS 18.5 Bluetooth Privacy Vulnerabilities" - https://news.ycombinator.com/item?id=44933435
Both of these submissions are [flagged]. I suspect that OP takes iPhone device logs and feeds the to an LLM to come up with security issues.
Edit: There isn't any exploit or bypass described here, the claim is just that "debug logic" is enabled on production devices.
Please don't buy "grey market" MS keys (i.e. super cheap keys or keys for products not sold to end users, like LTSC).
Either buy keys from legitimate vendors or use alternative activation methods (emulated KMS, etc.). I believe a lot of these grey market keys come either from MSDN subscriptions or leaked MAK keys, in either case, you aren't really paying for the product, you're just funneling money to sketchy people.
I mainly had this issue with the default Windows install image names.
Fragmentation can be a bit annoying, especially when using exFAT, which doesn't appear to have defragmentation tools available. It can be avoided by never deleting files and instead reformatting every so often.
That being said, it's still a fantastic tool because all the images "just work" everywhere a class-compliant USB optical drive would.
Rust's linter is also called Clippy, and they don't seem to have any issues.
I think a no-brainer solution here, which I am surprised isn't used, is to just immediately kick the account when a well-known signature, such as CheatEngine, is detected. If the program isn't even attempting to get around VAC, there is no point in doing the whole "delayed ban" thing.