timschumi

7 ms·

1.
by timschumi 10d ago
> you seem to understand the domain I'll have to note that I'm probably way worse than anyone doing this professionally or semi-professionally. This is the extent of what I learned as part of university, which was exclusively u
2.
by timschumi 12d ago
The Chromium issue is not public yet, so let's go with a very simple example. Let's say that you have a type confusion bug that (in terms of the interpreted language) allows you to use an Integer variable as an Array. That sounds
3.
by timschumi 21d ago
The processor version with the debugging incompstibilities was M4, I think.
4.
by timschumi 1mo ago
Is that with vanilla llama.cpp or with the third-party llama-swap manager? Last time I checked llama-swap was still the go-to solution, although I admit I haven't looked into it further.
5.
by timschumi 2mo ago
If you are talking about the addition of microG, that indeed seems like it hasn't been mentioned on the blog, although I'd argue very likely due to an oversight. I can find internal conversations that it deserves to be announced i
6.
by timschumi 2mo ago
> They stopped that malpractice a while ago (last year?). By now it has actually been almost two and a half years. > But they really hurt their credibility with the prior stance, and that their subreddit still has rules forbidding alm
7.
by timschumi 2mo ago
For a slightly more manageable list, the 590 of those that are or were supported officially are also listed on the LineageOS wiki [1]. [1] https://wiki.lineageos.org/devices/
8.
by timschumi 4mo ago
Not sure where CalyxOS came up in this?
9.
by timschumi 5mo ago
And it doesn't seem like anything newer than ARMv9.2 is available either, no matter the price point.
10.
by timschumi 6mo ago
Every system and package manager will be affected if it cannot download source code to build a package. NixOS less so, because pretty much all source downloads that are not restricted by license are a separate output that will therefore be
11.
by timschumi 7mo ago
> LineageOS was one of the OG de-googled Android ROMs, renamed a few years after Android Jellybean IIRC. Existing since 2009 as CyanogenMod and since 2016 as LineageOS, that would have been around the time where Android 7 (Nougat) was cu
12.
Exploiting MediaTek's Download Agent(blog.r0rt1z2.com)
21 points by timschumi 8mo ago|0 comments
13.
by timschumi 9mo ago
It's unfortunate that he uploaded this without notable commit history, it would be interesting to see how long it takes a programmer of his caliber to bring up a project like this. That said, judging by the license file this was based
14.
by timschumi 9mo ago
That's... cool, I guess?
15.
by timschumi 9mo ago
Not for the ones on the receiving end.
16.
by timschumi 11mo ago
> I can't even fathom what the build system is doing in order to require this amount of storage. A large number of 17 year old repositories, prebuilt toolchains, and the fact that you otherwise have every little bit of source code,
17.
by timschumi 11mo ago
There is a guide on how to set up LineageOS for libvirt (i.e. QEMU) [1], but there exist no prebuilt images at this point in time. [1] https://wiki.lineageos.org/libvirt-qemu
18.
by timschumi 11mo ago
As far as I have heard they have not actually secured partner access for themselves, they just got someone who has access to break their NDA.
19.
by timschumi 11mo ago
:^)
20.
by timschumi 1y ago
> What's wrong with asking to expedite the removal process, considering the process is detailed in the guidelines? Asking is one thing, the other thing is not accepting the decision of a maintainer on a topic that is at the maintain
21.
by timschumi 1y ago
Couldn't try to (together with Theo / t3) bully the Homebrew developers into a forced takeover of a package [1] if it were a conflict-free name. [1] https://github.com/Homebrew/homebrew-cask/pull/229
22.
A Full-Chain Exploit of an Unfused Qualcomm Device(hhj4ck.github.io)
3 points by timschumi 1y ago|0 comments
23.
Debugging the Pixel 8 kernel via KGDB(xairy.io)
4 points by timschumi 1y ago|0 comments
24.
by timschumi 1y ago
> My main complain by far to LineageOS is the necessity to wipe everything for major releases on my S10. That's not possible every year. Are you sure that you are not just misinterpreting the upgrade instructions? For the S10 a mand
25.
by timschumi 1y ago
Just so that nobody ends up confused: This is the same topic as posted here [1] a week ago, but presented in a blog post series format instead of as a slide deck. [1] https://news.ycombinator.com/item?id=44498614
26.
Google WiFi Pro: Glitching from Root to EL3: Part 1 – Characterization(raelize.com)
5 points by timschumi 1y ago|1 comments
27.
Glitching Google WiFi Pro from Root to EL3 [pdf](raelize.com)
1 points by timschumi 1y ago|0 comments
28.
by timschumi 1y ago
> Screwing up EFI vars doesn't make most systems unbootable. I have corrupted my EFI vars quite a few times trying to do funny things. UEFI implementations do tend to be buggy, but not all of them are that catastrophically bad. For
29.
by timschumi 2y ago
> It's already a basically bleeding edge C++. Why is it so much to ask for developers to use a more mature and established iteration so I don't need a brand new compiler? Because C++ got better and better in recent versions? Yo
30.
by timschumi 2y ago
But that's still not a circular dependency then, that's just the normal case for "I lost all my verification options" and it's exactly what the last option is for. If I create an account via e-mail and password at a

More ›