@feld We will end up with a machine-readable contract for sharing data between fediverse nodes (i.e. server-to-server capabilities negotiation) and there will be a netsplit based on whether your instance allows data to be "public/unauthenticated" (our current default) or "to privacy-preserving instances only"
I think I'd like this to happen, some people will benefit from it.
This is one reason why Google recently started using "google.com/maps" for its "Google Maps." Users will gladly give Google Maps access to their location. After all, the map needs to know where you are to give directions. But by using "google.com/maps" instead of "maps.google.com," all "google.com" properties now have access to the user's location after the user gave access to the location on google.com/maps.
@fu Generally anything below 70% will get the phone popped on the charger (wireless though) for an hour or so. If it's down below 20% I'll try to remember to pop it on overnight, but it will survive to the morning. But this is a newish phone with a large battery, and I don't use it as my main entertainment device; so in general it'll last a couple of days happily enough, just checking email & things like that.
@feld Living life on the edge then :-) As long as you have decent test suites, you're effectively handing the proofreading stage on to another machine. I suppose this does help to make the point that code is human speech after all :-)
Removed my filter for 'ChatGPT' & similar terms; it looks like the majority of my feed are now understanding that there is no substance to these toys, and are not taking the hype seriously any more.