@sun I thought the artstyle looked familiar. These are the same people who did a collab with Penny Arcade back in the day, where a "sex educator" talks about masturbation & sex toys with one of the PA artist's children:
@adiz That's what I'd like to know. I just recently discovered that FUTO's shit isn't as "open source" as I thought it was, and I remember how LBRY was technically "open source", but designed in such a way to be as unfriendly/unintuitive to 3rd party developers as possible, so now I'm very skeptical of any supposed "decentralized project" until it proves itself.
From what I can find via quick search, atproto is dual-licensed under MIT and Apache 2.0, so it appears to get the gold star of approval from the FSF at least:
But I have no idea if they're playing any tricks under the hood. The Guides section of atproto makes reference to self-hosting a "Personal Data Server". But I don't understand any of this enough to be able to figure out if there's any fuckery going on.
If I'm reading this correctly, Bluesky offers the possibility for users to host Personal Data Servers, but this really just offloads storage onto the end users. Message delivery is handled by dumping all messages onto relays, which are sifted through by applications called "AppViews" who pick out and forward them to users.
There is currently only one relay run by Bluesky Inc, and since it's expected to store literally everything for everyone, you'd need 5 terabytes of storage (and growing) to create one. I don't know what's involved with running an AppView instance, but I imagine it's not simple and right now apparently there's only one and it's also run by Bluesky Inc
So the devil in the details appears to be "sure you can host your own data on your own PDS, but whether anybody gets to see anything you post (or vice versa) depends on a service that's too big for anybody but a corpo to run, and we run the only one everybody uses". The relay/AppView layer appears to be where algorithmic stuff for user feeds is done as well, so there's your chokepoint for deciding who gets to see what (or doesn't).
@djsumdog@prettygood@romin Donating blood is cool and all, but what if I could sell my blood on the open market instead? It'd be like Wolf of Wall Street, but vampires instead.
>"For the first time, we have a clear pathway to securing the future of social media as a tool for connection, creativity, and joy," Nabiha Syed, Executive Director of Mozilla Foundation
>The initiative, called "Free Our Feeds," aims to create independent infrastructure around the AT Protocol, an open-source technology that powers the Bluesky social network, and allows anyone to build their own social media applications
Interesting that Mozilla bailed on Fediverse just last year, saying they needed to focus their resources on the browser and AI shit:
This weekend, it's time for 3-week-old Christmas leftovers. Project Zomboid crowded it out of the Christmas Streaming Special, but now it's back! STALKER's slightly less famous little brother, it nonetheless gives us mutants, radiation, snow, and vodka.
"Let's Try: Metro Exodus" is this Saturday January 11th, only on PeerTube
40K Game Idea: An Ork-focused RTS (or Turn-Based too I guess) that's 50% combat and 50% weapon/vehicle building.
Gather junk parts from enemy factions you defeat in battle and strap them together to form frankenstein Trukks, Battlewagons, and various types of Dakka. Style points are awarded for how spectacularly you can explode or eviscerate your enemies with them.
Due to Comiket, there will be no Streaming Saturday this week. However, if you see anything from C105 you wish you could have a hardcopy of, hit me up by Dec.28th and I'll be happy to mail it to you from Japan, as long as you have enough magic internet money :morshu:
@king Okay, I wasn't sleepy enough so I got on it now. I'ma page @silverpill into this conversation as well
Initially my server logs were showing errors regarding the subscription payment, and when I checked my monero_rpc service It was rejecting the tx for some reason. I've had this problem before, so I went into the monero_rpc config and changed the remote daemon address... actually had to change it a couple of times, but once it connected to a remote node successfully the payment transaction was recognized. I can see it confirming in my wallet now.
Right now I'm a little concerned that a back end monero_rpc error can easily go unnoticed.. if King hadn't told me he was testing subscriptions, I might not have noticed and the sub wouldn't show up on my end until I realized there were errors in the log.
Checking the logs for errors is arguably a responsibility of an instance admin, but I feel like some system to more noisily alert an instance admin of problems with the monero_rpc server might be a good idea... not sure how to implement that, though.