I’m @froztbyte more or less everywhere that matters

  • 21 Posts
  • 2.35K Comments
Joined 2 年前
cake
Cake day: 2023年7月2日

help-circle










  • 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)





  • 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 :|




  • 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