brobinson
brobinson on Hacker News
"died in a blogging accident"
Didn't all the major browsers alter their timing APIs to make this impossible/difficult?
It would block requests to OCSP responders, for one.
The 4chanx extension (userscript, run it in violentmonkey or equivalent) lets you nest comments in a chain to make following threads easy while maintaining the overall chronological state of the threads. You can also hide a reply, and it will automatically hide the entire chain of replies to that reply.
I _think_ iMazing can do what you want:
https://imazing.com/configuratorDisclaimer: I've never used this feature. I only use it for backups and copying files to my iPhone.
Note that Ruby also has \z which is what you generally want instead of \Z.
(\Z allows a trailing newline, \z does not)
Hah, I saw this:
Steve was not a big fan of authority, so he also liked the idea of a site without editors.
and remembered him getting prod database access to censor comments criticizing him. I guess it's true what they say about power corrupting you.
Imagine you did all of that, received and accepted an offer, and then they made you work on snap. Grim.
Same here. "Learnings" sounds ESL to me.
There's a huge difference between using your personal Spotify account at work and using your personal Github account at work.
Sivers is an OG. Definitely not a bot. I've looked at sivers.org/multiply at least once per year for the last 15 years.
Mine is just a cool-looking paperweight now.
Microsoft, Google, and other companies have all determined that about 70% of CVEs are memory-related. Here's the US government's take:
https://www.cisa.gov/news-events/news/urgent-need-memory-saf...These memory-related exploits disappear with Rust aside from in "unsafe" blocks (possibly the worst named keyword in any language... it should have been called "trusted"), and that means you have a smaller and more easily auditable attack surface for these types of memory-related exploits. Some code (e.g., FFI) can't be verified as memory-safe by the Rust compiler at compilation time so "unsafe" is there as an escape hatch. I've written a bunch of Rust since 2014 building things like webservers, realtime futures processing algorithms, MEV bots, etc., and I've only had to use "unsafe" a few times.
I've also worked in security on products at Fortune 100 companies, and C is a constant nightmare for CVEs. I think I have PTSD from having to update libcurl. The more software we have written in memory safe languages, the better off we all are.
Hey, thanks for the response! There have been a lot of across the board improvements in the kernel in the last four years so I'm surprised there's not a noticeable performance improvements in 6.2 (although I also consider 6.2 old at this point).
I'm curious what the performance difference would be on a modern kernel.
Well, the inverse is "we're so Barack".
What I got out of it was "determination eventually beats natural skill over time".
What are the better products that are available?
The addon you linked (on the Firefox version) only requests permissions on google.* sites so I don't think it will work for DDG. Is there a separate extension, or am I misunderstanding something?
>Wayland doesn't fractionally scale chrome, chromium, chromium, chromium, chromium, and other appimage and non-native applications.
The absolute state of desktop applications in 2023. Everything is a web browser. God help us all.