HN user
In Baarle-Nassau you can walk a few hundred meters and cross the border multiple times https://en.wikipedia.org/wiki/Baarle-Nassau. Or even walk within a house and cross the border.
Microsoft Kin was a separate thing, and was discontinued 48 days after launch.
Windows phone had excellent hardware (from nokia) and excellent UX, but very few apps bothered to support it. If my old windows phone was still updated and my critical apps supported it I'd still be using my lumia 800/900 series phones.
They seem to be different but overlapping: https://support.mozilla.org/en-US/kb/containers#w_common-que...
I'm going to guess that it was not a normal COTS SD card, and instead designed for continuous writes.
The factors for SD card failures in raspberry pi seem to be mostly SD cards not meant for the purpose and having things like swap, atime or disk logs enabled which leads to unnecessary writes.
Not sure if it is still like this, but jellyfin used to leak massive amounts of metadata. For example by checking the thumbnail paths (which were unauthenticated) you could see what shows/movies someone had.
Might want to warn the "friend" if they don't have auth on the tunnel itself.
A lot of IP cameras already do this via https://en.wikipedia.org/wiki/Motion_JPEG
Yes, it's wrong. But we have also agreed to all be wrong in the same way. Except during the specific day that we are wrong in different ways.
Correction: We are mostly right, most of the time, but wrong in ways most people don't notice except if they try to talk while everyone is wrong.
Clarification: Human perception of time is not understandable, and the machine abstraction even less so.
The parent said "2/3 of US installs are on non-phones (waydroid, nintendo switch, rpi, etc)", you responded with "Some Waydroid installations are on phones". My response to you was about the vast majority of waydroid installs tracked here are highly unlikely to be on phones due to the CPU architecture.
Is that really running x86_64?
Are we seeing different stats? Clearly x86_64 is the vast majority of waydroid installs.
waydroid_x86_64 181015
waydroid_arm64 8718
waydroid_tv_x86_64 3200
waydroid_x86 1215
waydroid_arm64_only 914
waydroid_car_arm64_only 69
---
usa_total 337390Right, but that would still not be x86_64 except on very uncommon phones. Look at the stats:
waydroid_x86_64 181015
waydroid_arm64 8718
waydroid_tv_x86_64 3200
waydroid_x86 1215
waydroid_arm64_only 914
waydroid_car_arm64_only 69
---
usa_total 337390Is it this one? https://www.youtube.com/watch?v=aGOmzQbRT_E
Given how uncommon x86 phones are (a few asus, lenovo, etc. that did not sell well) I think it's clear the vast majority of waydroid_x86_64 are not phones, right?
But I don’t think I would want to create a real database user for every version of the app.
Why not? Database users are (usually) not expensive, and with groups you can give access to a group you just add the user to.
Adding this logic to the connection pooler seems more complicated.
On these you usually can't reject them. It says
Data processing by advertising providers including personalised advertising with profiling (Consent required for free use)
Yeah, boring implies that it is predictable, proven and mostly unchanging. In software those almost always come with age.
To be honest it feels like these answers boil down to "we feel it'd be nice if this existed but we have no actual answers as to how to get it done".
---
To stick with your comparison: when letsencrypt and ISRG launched they had actual answers for how to deal with the hard challenges in their space:
A) how to get included in a trust roots (crossigning with IdenTrust at first and the knowledge and expertise of how to get included in the longer term)
B) Automated domain validation in a standardized way (ACME)
C) Long term commitments of sponsorships to ensure people could trust it would stick around
---
I wish you the best of luck, but I think this might have needed to bake a bit longer before publicizing.
So you have just built a wrapper around https://passportreader.app/, which itself is reading NFC enabled ID/passports from specific countries. The coverage map is here: https://passportreader.app/coverage.
Might be good to know that even in the US this approach would only work for ~50% of people, since a lot of people don't have passports. In most countries this does not work at all, since they don't issue NFC enabled ID/passports.
Think of it as a similar model to ISRG and LetsEncrypt.
In that case it was started by an institution (mozilla) with a lot of heft in the area (mozilla's CA program is one of the most broadly used) and was backed by other orgs (google) that had a vested interest in it's success. I'd be interested to hear which potential sponsors you see in a similar situation here?
rule of one person per subdomain
What is the plan to (without costly overhead or cost to the end user) validate who is an actual person? Even large corporations with loads of resources have problems with this without resorting to treating it as if a person equals a credit card number.
The screenshot clearly says "NOTICE TYPE: DMCA".
assuming we're talking just about "safe" Methods
That's a pretty big assumption. Any decent webdev should not let GET/HEAD/OPTIONS modify state (joining a meeting is changing state) and additionally PUT/DELETE should also be idempotent.
POST with JSON (or other non-form formats) api's should also have it's content-type header checked (text/plain forms can send a JSON body but the content-type will be text/plain). PUT/PATCH/DELETE and POST with a non-form content-type (application/x-www-form-urlencoded, multipart/form-data, or text/plain) will trigger a preflight so that CORS is properly checked before the actual request reaches the server.
Rolling release has nothing to do with this. It could just as well be a PPA in ubuntu or any deb repo for debian or similar.
The current installation shall already contain one (or more) public keys that it trusts for updates
The current installation was fetched via HTTPS, right? Either by you or in the factory.
Just saying the "bootstrapping already happened" does not make it not happen. It still needs to bootstrap trust from somewhere
Those have been broken again and again. Even if not, how do you distribute the public keys for it, how do you bootstrap that trust?
someone compromises the webserver
Sure, but that's true for 99% of things. Unless you establish trust outside of the normal distribution channel how would you protect against this? What is your proposed channel that is not bootstrapped from HTTPS PKI?
Yes. Or you can license it for specific purposes. But in general open data refers to data that is open to use by anyone, for any purpose, without restrictions except in some cases attribution.
Yes. Just like editing wikipedia will help train models that are used for data classification in north korea or whatever.
It's a feature of open data, it's open and usable by anyone.
Seems like tsx is a wrapper around esbuild, not tsc.
Ironic that the page says
... it does have a few small problems, such as not working on modern computers ...
When connecting to this site in firefox says
An error occurred during a connection to tom7.org. Peer attempted old style (potentially vulnerable) handshake.
But as a percentage of revenue I'd assume those are a lot smaller than Office365 is for microsoft and Workspace is for google.
Last I checked I don't think AWS included things like Amazon Prime Video either, AWS is primarily their buissness/platform offerings, not consumer things like Twitch/Prime/Music/etc.