Search

Items tagged with: mastoAdmin


Here's a #mastoadmin tip: Use your powers of custom CSS to make Mastodon more accessible. The default link highlight colour (both 3.x blue and 4.x purple) contrasts are not WCAG compliant.

Illustrated below – we also highlight mentions and hashtags like links to make them easier to see – I find the default of "usernames are not quite white, but it's hard to see the difference" pretty distracting.


I'm a little surprised to see a lot of people posting domains in #FediBlock that any competent admin should have blocked on day 1.

Start with the weirder.earth suggested instance blocks, which are generally bigger/more active ones: github.com/weirderearth/weirde…

Tenforward.social has a much longer list with links to admin announcements, with reasons: wiki.tenforward.social/doku.ph…

Here's the current flipping.rocks list: flipping.rocks/about/more#unav…

#FediBlock #MastoAdmin



#MastoAdmin #FediBlock

The admin of journa.host is publicly using and linking a scraping utility to track what instances have silenced or suspended his own.

This scraping utility is using code created by Kiwi Farms, and is hosted on the same domain as an instance he himself has suspended. So he'll suspend the instance because others have - but he's happy to use something they host.

In my opinion, this information has destroyed any good will he might have had left.


Yes, running single-user instances of Mastodon is resource-intensive.

I don't think hosting costs scale with followers though. My single-person instance with 1500 accounts has tripled its followers in a week and it's comfortably within the resources available to it with 25 €/month of expenses. Load has barely changed.
respublicae.eu/@praetor/109295…

Moderation and other #MastoAdmin costs however scale with the number of eyeballs, I suppose.


that's the screen I (and probably every #mastoadmin) was checking regularly in the last few days 😁
Our instance is not that big, but seems to be integrated in the network, we hit 500k 1.5 weeks ago, steering towards 1M events/day.
It's really interesting when you're hosting the hardware yourself (especially as a hobby project) and can't easily scale up CPUs, but switching to nvme really payed off. We currently run 2 sidekiq processes at 10 treads each, with basically zero queue backlog.