reflexe
Joined 5 years ago
Karma
218
Submissions
56
Member since
Jan 16
Software engineer and a team lead. Also a pole dancer.
View on Hacker NewsRecent submissions
Comment · 11 days ago
Sorry but this post makes zero sense.
Many apps (eg chrome) frequently fix bugs that are actively exploited in the wild yet have no public weaponized chain (sometimes for months).
The fact that there is no fully public weaponized chain does not mean it does not exist or that this bug is not as scary. It only means that it is not as trivial to exploit as log4shell/shellshock/etc.
According to cloudflare [1], it is being exploited in the wild.
Comment · 17 days ago
I worked on a very similar bug in the past, just with another ipq and another pcie card.
IMO, The issue is that cache coherency is not very well specified, and usually defined at the SoC/platform level.
Meaning, you could have the same arm core on 2 different SoCs, running the same driver with the same PCIe card and you will get corrupted data on the one where the PCIe controller‘s requests do not snoop the cpu cache.
Also, note that for both rx/tx to work, you need to invalidate on both sides: rx need to access the dram and not cache. tx need to verify that all was written to the dram before giving it to the hw.
Comment · 7 months ago
To add a little bit: the reason for that (or at least one of them) is strict aliasing rules:
If the compiler had to assume that a write to an int* might change the value of a double&, that’ll cause it to avoid some optimization and maybe even perform expensive reads.
This is the reason that you are not allowed to alias a variable with another type (can be disabled using -fno-strict-aliasing) [1].
However, one of exceptions is char and std::byte. The compiler is not allowed to assume that a write to char& won’t affect the value of a double& for example [2].
[1]: https://www.gnu.org/software/c-intro-and-ref/manual/html_nod...
[2]: https://en.cppreference.com/w/cpp/language/reinterpret_cast....
Comment · 8 months ago
Or even better: turn off the device. Cracking cold/BFU (before first unlock) devices is not supported in many cases by tools like Cellebrite [1].
[1] https://discuss.privacyguides.net/t/updated-cellebrite-iphon... : support matrix from 2024, in many cases only AFU (after first unlock) is supported.
Comment · 9 months ago
No idea why the downvotes, these are valid points. I still don’t fully agree with it:
1. There are alternatives to nvidia: these 3 companies are probably developing their own alternative to NVIDIA, at some point they will switch to their solution or to competitors (for example: google used TPUs to train Gemini 3 [1], with no nvidia GPUs, despite being a pretty large Nvidia customer).
2. The market seems to be consolidating: for example Apple has decided to use Google Gemini for their new Siri [2]. I’m not an export (or future teller), but I think it increases the chance that other companies might follow and get off the AI race.
3. I am sure that OpenAI and related companies would want to sustain these kind of orders, but I am not sure it is possible without more and more funding, and I don’t know if even Sam himself know to estimate how many GPUs they will be able to buy from Nvidia in 2026.
[1] https://x.com/JeffDean/status/1886852442815652188
[2] https://blog.google/company-news/inside-google/company-annou...
Comment · 9 months ago
According to nvidia’s 2025 annual report [1], 34% of their sales for 2025 comes from just 3 customers.
Additionally, they mentioned that customers can cancel purchases with little to no penalty and notice [2].
This is not unique for hardware companies, but to think that all it takes is just one company to get their sales down by 12% (14b$).
To cut to the point, my guess is that nvidia is not sustainable, and at some point one or more of these big customers won’t be able to keep up with the big orders, which will cause them to miss their earnings and then it will burst. But maybe i’m wrong here.
[1] https://s201.q4cdn.com/141608511/files/doc_financials/2025/a..., page 155: > Sales to direct Customers A, B and C represented 12%, 11% and 11% of total revenue, respectively, for fiscal year 2025.
[2] same, page 116: > Because most of our sales are made on a purchase order basis, our customers can generally cancel, change, or delay product purchase commitments with little notice to us and without penalty.
Comment · 9 months ago
My favorite east Germany escape stories is the escape is train driver’s Harry Deterling, that just drove the train into wall (which was not fully a wall by then if I understood correctly)
https://www.chronik-der-mauer.de/en/chronicle/_year1961/_mon...
Comment · 10 months ago
What is up with the name?
Edit: Kinkora implies that it has something to do with kinks, at least that was my first impression.
My guess is that it means something in another language, but maybe this is not a good first association that you would want for a AI image generation product that can be used in a professional setting.
Comment · 11 months ago
I think that reading all of the information from the SSD should “recharge” it in most cases. The SSD controller should detect any bit flips and be able to correct them.
However, this is implementation detail in the SSD FW. For Linux UBI devices, this will suffice.
Comment · 11 months ago
Also, FYI for the one person here who uses raw nand flash: run ubihealthd (https://lwn.net/Articles/663751/).
It will trigger reads in random areas in flash, and try ti correct any errors found.
Without it, the same issue as in the original article will happen (even if the device is powered on): areas in the NAND were not read for long time will have more and more errors, causing them to be non recoverable.
Comment · 1 year ago
Hopefully it will make Qualcomm behave more like Arduino and not the opposite.
Qualcomm is one of the worse companies I have had the pleasure to work with.
Their support model is hellish and they provide very little information and documentation, so usually you’ll end up doing a lot of guessing and reverse engineering. They will tell you to sign a contract with one of their “design partners”, but even they can’t get answers for basic questions.
Seriously, if they want more small cap companies working with them they have to treat them better, I worked with them as a small company and as a larger company and in both cases their support was basically non existent even if we were buying chips from them for more than 10m$ a year.
Comment · 1 year ago
<removed by me>
Comment · 1 year ago
Tie that chip to a beamformer (silicon labs have a few) and you have a phased array radar, which is a radar that does not move at all (pretty cool in my opinion)
Also, 15usd is not cheap for this kind of chip. You can buy a full wifi 7 rf/modem or a 4 core arm64 soc with this kind of money.
Comment · 1 year ago
I think that while data is a major point here, in my opinion, these are the reasons apps are preferred by developers:
1. Persistence: while websites are very easy to close, deleting an app is much more difficult and usually requires pressing on some “red buttons” and scary dialogs. It also makes sure the user now has a button for your app on their Home Screen which makes it a lot more accessible.
2. Notifications: while they exist for websites too, they are much less popular and turned off by default. Notifications are maybe the best way to get the user to use your app.
And while I hate the dark patterns some companies use (Meta, AliExpress, etc), I do understand why installing the app worth so much to them.