Yet another day of screaming at digital enshitiffication:
1. My coworkers and I are in a car driving to FOSDEM.
2. We pull up to charge the car.
3. Charging station REQUIRES you to use an app, no option to just pay with a card.
4. We try to install the stupid app. We carry phones running:
- GrapheneOS
- GrapheneOS
- GrapheneOS
- LineageOS, postmarketOS, iOS
5. Neither of our phones meet requirements to install the stupid app (Play Integrity API).
6. My iPhone can't install the app, because it's "Not available in your country".
7. We give up and drive to another charging station.
This is NOT how you introduce applications, "Circle K" 
reshared this






GrapheneOS
in reply to GrapheneOS • • •Our ns1 network has 11 locations on Vultr (Piscataway, Miami, Los Angeles, Seattle, São Paulo, London, Frankfurt, Singapore, Mumbai and Tokyo).
Our ns2 network has 8 locations on Misaka.io (Ashburn, Miami, San Jose, Seattle, London, Berlin, Singapore and Tokyo).
GrapheneOS
in reply to GrapheneOS • • •Vultr and Misaka.io both have very good transit and peering for anycast due to having matching transit providers within regions and globally.
Both anycast networks needed a lot of configuration with BGP communities for traffic engineering and are working very well.
GrapheneOS
in reply to GrapheneOS • • •Our anycast networks are deployed with 2x IPv4 /24 obtained we quickly obtained for free from ARIN via NRPM 4.10 + NRPM 4.5.
We could use our own IPv6 space everywhere we have BGP if we wanted to do that since we have a /36 which can be expanded into more space reserved for us.
GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •Demi Marie Obenour
in reply to GrapheneOS • • •GrapheneOS
in reply to Demi Marie Obenour • • •Demi Marie Obenour
in reply to GrapheneOS • • •Why does GrapheneOS need its own AS?
Genuine question. This isn’t obvious to me.
GrapheneOS
in reply to Demi Marie Obenour • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •Demi Marie Obenour
in reply to GrapheneOS • • •LΞX/NØVΛ 🇪🇺
in reply to GrapheneOS • • •will you open the "server" side of the way you do "time" via https.
so we can use similar tech on our project (and maybe allow a "pool" of public time server using the same tech (reduce burder on your server, and allow us to have our own one) ?
(i ask only because DNS and Time is the two piece i always want to control inside my network myself (have my own stratum 1 server (run GPS time receiver))).
GrapheneOS
in reply to LΞX/NØVΛ 🇪🇺 • • •@lexinova We plan to eventually make it more configurable. Setting it up on the server side is quite simple since it simply involves setting the time in milliseconds in a header. It falls back the second precision standard date header if that's unavailable but it should be provided.
We use HTTPS rather than NTP with NTS because HTTPS is precise enough for end user devices. In fact, we made network time much more precise by lowering the permitted clock drift from 2 seconds to 50 milliseconds.
GrapheneOS
in reply to GrapheneOS • • •@lexinova Using HTTPS is much simpler and essentially doesn't add any attack surface since it's already being used for so much other functionality. HTTPS also nearly always works while NTP does not including via Tor which doesn't have UDP.
Bear in mind non-military GPS isn't authenticated and GPS is being widely spoofed especially in warzones. We use 6 different upstream sources with NTS for our servers where a minimum of 3 sources need to agree on the time in order for it to update the clock.
GrapheneOS
in reply to GrapheneOS • • •Demi Marie Obenour
in reply to GrapheneOS • • •Die Welt ist
in reply to GrapheneOS • • •GrapheneOS
in reply to Die Welt ist • • •@dieweltist ARIN, RIPE, etc. are Regional Internet Registries (RIRs) and then there are many organizations holding IP space with those which assign that space either directly to customers or to provide services to those customers.
> A Local Internet Registry (LIR) is an IR that primarily assigns IP addresses to the users of the network services that it provides. LIRs are generally Internet Service Providers (ISPs) whose customers are primarily end users and possibly other ISPs.
GrapheneOS
in reply to GrapheneOS • • •Demi Marie Obenour
in reply to GrapheneOS • • •GrapheneOS
in reply to Demi Marie Obenour • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
Unknown parent • • •