Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
zekica
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
zekica
2y ago
There is no separate per-process address space on 8080 or Z80, for that you need an MMU/protected mode.
62.
▲
by
zekica
2y ago
Cryptography is every download you ever do in a browser, bitlocker or equivalent encrypted disk access. Add to that gzip or brotli compression (common in HTTP). Hardware decoders for newer video codecs (such as AV1) are not that common (les
63.
▲
by
zekica
2y ago
rEFInd is great! I wish they just updated the default theme to something nicer.
64.
▲
by
zekica
2y ago
That's one of the original design requirements for wireguard. Unless a packet is signed with the correct key, it won't respond at all.
65.
▲
by
zekica
2y ago
Starlink is in a better position as their satellites are in a low earth orbit - 30 times closer than geostationary. It correlates to 1000 times (30dB) stronger signal on both sides.
66.
▲
by
zekica
2y ago
Yes, but it doesn't have to be. Have you looked into Dave Taht's crusade against buffers?
67.
▲
by
zekica
2y ago
Honest question: why do we need to optimize for <10kbps? It's really impressive what they are able to achieve at 6kbps, but LTE already supports >32kbps and there we have AMR-WB or Opus (Opus even has in-band FEC at these bitrate
68.
▲
by
zekica
2y ago
Never? Google will probably reduce their SWE more and more assuming we get exponentially better at LLMs or something better comes along, but it won't ever be fully replaced.
69.
▲
by
zekica
3y ago
Not really, they updated to 5.6.x but used code from the git tag, not from the tarball, and only in their snapshot (not stable) version. The git repository never contained <i>build-to-host.m4</i>, so the injected build step
70.
▲
by
zekica
3y ago
Mostly true, but IPC is not the only thing influencing power consumption - process node also plays a significant part, so Apple will be ahead as long as they use the newest nodes at TSMC. Apple's IPC mostly comes from their 8-wide inst
71.
▲
by
zekica
3y ago
> but that raises the question of why Red Hat are writing a new driver Nvidia's driver cannot be included in the upstream linux as it doesn't follow kernel coding style and code organization, but more importantly it is tightly
72.
▲
by
zekica
3y ago
udp[8] = 1 filters only handshake packets. Without it, data packets would also be sent to the userspace daemon. I'm not sure if initial handshakes can be replayed, but since WireGuard ignores unknown clients, it might be possible.
73.
▲
by
zekica
3y ago
I don't miss it, DisplayPort is a really good replacement.
74.
▲
by
zekica
3y ago
64:ff9b::/96 is allocated for NAT64 - and most US mobile carriers use this as most Android and iOS phones use IPv6 only APNs with DNS64 and 464XLAT.
75.
▲
by
zekica
3y ago
The difference is that OpenWrt has the entire source code available, and unlike those franken-distros, it is built as vanilla linux + a set of patches. As long as there is enough interest, anyone can rebase these patches on top of a newer m
76.
▲
by
zekica
3y ago
> so they're far from the only group guilty of benefitting from openwrt without contributing This is certainly true. SoC vendors often base their SDK on a fixed version of OpenWrt and then add proprietary patches on top. Then sell t
77.
▲
by
zekica
3y ago
As a small contributor to OpenWrt, I don't like the whole: release one version of their proprietary fork of OpenWrt and then just do security fixes on top of that. If they really want to focus on hardware and base everything on top of
78.
▲
by
zekica
3y ago
Won't tail call optimization mostly mitigate this?
79.
▲
by
zekica
3y ago
IMHO, nuclear is not delivering only because of new compliance requirements and nimbysm.
80.
▲
by
zekica
3y ago
No, AMD doesn't have E-Cores right now, but even when they do it won't ever crash: they have Zen4 as their P-Core and Zen4c as their E-Core. Both support exactly the same extensions.
81.
▲
by
zekica
3y ago
I bought MT7921K on a PCIe card for two older PCs and they work fine, AX210 is better but Mediatek is not bad - between two of them on 6GHz they managed >1Gbps and didn't lock up at all even after 200GB. Just had to use at least Lin
82.
▲
by
zekica
3y ago
90W is peak power consumption for these. They idle at about 8-9W measured at the wall socket or $22-25/year.
83.
▲
by
zekica
3y ago
If the network already supports NAT64 I would use CLAT running on the system. That way you don't need LD_PRELOAD.
84.
▲
by
zekica
3y ago
You can have an AP accepting multiple different WPA2-PSK and/or WPA3-SAE passphrases, and since on WPA2 PMK depends on the password, and on WPA3 PMK is different for each client, you can put them in different VLANs or have per PMK MAC
85.
▲
by
zekica
3y ago
Great explanation but went right away with NAT, port forwarding and no mention of proper routing setup and no mention of IPv6.
86.
▲
by
zekica
3y ago
You can use Mozilla's offline translate extension - it doesn't support many languages but it works.
87.
▲
by
zekica
3y ago
It is actually star pound star pound 4 6 3 6 pound star pound star. 4636 represents INFO.
88.
▲
by
zekica
3y ago
IMO, better options are box86/box64 or FEX.
89.
▲
by
zekica
3y ago
It was last time I was looking.
90.
▲
by
zekica
3y ago
RIPE-738 (European RIR's address allocation and assignment policy) says that home users should get at least /56.
More ›