will keep the offer in mind when I have the spoons and round tuits for it :)
froztbyte
joined 2 years ago
I’m a bit split on this one
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 :|
it would be incredible if yud’s one of the types to lose his focus around sauce 3, would do a real kicker to the shine of his grift
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)
is the consensus solution on how to subvert the acausal robot god
dunno if you've yet gotten to look at the most recent yud emanation[0][1][2], but there's a whole "and if the robot god gets too uppity just boop it on the nose" bit in there
[0] - I mean the all-caps "YOU'RE ALL GONNA DIE" book that came out recently
[1] - yes I know "emanation" is a terrible wordchoice, no I won't change it
[2] - it's on libgen feel free to steal it, fuck giving that clown any more money he's got enough grift dollars already
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
thanks for linking this, was fun to watch
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
view more: next ›
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