landr0id

7 ms·

1.
by landr0id 11d ago
I used to date a girl who was a designer and had to plead with her that breaking behaviors I'm used to is not a positive UX. "But it adds motion" was the classic reply.
2.
by landr0id 18d ago
It's useful for security research since you can do kernel debugging and inspection of the device not possible in the simulator. As others pointed out it's also useful for e.g. click/spam farms which need a "real" iP
3.
by landr0id 27d ago
[3] is no longer true. They're definitely not unprepared for an incident like this. It's not the first time they've done it and they published an update to their process in Feb: https://blog.rust-lang.org/2026
4.
by landr0id 2mo ago
Comments like these are why, even if Fil-C has cool technical accomplishments, I find it hard to speak positively about it. You unfortunately seem to forgo all nuance and push disingenuous arguments which fuel the cycle with similarly disin
5.
by landr0id 2mo ago
>you must go through a system provided shared library rather than make syscalls directly Just to add to this, on Windows for example you're really only supposed to invoke syscalls via ntdll as the syscall table is not stable so thei
6.
by landr0id 2mo ago
I still don't think that does anything regarding use-after-frees, only double-frees. Here's the code: https://codeberg.org/ziglang/zig/src/commit/e44e927d33d37c44... The closest callout in the
7.
by landr0id 2mo ago
>The DebugAllocator catches use-after-free (at least on page-level) To clarify, is that to say that you have to use the `std.heap.page_allocator` as its backing allocator?
8.
by landr0id 2mo ago
>ReleaseSafe catches use-after-free errors through runtime checks which panic if the program tries to use freed memory. I don't know Zig so maybe they know something I don't, but I have seen no evidence that it catches any type
9.
by landr0id 2mo ago
For the Nomad: The caps slightly rotate. If you look at them from the side profile, they are also all varying heights. I found enough variance in the physical layout of keys that I was constantly making mistakes and pressing multiple keys s
10.
by landr0id 2mo ago
If anyone is looking at this thinking it looks pretty and wants to check out Work Louder's keyboards, let me save you the time. Their keyboards must be made by designers who do not type much because they are both not pleasant to type o
11.
by landr0id 2mo ago
Big fan of nextest and this is my first time seeing this site. I'll be real I feel a bit ridiculous commenting this but you might want to consider rephrasing this: >Treat tests as cattle, not pets. Detect and terminate slow tests. N
12.
by landr0id 2mo ago
Yeah my bad for not defining it. "Extra-Sensory Perception", basically as you said I believe is the most common feature -- but in general I think encompasses cheats that generally boost your "senses". So it could use a
13.
by landr0id 2mo ago
I wonder how often wall hacks are actually used in high-level competitive play by cheaters vs ESP. ESP seems like the better route to avoid manual review flagging suspicious activity. Audible cues (which this currently does not mitigate, an
14.
by landr0id 3mo ago
I suppose they did make their work public after all :) Thank you for pulling up the references.
15.
by landr0id 3mo ago
Not to take away from the authors' work, but this was actually the approach taken by some engineers while Spectre / Meltdown were still under embargo. Not sure if they ever mentioned their work publicly so I will avoid naming them
16.
by landr0id 4mo ago
I didn't really mind the fn keys being there. I rarely use function keys unless I'm RDP'd to a Windows machine. What drove me crazy though was the escape key. They later added the physical escape key back but I think at that
17.
by landr0id 4mo ago
GPU memory/shaders/etc. isn't protected by MTE or PAC. They said "data-only", so I guess GPU commands could fit into this description.
18.
by landr0id 4mo ago
Static analysis tools + MCP server + a debugger with an MCP server makes reverse engineering incredibly easy and low-cost. I wrote a blog post about this recently: https://landaire.net/reverse-engineering-with-ai/ Just
19.
by landr0id 4mo ago
They exploited a linear stack buffer overflow. Not a write-what-where or arb write. A linear stack buffer overflow in 2026! There are at least two distinct failures there: 1. No strong stack protectors. 2. No kASLR. That's 20-year-old
20.
by landr0id 4mo ago
Ask yourself why Mythos was so easily able to develop a remote STACK buffer overflow vulnerability.
21.
by landr0id 4mo ago
>Last I read, ASLR is a good thing to have, but overall is usually not difficult to defeat. For local attackers there may be easier avenues to leak the ASLR slide, but for remote attackers it's almost universally agreed it significa
22.
by landr0id 4mo ago
FreeBSD didn’t have user land ASLR until 2019 and, amongst other mitigations, still doesn’t have kASLR. It’s not a serious operating system for people who care about security. If you want FreeBSD and security take Shawn Webb’s HardenedBSD.
23.
by landr0id 4mo ago
Mythos hacked the site, wrote, and published the article
24.
by landr0id 5mo ago
Their GUI system (GPUI) is not very mature for use outside of Zed. GPUI is basically a UI framework in the truest sense: a framework for building UI... frameworks/components. It has core functionality for async execution, an ECS for gr
25.
by landr0id 5mo ago
https://www.iroh.computer/sendme Iroh's protocol can figure out if the devices are on the same LAN and avoid going over the internet. It can work without a discovery server too -- i.e. completely LAN.
26.
by landr0id 5mo ago
They wrote something that allowed them to virtualize Git -- can't remember the name of that. But it basically hydrated files on-demand when accessed in the filesystem. The problem was I think something to do with like the number of git
27.
by landr0id 5mo ago
>At the same time, the larger tech companies (Meta and Google, specifically) ended up building off of hg and not git because (at the time, especially) git cannot scale up to their use cases. Fun story: I don't really know what Micro
28.
by landr0id 5mo ago
Part of the idea behind stacked PRs is to keep your commits focused and with isolated changes that are meaningful. A stacked PR allows you to construct a sequence of PRs in a way that allows you to iterate on and merge the isolated commits,
29.
by landr0id 5mo ago
I think Pijul has some good ideas, but I’m afraid the network effect of git at this point is too strong. I think jj’s concept of being a front end for many backends and sharing a common UX over them is a good one, but without a pijul backen
30.
by landr0id 5mo ago
It's not something to over-index on, but it's not a strong protection measure. It simply raises the overall cost to attack and analyze a system. Take the PS5 for example. It has execute-only memory. Even if you find a bug, how do

More ›