jrollans.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Can anyone recommend some relatively affordable managed #Mastodon hosting?
We've been with the absolutely fantastic Masto.host since starting Writing.Exchange in 2017, but it's become prohibitively expensive -- especially for a community of only ~250 active users, as our hosting costs are about to increase another $50 to $589/month this month.
My essentially single-user Mastodon server is becoming more expensive to run on @mastohost without doing some cleanup. My problem is that I don’t actually know how/what to clean up.
Early on I used relays to improve federation; I think there’s a TON of data in the db from that which could just be purged, but I don’t want to accidentally lose any user data. A couple of years ago we did run `tootctl statuses remove` but I might have still had a relay enabled more recently.
I think we should have a #MastoAdmin pin. I think I deserved one. What do you think @Gargron?
It’s been 5 full days without me SSH-ing somewhere. I think it is a new record since I started my #homelab. I couldn't take it anymore and upgraded my #GlitchySocial Mastodon instance to 4.6.3 today. While on vacation. While away from servers.
#selfhost #SelfHosted #selfhosting #vacation #Mastodon #mastoadmin
This will very likely be my last post here, and it's unlikely I'll be able to respond to any comments.
I've run Strangeminds for about three and a half years. Most of the time it's been fun, other times (when things go wrong) it has got very stressful.
It's time to move on. I've had my fun but this server didn't get as busy as I'd hoped it would. I'll be moving to #Universeodon later, and I know I'll be in very capable hands there.
There's still a few 'active' accounts on here, but they've all had plenty of notice of the impending shutdown, so I won't loose any sleep if they haven't prepared for this.
This just leaves me with one final thing...
[Me] Computer, this is Danny, request security access
[Computer] Identity acknowledged
[Me] Computer, initialise auto destruct, 72 hour silent countdown
[Computer] Destruct sequence completed and engaged, awaiting final code for 72 hour silent countdown
[Me] Code 0 0 0 Destruct 0
Tencent (43.173.128.0/18) decided to scrape phpc.social, badly, slowing things down for everyone else.
That IP range has now been blocked. Sorry for everyone having to endure slow performance of late.
@mastohost Do you run a self-destruct for Mastodon instances you host then suspend? canada.masto.host is still in my database of instances when I look at federation... #MastoAdmin
I added a throttle for unauthenticated accesses to /tags on our public Mastodon instance. The rate limit of 50 in 10 minutes triggers quickly, and for the first time this year, our media cache usage has been slightly decreasing since.
A toggle to completely disable unauthenticated access to hashtag search would curb the current wave of scrapers quite effectively.
I'm curious how the Mastodon/Fedi admins in California are thinking about SB 976. The law has a pretty broad description of an "Addictive Feed" but it seems like the linchpin component is that the feed be driven by information provided by the user.
It seems like a stretch for this to mean feed self-curation ("following" a user or hashtag feed)... but perhaps an uncharitable read might imply the Home feed is a violation of this law? It seems like a leap (to this non-lawyer) to claim that as "information provided by the user"
Full Text: https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202320240SB976
Kurz weg, und wieder da.
Mit 4.6.3, wieder tootata.
Glücklicher Weise kenn ich mich mit Aktualisierungen besser aus als mit Reimen.
Bitte wieder weiter tooten
https://github.com/mastodon/mastodon/releases/v4.6.3
We have published a new blog post, explaining how we run #MastodonAfrica inside a #FreeBSD #Podman #container.
「Mastodon and Related Infrastructure with Podman Containers」
We just released Mastodon 4.6.3, containing several bug fixes.
Full release notes and update instructions are available on the GitHub release page.
RE: https://mastodon.social/@mastodon_releases/116856288361721077
☑️ Mastodon v4.6.3
https://social.la10cy.net/@mastodon_releases@mastodon.social/116856288423042483
What is the difference between "suspend" and "reject" in the context of account moderation via the web interface? #mastoAdmin
I'm thinking reject sends a rejection email while suspend is silent?
@matt_birchler fork of @TangerineUI is now installed as an optional theme on Listodon. Yay!
Not to let the cat out of the bag prematurely, but...
If you were going to start posting about cool servers that aren't run by Mastodon GmbH on the @Mastodon account, which hashtag would you use?
#Mastodon #Fediverse #MastoAdmin
| #ServerFeature: | 0 |
| #ServerSpotlight: | 0 |
| #ServerHighlight: | 0 |
| Something else? Comment please!: | 0 |
I'm using the extended web interface of the Mastodon instance I'm on. This allows for multiple columns with different content. I created one column to follow hashtags, by searching for a hashtag and then selecting "pin" in the column in which it shows the resulting posts. This column offers the option to include additional hashtags, and then I get a field where I can enter additional hashtags I'd like to show up there (see screenshot).
I can enter four additional hashtags by entering the name of the hashtag and pressing enter. If I enter a fifth one, when I press enter it just disappears. It doesn't stick.
So apparently this is limited to a maximum of five hashtags per hashtag column.
This feels like a bug to me, or a rather arbitrary limitation that doesn't make a lot of sense. Before I create a bug report, I was going to ask, is this normal? Is this deliberate? Is it a feature? Or is it indeed a bug?
For reference, the current Mastodon version on this instance is 4.5.13.
@stefano Any idea?
If you're running a public Mastodon server, it is really important to set aside running costs for three months. Leave this money in a separate account if possible, and do not touch it for as long as your server is running.
This three month set-aside means you can guarantee your members three months warning if you ever decide to close the server, which is plenty of time to move accounts. This gives your server credibility both with existing members and potential new members.