black mirror enhancement: because the algorithms involved may present multiple likely fits to any given input, each output is also considered a conception and given due protection (even if not used)
again, I ask you: please make better posts. you could start by not shooting from the hip about things you know little to nothing about. even better would be asking questions to learn.
For instance, as Electrek reminds us, in 2016, Elon Musk made a promise. He promised that, by the end of 2017, a Tesla would be able to drive itself from coast to coast. We’re talking Los Angeles to New York, with no human intervention.
That was bulls**t. Listen to any tech CEO nowadays and you will hear nothing but an endless stream of wild proclamations about how so-and-so massive shift will occur within the next 10 years! Five years! One year! Next week!
nice, good collection of links, will help next time I need to find it. couple weeks ago I mentioned it on masto and I had someone Very Huffily reply to me (a situation I resolved by simply blocking them, gfy with that nonsense)
Xanadu’s micropayment-oriented transclusion-and-royalty system is impossible to correctly implement, due to a mismatch between information theory and copyright; given the ability to copy text, copyright is provably absurd
it kept being funny to me that even while xanadu had already shown the problems with content control the entirety of the NFT craze just went on as if it was full greenfields novel problem
The details lie in the devil, for sure…you’d want the price [of making a change to a document] low enough (zero?) not to incur Trivial Inconvenience penalties for prosocial things like building wikis, yet high enough to make the David Gerards of the world think twice.
some of these people just really don't know their history very well, do they
on a total tangent:
while xanadu's commercial-aspiration history is intimately tied up in why it never got much further, I do occasionally daydream about if we had, and if we could've combined it with more-modern signing and sourcing: daydream in the respect of "CA and cert chains, but for transcluded content", esp in the face of all the fucking content mills used to push disinfo etc. not sure this would work ootb either, mind you, it's got its own set of vulnerabilities and problems that you'd need to work through (and ofc you can't solve social problems purely in the technical domain)
has there been any meaningful advancement or neat new research in agoric computing? haven't really looked into it in a while, and the various blockchain nonsense took so much air out of the room for so long I haven't had to spoons to look
(separately I know there's also been some developments in remote trusted compute, but afaict that's also still quite early days)
much of the lore of the early/earlier internet being built is also full of some extremely, extremely unhinged stuff. I've had some first-hand in-the-trenches accounts from people I've known active from the early-mid 90s to middle 00s and holy shit there are some batshit things happening in places. often think of it when I see the kinds of shit thiel/musk/etc are all up to (a lot of it boils down to "they're big mad that they have to even consider other people and can't just do whatever they like")
I really don't buy the "billing mistake" line - they've been doing the same thing to many other community-org slacks. I've seen with my own eyes the mail that was sent to the ZA tech slack
on the one hand, the post as first posted had a lot of “victimised” language (“omg slack is extorting us”) and frankly that felt like bait - esp as many, many volunteer-type orgs that have had similar slack setups have been taking a hammer for months now (as I posted before, a local ZA tech setup was one, and more recently that big k8s one too). there’s enough precedent here that expecting slack to have behaved otherwise (even “honourably”) seems to me to have been almost foolish
on the other, slack 100% only took action once this did hit hype and enough eyeballs, and only reacted since it was an embarrassment
but…yeah. slack hasn’t been a good option for public use for literally years now :|
someday(tm) I’ll get around to looking into getting a season pack from the states to here (which possibly might be distinctly non-trivial, and if it is I’ll have bother trying to figure out the logistics of it, which ugh)
heard people reached those by just deleting tweets by hand.
yeah, the various backend interactions tied to web controls are extremely low-count limited
you could probably do it by smacking together a userscript (or whatever the fuck is the these-days version of greasemonkey/tampermonkey/??? to use) with a moderately simple algorithm.. open a window, click execute, leave it going by itself for however long it takes to get through everything. it doesn't have to do everything in minutes
I also heard blocklists put a high strain on the twitter so not going to look into removing that
probably the feed compute stuff only has this computational expense incurred for any displayed feeds (pruning off calculating stuff for long-enough-inactive users is one of the cheapest easy gains in that type of content feed), so this might not matter much. don't have enough insight into real ops there to know one way or the other tho
it's kinda hilarious how close "steelmanning" (as practiced by some) already is to this, but probably not far enough to be usable for that purpose on its own
hadn't seen that saltman clip (been real busy running around pretty afk the last few weeks), but it's a work of art. despite grokking the dynamics, it continues to be astounding just how vast the gulf between fact and market vibes are
and as usual, Collier does a fantastic job ripping the whole idea a new one in a most comprehensive manner
from when I last looked into this: twitter 100% has[0] (unstated) web API ratelimits for various subservices[1], but getting direct API creds became a "give us your actual phone number" thing even before felon took it over...
so I just decided to tombstone my account by making it private, updating bio, and never logging in again
not willing to give them what they want for API access. might at some point go write some web automation to recurringly click a delete button? idunno
[0] - ....well, 4 years ago, "had". probably maybe still does, on whatever parts of the haproxy or whatever config didn't get absolutely fucking destroyed in felon's mania to rebrand it to "x" overnight (a process which failed hilariously badly for weeks and I still think fondly of to laugh at)
[1] - when going through the "your interests" list (hidden deep in settings), if you unticked too many boxes too quickly you'd hit a webserver-enforced ratelimit on request limits and then half the webapp would get a bit fucky for an hour. ratelimit was something like 30/min with a 1/m type token-bucket refresh. quite the shitshow
ruby's had this problem for ~2 decades now. like, the "rockstar dev" archetype literally became big directly because of ruby's popularity and perception at the time
I haven't been active in/near the ruby space for a number of years now so I can't speak to the modern details well at all, but I wouldn't be too surprised to learn that the various branches of it haven't really learned how to deal. I will say that I have seen some improvement over that period, but... yeah
absolutely not a thing to be "at risk of", and a little bit worrying to see someone even worrying about