SahAssar

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.

SahAssar

avant-hierdiscuss

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.

SahAssar

il y a 4 joursdiscuss

They seem to be different but overlapping: https://support.mozilla.org/en-US/kb/containers#w_common-que...

SahAssar

il y a 5 joursdiscuss

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.

SahAssar

il y a 5 joursdiscuss

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.

SahAssar

il y a 7 joursdiscuss

A lot of IP cameras already do this via https://en.wikipedia.org/wiki/Motion_JPEG

SahAssar

il y a 10 joursdiscuss

> Not true. 1990s connectors hardly ever broke for me.

RJ11, RJ45, USB-A, PS/2, SCART all seemed to break for me in similar frequency as I have encountered with modern USB variants.

> VGA connectors, SCSI connectors

Neither were designed for easy or frequent plug-in/plug-out and would not work for the use-cases USB-C are made for. Many VGA cables/devices would probably only get plugged in/out <5 times, whereas a USB-C device might get that in a single day. Also, I have phones with USB-C smaller than a SCSI connector in width/height so just the raw difference in material might be a factor.

> DC barrel jacks

I've broken multiple, but my first guess would be that the cables and electronics that you used DC barrels for was of much higher quality and cost than what USB-C stuff you are using.

SahAssar

il y a 14 joursdiscuss

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.

SahAssar

il y a 16 joursdiscuss

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.

SahAssar

il y a 16 joursdiscuss

Is that really running x86_64?

SahAssar

il y a 16 joursdiscuss

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               337390

SahAssar

il y a 16 joursdiscuss

Right, 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               337390

SahAssar

il y a 16 joursdiscuss

Is it this one? https://www.youtube.com/watch?v=aGOmzQbRT_E

SahAssar

il y a 17 joursdiscuss

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?

SahAssar

il y a 17 joursdiscuss

> 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.

SahAssar

il y a 19 joursdiscuss

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)

SahAssar

il y a 22 joursdiscuss

Yeah, boring implies that it is predictable, proven and mostly unchanging. In software those almost always come with age.

SahAssar

il y a 25 joursdiscuss

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.

SahAssar

il y a 25 joursdiscuss

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.

SahAssar

il y a 25 joursdiscuss

> 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.

Submissions

Show HN: Maps.black – Maybe the easiest way to use/host free and open maps

The Agile Paradoxon [video]

Benchmark comparing PostgreSQL against other specialized graph databases

Show HN: Skruv – No-dependency, no-build, small JavaScript framework

PaperTTY (eInk driver for raspberry pi) now supports GUI applications via VNC

Building a high-available file storage with Nginx, haproxy and lsyncd

comments