Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kevincox
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
121.
▲
by
kevincox
7mo ago
I think the key difference is that they only need to coordinate when the reader and writer are close together. If that slows one end down they naturally spread apart. So you don't lose throughput, only a little latency in the contested
122.
▲
by
kevincox
7mo ago
Random idea: If you have a known sentinel value for empty could you avoid the reader needing to read the writer's index? Just try to read, if it is empty the queue is empty, otherwise take the item and put an empty value there. Similar
123.
▲
by
kevincox
7mo ago
Programming in assembly isn't really "hard" it mostly takes lots of discipline. Consistency and patterns are key. The language also provides very little implicit documentation, so always document which arguments are passed ho
124.
▲
by
kevincox
7mo ago
But it is about code syntax. Languages like Haskell make it part of the language by only supporting single-argument functions. So currying is the default behaviour for programmers. I think you are focusing on the theoretical aspect of parti
125.
▲
by
kevincox
7mo ago
It's still not very useful to hide the length. If you don't know the length and just start guessing with passwords of length 0 it only adds about 1/N extra guesses where N is the alphabet size compared to guessing strictly th
126.
▲
by
kevincox
7mo ago
Yes the most likely to fall are going to be targeted, but if you make that group of people 90% smaller with a delay that is still beneficial. Whether the feature is beneficial overall is a different story. But helping some people is great e
127.
▲
by
kevincox
7mo ago
Just because you have one example of someone who would not realize doesn't mean that the number of people who would realize is zero.
128.
▲
by
kevincox
7mo ago
I think the more important aspect is that people will have 24h to slow down, think, and realize that they are being scammed. Urgency and pressure is one of the top tactics used by scammers. Scammers will definitely call back the next day to
129.
▲
snap-confine + systemd-tmpfiles = root (CVE-2026-3888)
(cdn2.qualys.com)
1 points
by
kevincox
7mo ago
|
0 comments
130.
▲
by
kevincox
7mo ago
Probably, because you are now associating your internet browsing with your personal information. (I don't know if they have the sophistication to actually do this, but it is very possible.)
131.
▲
by
kevincox
7mo ago
Completely free as in you don't have to give them money. But you need to give personal information which also has value.
132.
▲
by
kevincox
7mo ago
I actually disagree with Rule 3! While numbers are usually small being fast on small cases generally isn't as important as performing acceptably on large cases. So I prefer to take the better big-O so that it doesn't slow down una
133.
▲
by
kevincox
7mo ago
That's not quite true. Only one pixel is being activated at a time but the phosphors continue to emit light for many pixels. In practice you get a handful of lines lit to varying degrees at at time. Maybe 1-2 lines quite brightly lit a
134.
▲
by
kevincox
7mo ago
The scale on the left was also very stuttery. Even when scrolling slow I could see the distance at the bottom updating at a very high frame rate and the scale on the left only moved occasionally which felt awful.
135.
▲
by
kevincox
7mo ago
Yes, this can help a lot, but it definitely isn't perfect. Especially since CPython uses reference counting it is likely that many pages get modified relatively quickly as they are accessed. Many other GC strategies are also pretty hos
136.
▲
by
kevincox
7mo ago
Yeah, I see what you mean. It basically shows that they contributed to ffmpeg purely because it helped them, but then they wrote this post to get good will for that contribution.
137.
▲
by
kevincox
7mo ago
I find it hard to be too upset, better late than never. Would it have been better to upstream shortly after they wrote the code? Yes. Would it have been better if they also made a sizable contribution to fmmpeg? Yes. But at the end of the d
138.
▲
by
kevincox
7mo ago
> By running all encoder instances in parallel, better parallelism can be obtained overall. This makes a lot of sense for the live-streaming use case, and some sense for just generally transcoding a video into multiple formats. But I wou
139.
▲
by
kevincox
7mo ago
This is surely why Facebook was interested in funding this work. It is common to have N workers or containers of Python because you are generally restricted to one CPU core per Python process (you can get a bit higher if you use libs that u
140.
▲
by
kevincox
7mo ago
But you are still more or less limited to one CPU core per Python process. Yes, you can use that core more effectively, but you still can't scale up very effectively.
141.
▲
by
kevincox
7mo ago
I don't know but if I had to guess. 1. Google uses protobufs everywhere, so having something that behaves equivalently is very valuable. For example in protobuf renaming fields is safe, so if they used field names in the JSON it would
142.
▲
by
kevincox
7mo ago
This doesn't always protect against out-of-bounds writes. Although if these sentinel values are in read only memory mappings it probably gets pretty close. (Especially if you consider kernel memory corruption a "bitflip".)
143.
▲
by
kevincox
7mo ago
Excellent for pingfs ( https://github.com/yarrick/pingfs )
144.
▲
by
kevincox
7mo ago
LineageOS provides ADB root access in stock builds. Sure, it isn't as convenient as some su apps but at least I can use ADB to access every file on the device. It probably also improves the attack surface compared to a su app. > It
145.
▲
by
kevincox
7mo ago
Fair enough. Owning means having a choice. The unlockable bootloader enables that. But for me the choice of OS will be one that lets me access all files on the device should I need to.
146.
▲
by
kevincox
7mo ago
Yeah, I would be fine with a different build stream. I do think it could be sufficiently secure in a single stream but it will always be increased attack surface so the safest option is to do separate builds. I also don't include a roo
147.
▲
by
kevincox
7mo ago
Yes, that is why it is a deal breaker. I'll choose to run a different OS. I didn't say that GrapheneOS must support root. Just that I won't run it if they don't.
148.
▲
by
kevincox
7mo ago
Yeah, I would install this in a heartbeat. I am very close to building myself but manually updating the phone every week or two is a big effort. I could use one of the third-party OTA builds but that is extending trust much more than I need
149.
▲
by
kevincox
7mo ago
Any files created by apps in their main data directories are inaccessible on most distributions of Android (I think it is actually required to be Google certified). The exception is apps that go out of their way to store files in user acces
150.
▲
by
kevincox
7mo ago
Yeah, this is the deal breaker for me as well. The fact that I own my device is non-negotiable. It is the reason I left the stock OS and I'm not going back. The idea that I can't access my own files if an app doesn't explicit
More ›