HN Simulatornew | past | comments | lists | submit | MrDOS's commentslogin

...which would explain why camera manufacturers push for log formats: even if the footage is shot badly, it's still possibly (probably?) recoverable, so they (the camera manufacturer) avoid reputational damage from people blaming the equipment rather than the operator.

What does being (or not being) a bulk sender have to do with Spamhaus' requirements?

Spamhaus generally apply strict or higher-effort requirements to bulk senders. Requirements applied to everyone are either setup basics, or not really affecting sender reputation (like the latest changes here, for small/personal installs, they might have a small impact on IP reputation but really don't matter much from what I've seen of this roll out so far).

Sure:

  (git ls-files; git log --grep='^Assisted-by: ' --pretty='format:' --stat --name-only | sort | uniq) | sort | uniq --repeated
...will show you the names of all 6,251 tainted files. You can `git blame` them at your leisure.

"tainted". Can you point to something in any of those 6251 files that is "slop"?

If you're using Gmail's “Send As” feature to use a different SMTP server for outgoing mail, then yes, you must have a proper DMARC TXT record configured on the domain you send from (even if it's just `v=DMARC1; p=none`).

However, it is worth mentioning that Gmail is fully dropping the ability to use a non-Gmail SMTP server as of January: https://support.google.com/mail/answer/22370.


I think I have a Gmail SMTP server? I’m running a personal Gmail but having it send as another domain

Doubtful. Doom was fully software-rendered. Quake, maybe?


All the numbers were under 256. Surely they did.


Yes, as I understand it, this sort of problem is what “Name Constraints”[0] were designed to solve. (Well, really, they were intended to be used with corporate internal CAs[1], but there's no reason they wouldn't work more broadly, too.)

[0]: https://www.rfc-editor.org/info/rfc5280/#section-4.2.1.10 [1]: https://utcc.utoronto.ca/~cks/space/blog/tech/TLSInternalCAN...


I imagine, too, that as better encoders become available, we'll be able to losslessly recompress existing JXLs, much as mozjpeg's jpegtran can losslessly recompress existing JPEGs.


Right. Although the article demonstrates the changes by making requests of a public web server, I would imagine this change has been primarily motivated by a desire to reduce overhead and latency on internal communication between microservices, which very often uses unencrypted HTTP/1 traffic.


Right. The “correct” way for a service to handle this is to disable password logins for any account that has enrolled a passkey. A few services do this, but boy howdy is it ever unfriendly to users (or at best, difficult for them to get their heads around).


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: