Permik

I haven't written up an article about it yet, but from a cursory look of the legal stuff this only affects private citizens and could be circumvented by setting up a shell company that owns your devices.

Legally, you can't surrender these devices, access to them or their passwords, as they are company property.

I'm not sure that if this is an obvious question that has been gone through already, but have any of the death threats relating to Rust stuff actually been "verified" or is it just an opinion that has been repeated enough times until it has been accepted as truth?

Just the open amount of discontent towards the language and the community, creates the perfect storm for a malicious individual to pose being a Rust developer that sends death threats for doing things that are not aligned with the values of the language/community.

If you want to, you can report any vulnerabilities to the Finnish Cyber Security Centre and they'll handle all of the reporting and mediating the issue with the affected party. You can do this wholly anonymously, so you don't have to worry about some trigger-happy corpo ruining your life.

Traficom's FCSC has been a great asset for white hat security reseachers globally by allowing them to just keep contributing to the common good.

For the generic selector naming I'd suggest "cascade selector/selectors" as that gives a hint of the origins and describes the actual function of it pretty well.

But in the real world, for maximal battery savings and therefore UX, routing any notification data via APNS is recommended.

Fortunately you can choose the payload by yourself and just send a notification "ping" without any data about the messages. But if we're serious about security, you just don't ping the client about new messages because even the time and existence of a notification can be compromising. _The user will know that they got a message, when they open the app and see that they got a new message._

It's good until some unregulated electronic device creates interference that makes some poor guys pacemaker act up and kills them.

It definitely is relevant here, buries the lede and tells that you're trying to skirt the HN guidelines.

Nothing exists in a vacuum and the surrounding context can and IMO *should* be taken into account.

I've been toying with an idea of creating a JS runtime that tries to run all code two times, one which runs all identifying information inside a runtime that has any network API's stubbed, and another that replaces the identifying info with garbage.

Most likely needs manual quirk code overlays for sites, but it's totally a solvable problem.

archive.today has a documented history of altering the archived content, as such they immediately lose the veil of protection of a service of "public good" in my books.

Just my 2 ¢, not that it really matters anymore in this current information-warfare climate and polarization. :/

Not sure if you're talking about Adnauseam, but this is basically the lawful evil version of the extension you're describing. https://adnauseam.io/

Adnauseam actually clicks on every ad in the background, otherwise it's just a wrapper on uBlock Origin.

Ain't so different from a severed piece of a reproductive organ as a logo of a company :D (I'm talking about an apple tree and it's fruit)

Assuming US, I think that the gov't can't actually compel speech from an entity e.g. force to keep signing the canary. Warrant canaries are the way entities can circumvent the narrow case where the gov't actually can restrict your free speech, by creating a case where your lack of speak is telling. By this framework we can then come around again to the first point.

Seems that every intelligence agency is still in the dark about Väinämöinen, lmao.

Duplicate, comments hither? https://news.ycombinator.com/item?id=46536753

Also related, not a DB but an incremental computation engine: https://github.com/salsa-rs/salsa

This can be found in things like the rust-analyzer and other actual compilers.

Huh, this seems like a cool optimization problem that I gotta dig in later. As sweeping was mentioned, there's an argument to be made that we could/should optimize for: - longest possible strides, you can pick up speed and minimize used time - allowing overlapping strides on "intersections", as intersections have more traffic and thus should have more grime and wear. - back-and-forth sweeping along a stride. Like with grass or mopping a floor, if there's any "evidence" left of the sweeping, it'll be more aesthetically more pleasing. - finally minimizing extra turning, as turning is slow

If someone has any extra suggestions on what restrictions/optimization targets there should be and the rationale for that, I'd be more than happy to receive them!

After seeing a cool demo of using precomputed blue noise with thresholding to approximate transparency in shaders. I'm quite interested about using the same technique for colour mixing.

Do note that unfortunately any future devices by Sony are just phones by other manufacturers that are just Sony branded. Sony stopped their first party device manufacturing, so your mileage of the hardware might be wildly different in the future.

This is false, recently the details element has gotten support for grouping them: the [name] attribute. This effectively enforces tab-like semantics where only one of the grouped details elements can be open at a time.

This is a quite recent addition and the modern web is evolving too fast so I wouldn't put it past myself for missing this :)

Yay for progress and for JavaScript free solutions!

Just disable ClearType and all your text will be uniform :)

Hello, it's me, your billionaire friend, Broizoz, take a look at my book store.

[Image with a bookstore filled with AI slop]

Not that I can answer for OP but as a personal anecdote; I've never been more productive than writing in Rust, it's a goddamn delight. Every codebase feels like it would've been my own and you can get to speed from 0 to 100 in no time.

Technically EU already has this as a right in the recent DSA legislation to be able to appeal any automated moderation that online platforms hand out.

"computer can never be held accountable. Therefore, a computer must never make a management decision." - IBM, 1979

They could get rid of the overheating problems by slapping some Frore systems cooling chips on the dies and IO chips. No need to cook the mf out of the chips as we already have solutions to cool them.

Alternative, non negative title: "Privacy advocacy against Flock-cameras cross political divides"

You seem to forget that all the people on public transit essentially get their time back. It's so much more efficient than everyone having to use their own time to all individually make that effort.

I made some calculations like a year ago using public data from Finland in the year 2023, the people lost collectively 55k years to driving cars. If we could take all that time back by doing minimum wage work in Finland, that'd add 4,841,511,500.55€ to the GDP and add approximately 164,006,202.08€ of taxable income to the state.

Of course that's just an approximation which presumes everyone could do their jobs while commuting and that you could get 100% efficiency. (But many of the values in the data were rounded down, so this is technically just a lower bound on the value ROI)

E: fixed mafs

With apps like Shizuku you can do the whole nine yards all locally untethered with one device :)

This is actually a non-issue with tons of unnecessary fear mongering going around, see my comment here: https://github.com/enaix/apk-loader/issues/1

You can already bootstrap an ADB connection to your own device without any extra hardware via Shizuku. Won't be long until F-droid releases a plugin that does the installation via Shizuku.

I'd still give them the benefit of the doubt as most (all?) of the contributors are Finns who you can almost guarantee to have a "no bullshit" type of mentality to essentially everything. And what I'd guess, the team most probably has quite an academic background because of the local culture.