@KevinMarks At $100 or so you’re on the cusp of it being better to just rent 1U of co-hosting, buy a cheap server, and drop the AppEngine ecosystem

@aral Except for a few cases like this, my Touch Bar has been unused. Apple invested so much in it, and it noticeably bumped up the end user price, but was so underwhelming. Lack of physical escape a mistake. Lack of haptic was a mistake. Inability to find the keys on the bar by touch was also an issue. We all just wanted something like a mini Lebedev keyboard up there.

To quote from recent blog post by @davew:

“to build #interoperability, #Implementors make things work, not #W3C committees” (1/3)

This sums up my recent thoughts that some people put too much emphasis on getting a standard published and less on actually getting something out the door that is usable because somebody has bothered to validate it by getting their hands dirty and implementing something not only interoperates with another implementation but works as needed (not necessarily as intended). (2/3)

The more astute will recognise that I’ve been working on my #ActivityPub implementation so my viewport on these matters is distorted by hitting reality. (3/3)

@thisismissem @trwnh @julian @pfefferle @manton @samsethi @renchap @andypiper Beware those stop gap solutions that become permanent instead of temporary in nature.

@deadsuperhero @mro Th developer community has always, despite what they say, developed for other developers first and users last. Plus, what normal person wants to get involved with setting up a server, installing, configuring, and maintaining some software, DNS, and all the other things.

@julian Would it be an idea to put some examples (redacted to protect the innocent^wguilty) into a github repo (or blogpost, or whatever) so there is a corpus of things to test against/watch out for?

@evan It is a low-quality signal that just means mutual connections: interpreting anything more from that is unwise. IRL we have mutual connections, and I’m sure if we exchanged references/vouches about those mutual connections the result would not be identical because of our different experiences of interacting with them (we move in overlapping not identical circles).

@evan Programmers are lazy/busy and barely have time to read the README file, let alone do due diligence on a package they’re importing. Plus, if we have connections in common, asking for any kind of reference is IRL highly dependent on personal whims and vendettas (and comes with no guarantees). For #xy it seems there were other actors “vouching” because nefarious actors will “juice” where needed: build their own network of connections to appear genuine to aid their agenda.

@evan A nefarious actor will simply juice their “verified fediverse account” with “reputation” (whatever that is). The #xy crisis seems to be a long-term play.