avian
Or are you saying old fridges didn't have a bang-bang controller and hence could have an honest thermometer built in?
Do they really? When replacing my 20 year old fridge (that had an actual mechanical temperature gauge) with a new one I specifically bought one that had a (now digital, of course) display for the current temperature.
It turned out that the temperature display is completely faked. It always shows exactly the set temperature, from the moment you power it on. I guess because of (actual or imagined) customers complaining why their fridge shows e.g. 7°C when they set it to 4°C.
Incidentally, my new smart AC does exactly the same thing. Subjectively it's worse than the old one at keeping the place not too cold and not too warm, but it makes damn sure to never show the actual measured temperature anywhere.
Everything is getting dumber.
It takes an agent on the order of 100 billion operations to produce a single token. A person (generously) taking just a second for a single mental addition or multiplication would take tens of thousands of years to write just a single line of code.
Unfortunately this only talks about what DMARC policies are published by domains. I was hoping they will go into some analysis of how many mailboxes actually hard-enforce DMARC rules on ingress (as in, respect the DMARC policy as published by the sender's domain, p=reject or whatever else it might be)
I have been hesitant to enforce DMARC rules on my server. Partly because maintaining it was a pain (see opendmarc - maybe better with rspamd now), but also because on my test runs I saw plenty of legitimate incoming mail that simply would get rejected if I were to enforce DMARC on ingress.
I suspect big players like gmail have some kind of soft enforcement/reputation/machine learning approach to DMARC, but this is way too much work for a small time admin like me.
I remember when Gmail came around and everyone was more than happy to hand off their email to Google. No spam and ability to send and receive huge (for the time) attachments I think were the main things people wanted.
Not sure if that was before or after everyone was happy to hand off their web browser to Google.
Yeah, the arm is definitely the part of the human body that is most sensitive to a laser that can make insects go up in a puff of smoke...
It's hard to find good info on this since 99% of search hits are people talking about setting up DMARC from the _sender_ side.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014058#39
You would have the "new web" consisting of the top n major websites paying this fee.
And then you would have the "old web", accessible only to people still owning their own PCs with unrestricted browsers. And probably heavily scrapped by AI companies to reguritate to the masses through the new web.
I like this headline. In other words, AI will suck out every last bit that makes engineering fun.
I know, I know. The job is to make money for your employer not have fun. AI makes money faster so shut up and do your job.
But fuck, I took this career because I found joy in understanding things and making things that look and work well.
Advertised prices for my setup are now roughly 2x what I'm currently paying.
But don't underestimate the stubbornness and time some people can dedicate to complaining to authorities. You might have a neighbor that will send letters about how they have to pay mandatory monthly bills for the national public broadcast they now can't listen to. They will complain and complain enough that eventually the broadcaster will send someone over with a spectrum analyzer and then the ball starts rolling. There have been court cases over stuff like that in this corner of Europe.
But I agree, you can argue those offenders went out of their way to cause trouble. In the cases I read people kept doing stupid things even after several warnings and apparently only got their lesson only when dragged into court.
In Germany and everywhere else. The difference is how much it's enforced.
Note that this project isn't using that horrible Raspberry Pi GPIO PWM hack that shits all over RF but an off-the-shelf low power car FM transmitter product. I guess if someone knocks on your door you can point your finger to whoever in Germany sold you that.
I guess you could do a whole circuit on photo-etched or stamped sheet metal inside a glass envelope in a similar process that VFDs, although I don't know how you would implement cathode heating. It would be an interesting exercise to think where that could lead you, but I think modern VFDs date much later, when semiconductors already wholly replaced tubes in digital logic.
What fails in a tube is usually the heater filament, which is a wear part with a limited life. Where some (very) expensive tubes did go is to have replaceable heaters - so not more but less integration.
I saw that announcement yesterday, went through the list of fixed issues and decided to wait with the upgrade since none of them were relevant for me.
If I haven't just seen this on the second page of HN I would have probably deferred this upgrade for a few more days.
I've seen similar things posted on here before that had a binary build only and zero technical documentation. It was really hard to see any kind of research or education value in those.
Here's an excerpt from a 2013 article in Scientific American that appears on the first page of results when searching for "voyager left the solar system" [1]:
> Voyager 1 was starting to get a reputation as the spacecraft that cried wolf, after scientists repeatedly claimed it was leaving the solar system, only to change their minds and say it wasn’t quite there yet.
[1] https://www.scientificamerican.com/article/voyager-1-leaves-...
My thinking so far against was 1) after a few months I'm pretty sure I would hear about the real attack 2) Repeating too frequently. People aren't getting hacked all the time (I hope).
But who knows? Now I'm thinking that maybe some other step in the attack is failing and maybe the attackers just trigger the email bomb part pre-emptively in case they actually succeed in resetting the password/purchasing/whatever.
It's not even that much of a hassle. What worries me is that I don't understand why someone would go through the trouble of doing this for no apparent benefit. I hope I'm not somehow unknowingly enabling some sort of an attack on any of the entities sending these automated replies.
In recent months I'm seeing instances where random personal mail accounts on a server I run would receive a barrage of mail in a short amount of time.
Mail seems to be bounced via Google Groups - they are sent from Google's IPs and have headers like X-Google-Group-Id, List-*, etc. all pointing to Google Groups. The actual group ID changes after each individual instance of this. However when I actually check e.g. the List-Archive URL, the group appears to be already been deleted.
The content of mail looks like it originates from various (legit-looking) random public web services, support requests, issue trackers, web contact forms etc. For example, a common reoccurring one is Virginia Department of Motor Vehicles (as in something like "thank you for filing a document #123 with us").
No apparent phishing links, no attached malware, no short advertisements snuck into a text field etc. Just automated replies from "noreply@"-type addresses.
It does not seem to be the case of trying to hide another attack (as discussed here for example: https://news.ycombinator.com/item?id=47609882) - over many instances I've not seen any other malicious activity. And this mail is filtered out easily enough based on Google's headers.
It all looks like there is some bot that a) creates a Google group and subscribes (one or more) random email addresses to a Google group and then b) enters the group's mail address into a bunch of random web forms that then send their automated responses to the group.
What could be the motivation for this? After the fact it's filtered pretty easily based on headers. It's not nearly enough volume to DoS the server. But why would someone go through the trouble of setting this up?
This complaint was sent to Google, probably because the cloudinary.com URL appeared in their search results.
It's doubtful anyone at Fiverr was made aware of this - unless Google typically forwards these complaints to the actual host of the offending URL. Even then, it would go to Cloudinary who would in turn need to notify their client. Many hops with plenty of "someone else's problem" barriers for the message to overcome.