Good instinct to fight against antisemitism, because there is a lot of it. Unfortunately the Israeli government lobs accusations of antisemitism at its (legitimate) critics frequently, enough so to muddy the waters between actual antisemitism and criticism of the Israeli state.
Because KDBX is a gzipped and encrypted stream, this is actually fundamentally an issue with the spec itself. A client must re-encrypt and compress the file prior to writing because a mere append operation is not possible. SQLite solves this issue by allowing you to write with page level granularity rather than being forced to dump the whole file for a single tiny change!
Yes actually, I have personally onboarded several people to BitWarden! (Including manually migrating their accounts, setting passwords and passkeys, etc) However, I dislike the centralization and lack of control. There was a paper discussed within the past couple days on HN about what a malicious BitWarden server was capable of, despite BitWarden's marketing. I believe BitWarden's team responded promptly and appropriately to the research.
VaultWarden is a good compromise (offers the choice of SQLite or Postgres under the hood), putting you in charge of the primary server, but it is honestly overkill for a single personal user compared to a kdbx file on a webdav share.
I think it also touches on issues of interest to the hn crowd (it's being reported on a YC-incubated platform!), and one especially unique things about the reporting is the spatial reconstruction of the scene, which is not a degree of detail you typically get, and limits the number of variations of interpretations possible.
I also think issues of censorship are very high on the list of topics of interest on HN and few topics are subject to more extensive censorship than reporting on events in Israel and Palestine.
Israel and Palestine is one of the most obsessively covered topics in every form of western media. All the more the reason it doesn’t belong on HN. I’ll grant that there’s a tech angle to this specific story, but past experience with such articles on HN is that they reliably devolve into endless repetition of fixed talking points on each side. No useful information or opinion is conveyed, just endless insinuation and infective.
Furthermore, there are handful of accounts who sole purpose seems to be to pump the HN feed full of Israel and Palestine. People who want so badly to talk about a single political topic should probably go to Bluesky.
I agree that Bluesky is a great place to go into more depth about it, and in many respects a better place than HN to get good discussion. But I think there's equivocation going on here.
Framing it as "obsessive" is an attempt to shift away from subject matter toward an attitude of journalists or consumers, like it's borne of the same attitude as paparazzi. But I think it merits significant coverage not for that reason, but because it so frequently meets criteria for meriting journalistic attention.
I agree that comment sections can be bad, but they aren't always, and to some degree I would rather trust moderation than suppress reporting on a topic of legitimate interest. You're exactly right that a lot of reaction is toxic and politicized, and sometimes the way that manifests is by trying to cook up rationales to suppress stories by flagging them. Out of respect for the concern you've identified, it would be a huge mistake to let politicization win by allowing politically motivated abuse of flagging.
I think the solution which will lead to the best quality of life for people in and around the levant is a single, secular state. Two states that are both ethnonationalist is unsustainable, and any single state which isn't secular can only be achieved through genocide. Freedom to practice whatever religion, seperation of church and state, and no apartheid for a certain group of people.
I tried to describe this in [1]: "Unsigned integer are intentionally not supported to simplify learning and using the language, to avoid surprising behavior and edge cases, and to reduce security issues and error-handling pitfalls. When needed, unsigned behavior is available through explicit operations. This design does not affect performance or memory usage."
I understand this may not sound very convincing yet... it is hard to describe... basically, unsigned types sound simple, but they are not.
Hmm, I don't quite follow. For usages like counters or version numbers, it seems like allowing negatives makes things more complicated rather than less.
Like, what if you're getting a u32 over the wire? I feel like using an i32 to represent that data makes it more error-prone. Numbers will unexpectedly appear to be negative?
reply