As just one data point here, let me say thank you for all your writing on it; it was super useful to have things to point at to say “we don’t have to just blindly do a thing the auditor suggested!” for our SOC2.
At least concert tickets are somewhat aligned with listening to music, unlike autoplaying video podcasts on the homepage rather than showing my playlists.
A lot of these videos get recommended to me, and although I haven't done hardware designs in 10+ years at this point, it's pushing me to get back into it again - and PCBWay lives in my head rent-free for when I do. If it were a one-off sponsorship I'd have forgotten about it, but the consistency across a load of different channels really cements it.
You can check out the protocol at https://github.com/fairpm/fair-protocol - anything WordPress or Typo3 specific are in the extensions, and the core protocol is self-contained. We'd love to work with more ecosystems to bring FAIR to them, and we've already had some discussions with others including maintainers of popular (dependency) package managers.
An "aggregator" is the thing that discovers and lists repositories - the equivalent of a search engine. Anyone can operate one themselves, and we (the FAIR project) operate a canonical one on our website, which is fair.pm.
I think it's understandable for both Backblaze and most users, but surely the solution is to add `.git` to their default exclusion list which the user can manage.
The aggregators can choose who to index, and we operate one at fair.pm - the idea being that you only federate repositories that meet requirements, and can defederate those which are bad actors. (End users can install directly from repositories though, and can always switch the aggregator if they find the rules too restrictive - no lock-in.)
Currently the reference implementation is for WordPress, but we’re working to bring it to Typo3 and other software at the moment too. The protocol is comprised of a core plus per-software extensions when needed.
We didn’t give up! We’ve pivoted efforts - focussing more on the technical part of the project, and expanding into other ecosystems. We’re currently working with the Typo3 community to bring FAIR there, as well as expanding further.
(AMA, I’m a co-chair and wrote much of the core protocol.)
On one of my old MacBook Pros, I managed to do this naturally through friction from my wrist moving back and forth on the keyboard for years; good idea to get ahead of it.
A 450kph limit for the rolling stock is great, but how many lines are actually capable of these speeds? There's only a single line (Chengdu–Chongqing, currently under construction) which is designed for 350kph, with sections capable of 400kph. Aside from that, most lines are at 350kph - unless I'm missing something.
I’ve been procrastinating on one as well, but I can recommend the Inkplate devices, which come with a ESP32, battery, and a case (optionally); handy platform to hack on. (If only it were so easy to finish the project…)
They consented to their data being used to verify their identity, not to train an AI on their data. Each separate purpose the data is being processed for needs its own basis.
Nexstar's stations blocked access from European IPs, providing a 451 Unavailable for Legal Reasons response code; Nexstar are the largest TV station owner in the US, so a large number of sites for local affiliates were unavailable. I think other networks (Sinclair) may have also one so.
> Boring Company has actually built tunnels and passengers are actually riding it. No one else is even trying.
Boring Company bought an existing tunnel boring machine (TBM), and used it to dig a car tunnel. Their only “innovation” in terms of any cost savings is to dig smaller tunnels - which we already knew could be done (tunnel cost grows with diameter), and which we don’t do for good reasons (capacity, emergency egress).
The branding and marketing exercise was excellent though.