Apparently #googlefiber has 8 Gbps in Austin now. Got an email about it, hit the upgrade button (+$25/mo), rebooted the modem, and...yep, the Cat6 run I have between fiber jack and router can pass 8 Gbps.
Liquidated my shares in Apple today. Current management is awful and I have little faith they can move the company forward in a meaningful way. Putting my money toward more worthy companies. Hell, Apple even has me researching Android phones now.
@codeguy Size wise, unfortunately you have basically two options (S24, Pixel 8). The larger flagships have more features, though I've been on the "small base flagship" train since the OG Pixel (Pixel, Essential Phone, S20, S21, S22, S23, S24) and it's served me reasonably well. I'm partial to S-series Samsungs for modem/reception reasons, but Pixel software is a bit better IMO.
@codeguy In which case, S24 series would be the thing to get at the moment, picking the feature level/size you want. Or a Pixel. Moto's stuff is solid price/pref wise but you have to wade through bloatware on initial phone setup that subsidizes the device, so meh. Also not sure on security updates. OnePlus is solid too for larger phones, but also not sure on updates off the top of by head.
@yashasolutions The instructions for the former package literally say to use pip...and with a clean (from brew) python3 install that doesn't work, including when trying with pipx.
Oh, and even if I had gotten it installed, turns out it still uses a version of the API that no longer exists.
And yes, my point of comparison for "Rust actually works here" was the Rust CLI you linked.
Finally taken a chance on a new apple silicon machine. Immediately run into problems with docker with the work image. Now have to decide how much effort I want to put into getting it working, versus sending it back and sticking with my x86 machine.
@splateric If it's docker-compose, specifying architecture flags in the compose file should allow you to grab the correct image (e.g. the x86 one) and have Docker emulate it. There's a perf penalty but sometimes that's a sufficient workaround.
I've got a slightly underused VPS with @bitfolk running #debian stable. Is it possible to install a #mastodon instance in a container and backup content to Dropbox or similar?
Basically, a single user instance with my random droppings and photos of my dog, etc. #mastoadmin
@Dtl@bitfolk Mastodon does have a Dockerized version, but for storage you need an S3 workalike, which Dropbox isn't. Backblaze B2 would work though, and is free for the first 10GB and cheap thereafter.
#MastoAdmin question: what are admins doing about media storage and bandwidth? The shop is on S3 + Cloudfront, and it's easily our highest cost on a monthly basis. What other options are there? How do people contain those costs?
A major difference between the #ActivityPub federation and the #BlueSky#Atproto (#Atprotocol) federation is that under AcitivityPub, used by Mastodon, all servers that need to send or receive data from other servers need to make direct connections to each other. This means many queued jobs and many connections, maybe thousands. This leads to the classic sidekiq queue problems when Mastodon instances have numerous users with numerous follows, and relays.
In contrast, in atproto, the user's PDS, Personal Data Server, doing equivalent work of a Mastodon server, for example, only makes a few connections to the relay server's fire hose to deliver and pick up messages. It never connects to any other PDS directly. Theoretically, a tiny #PDS on atproto can handle a considerable number of users. This seems to be an advantage.
Mastodon admins spend a lot of time and money fighting performance issues, database connection counts, and sidekiq queues because the server has to talk directly to other servers. But the PDS only needs to talk to maybe one, or possibly a few relays to get and send messages.
Here's a diagram of the atproto architecture. It appears quite a simple architecture.
@Jeremiah@admin Also, the perf issues with Mastodon are just that: perf issues with Mastodon, a thing that runs on Rails. If someone has a huge following such that heavy fanout is needed, there are (much) more efficient AP implementations out there.
I'm shopping around again for options to host masto.nyc outside my home. Right now, I'm considering:
Colocation Datacenters
Pros: We can host locally! And support NYC businesses. Much more affordable long term.
Cons: Still have to manage our own hardware.
Cloud
Pros: Easy to scale. Easy to maintain.
Cons: Difficult to find a local provider. Expensive.
In the meantime I'm looking for more concrete evidence of how much it would actually cost to migrate to cloud resources.