I keep getting asked to support writing rich-text-formatted posts in #Hometown (we already read them just fine). I finally wrote down, in this comment on this Github issue, a short essay outlining all my concerns with doing so:
Some of this is problems with Markdown, while some of this is problems with interoperability regarding any rich text rendering at all.
Fediverse tip, reporting
Don't forward reports to the user's instance admin unless you have reason to believe the instance admin is trustworthy. I have seen numerous instances where admins have shared reports with the target user and where the report has been used to harrass the person presumed to have made the report.
If you aren't sure, don't forward. Your instance admin can always choose to forward the report.
Any admins know of a good way to tell when it's time to put your mastodon-web and mastodon-streaming services on their own server?
Sidekiq is easy by watching the queues, but I can't tell when the puma or streaming services are getting overloaded. Any ideas?
I had actually forgotten that in December 2019 I was asked by The Verge to give my opinion on Jack Dorsey's Bluesky decentralization project. This is what I said at the time and, well, lol, I stand by it
In advance of deleting my Twitter account, I made this web page that lets you search my tweets, link to an archived version, and read whole threads I wrote.
I will eventually release this as a website I host where you drop your Twitter zip archive in and it spits out the 100% static site you see here. Then you can just upload it somewhere and you have an archive that is also easy to style how you like it.
This is yet another reason to write media descriptions whenever you can--large files can get lost in transfer and bandwidth/capacity varies widely between instances, so your media are not 100% guaranteed to federate. Your descriptions will make it through much more reliably, however, keeping your post useful even if the attachment is dropped.
@rose oh i see the problem is not that raspberry pi are hiring someone whose proudest professional achievements are a menace to their userbase
the problem is that fedi vegans are hunting them for sport
From now on this is my official explanation of the #fediverse:
ok so we've clearly all read Thomas Pynchon's The Crying of Lot 49. Remember W.A.S.T.E.? the network of trash cans run by societal dropouts? and somehow they manage to deliver letters from trash can to trash can? that's fediverse
instance media & space ramblings
Remote media was rampantly broken on this server since I've had to impose very strict cache restrictions to save disk space and, at one time, mass-deleted media to rescue the server from an overflowing disk that crashed the database. It's a real pleasure to start seeing media consistently again. Like if it were simply an all-text experience that's another thing, but seeing *some* media in patches and others blank was kind of maddening.
Now I can actually allow media caches of up to 7 days and even longer (!) if I want, and am requesting media files, especially profile avatars, that I had deleted as an emergency measure. The price is a slower initial loading time while media is fetched and cached, plus slower media uploads, but I think it's made up by reclaiming 18.5 GB in local disk space (this is while I was allowing only one-day cache of remote media), getting much roomier storage for literally pennies, and not being at constant risk of a whole-instance crash.
Between refreshing media and just normal use, the size of our media files in the remote bucket grew about 3 GB since yesterday. If this were on local disk the instance would already have crashed and/or I'd be running frantic media cleanups jobs. Aaahhh, the sheer peace of mind.
All right, the instance is running and media uploads seem to be working again, though there are sporadic failures that I'll be watching & tweaking for while we try this for a few days. Hang on, folks!
Wow cache is far and away the biggest directory of media files so far, and accounts/avatars alone takes up 4.9 GB. And that's with a blocklist a mile long including the biggest instances at mastodon.social and .online. No wonder media cache cleanup did so little, since it evidently doesn't do anything about cached remote avatars. Very glad to be getting all this off the server's limited disk space--now if only I could get the server to serve these images! :P
Accounts culled, though it doesn't seem to have done a huge amount disk space-wise. Running media file synchronization now.
I'm the tech support person on writeout.ink. Avatar image is a butterfly sitting on the mouth of an ink bottle.
A small instance for writers.