News for hackers. Stuff that matters.

gregsadetsky

Re:Polyend releases the Tracker firmware source code on Monday November 02, 2026 @05:19PM (#50344742)
Relatedly, Erika Synths released the source code of the LXR-02 very recently as well: https://www.ericasynths.lv/news/post/lxropen

(I/AI had fun porting it to wasm/web! I don't want to seem too self-link'y, so if anyone asks, happy to share the link)

I also have a Polyend Tracker for sale if anyone's in the market..! It's a great device, I'm just trying to focus on having less right now.

Re:Twelve years of distributed SQLite on Sunday October 25, 2026 @08:26AM (#50230833)
Ah yes, sorry - saw your name there too but didn’t read closely enough.

Are you still going to use dqlite after this experience, or has it shaken your confidence in it? Also what’s been your experience with microk8s itself - I hadn’t heard of it before

Re:Twelve years of distributed SQLite on Saturday October 24, 2026 @04:46PM (#50225066)
I feel like there should be a comparison table listing all of these engines and how they compare on their external dependencies, whether a single leader/any node can write, their shape (embeddable library vs server), etc.

IMHO support for transactions is a pretty important dividing line. Some engines support full SQLite transactions while others - like rqlite - don't officially support BEGIN/COMMIT [0], which matters if you rely on multi-statement transactions.

A friend/colleague has been building a pure-Python client for dqlite [1] (DB-API and SQLAlchemy), which may interest folks here. dqlite has full support for transactions, and like rqlite doesn't have external dependencies (ie no S3/Consul).

No knock on rqlite or any other engine - dqlite has warts too [2].

[0] https://rqlite.io/docs/faq/#does-rqlite-support-transactions

[1] https://github.com/letsdiscodev/python-dqlite-dbapi

[2] https://github.com/canonical/dqlite/issues/882 opened by my friend, https://github.com/canonical/dqlite/issues/908 , https://github.com/canonical/dqlite/issues/912 opened by me

Re:Twelve years of distributed SQLite on Saturday October 24, 2026 @04:29PM (#50224909)
Re:Show HN: Turn regular JavaScript into a neural net on Thursday October 22, 2026 @04:17PM (#50200423)
As far as I understand, this doesn't turn "regular" JavaScript into a NN, it's rather "write your logic in a DSL that creates a neural-net-shaped circuit"

the source code for the OS demo is not "regular" code, it's full of `emiRelu`... https://github.com/chenglou/handwired/blob/main/src/handwire...

The main site & readme seem to overclaim, while the docs say things like "With Handwired you write a numeric program" and "No tool converts existing JavaScript source into a program" - https://github.com/chenglou/handwired/tree/main/docs

happy to be proven wrong, to have misunderstood this, etc.

Is there a way to know that a web/https client is susceptible?

As in - could I connect to a site signed with those certificates and see that my browser/client accepted that certificate?

I assume these certificates have been pulled from most browsers - but - an un-updated curl or wget would still accept these, right?

EDIT: found https://emudhra.we-have-a-problem.com/ , scroll down to 'Does your client still trust the compromised intermediates?'

EDIT 2: a few tests you can also run...

    curl https://dv-g3b-emudhra.we-have-a-problem.com/
and in Python:

    import urllib.request;print(urllib.request.urlopen("https://dv-g3b-emudhra.we-have-a-problem.com/").read().decode())
I do (half) remember reading that book! I actually meant to ask (in my question above) whether that book is actually "accurate"/representative of malware negotiations.

Older »