Would any #mastoadmins have any idea why my blog is failing to verify? I have added the special link to my blog as instructed yet the link still does not turn green and I am at a loss to troubleshoot this any further.
Would any #mastoadmins have any idea why my blog is failing to verify? I have added the special link to my blog as instructed yet the link still does not turn green and I am at a loss to troubleshoot this any further.
Oh, Mastometrics is down ? "Profibited IP" says Cloudflare ?
Sounds like an interesting story is about to come out
All #MastoAdmins, the yearly stress test is officially over. Austria has won #Eurovision. Traffic should slow down again. Thank you for your participation.
If any #mastoadmins want to test this out themselves, this is the query I used to find the messed up polls:
SELECT
polls.created_at
, polls.id
, polls.account_id
, polls.votes_count
, pv.total_votes
, polls.status_id
, ARRAY_LENGTH(polls.options, 1)
FROM polls
INNER JOIN users ON
users.account_id = polls.account_id
INNER JOIN (
SELECT
poll_id
, COUNT(*) AS total_votes
FROM poll_votes
GROUP BY poll_id
) AS pv ON
pv.poll_id = polls.id
WHERE pv.total_votes > polls.votes_count
ORDER BY polls.created_at ASC;
then this to find the polls that are not messed up within the same time period:
SELECT
polls.created_at
, polls.id
, polls.account_id
, polls.votes_count
, pv.total_votes
, polls.status_id
, ARRAY_LENGTH(polls.options, 1)
FROM polls
INNER JOIN users ON
users.account_id = polls.account_id
INNER JOIN (
SELECT
poll_id
, COUNT(*) AS total_votes
FROM poll_votes
GROUP BY poll_id
) AS pv ON
pv.poll_id = polls.id
WHERE
polls.created_at >= '2025-03-04 23:03:26'
AND pv.total_votes <= polls.votes_count
ORDER BY polls.created_at ASC;
The good ones all have options array length <= 4 and the bad ones all have options array length > 4
The way I increased the poll options was by modifying MAX_OPTIONS in app/validators/poll_options_validator.rb. This appeared to work prior to v4.3.4.
Edit: Adding this here for visibility. This was not a bug in the Mastodon code, but rather the result of me increasing the max poll options on the web server but not on the server running the sidekiq processes.
More details here: https://github.com/mastodon/mastodon/issues/34662
Mastodon admins currently getting slammed by Earth's least creative spammer really shows how awesome #mastoadmins are if you haven't seen this spam yet.
But bruh we need more spam fighting tools. This spammer is literally sending identical DMs to probably thousands of users and we don't have a stock tool that allows us to auto block/flag it.
I've been experimenting with enabling translation on my instance and since I've seen zero documentation about how to configure LibreTranslate with a purchased api key, I'm going to share my findings here.
Pretty much every guide out there for enabling translation on a Mastodon instance using LibreTranslate assumes that you are going to be setting up the LibreTranslate server yourself. That's admirable, but translation is pretty resource-intensive. When I tested this on my instance, it was taking about 2 seconds to translate a post, and even longer for longer posts. Plus there were some languages that weren't working at all. That was probably on me for not setting up the language packs correctly. Maybe I'll give it another try, but somewhere in the middle of wrestling with the translation server, I realized that I'm here to run a Mastodon instance, not a LibreTranslate instance, so I went and purchased an api key from LibreTranslate for their lower tier of $29 a month (good for 80 translations per minute). Based on the average donations we get each month, that seemed a reasonable cost that we could afford. The trouble was, configuring the instance to use the api key didn't seem to be working at all.
Now if you go to https://libretranslate.com it lets you play around with the api and shows what the post request and the subsequent response looks like. In the post request and in the api documentation, the endpoint for the translation service is:
https://libretranslate.com/translate
but if you set LIBRE_TRANSLATE_ENDPOINT to that value in your .env.production file, it won't work. After a bunch of googling and experimentation, I finally went and looked at the pull request for this feature on GitHub. And that's where I saw that in the code for the post request it takes the configured LIBRE_TRANSLATE_ENDPOINT value and then adds the "/translate" at the end of it.
Even though I was sure I had tried this before, I set LIBRE_TRANSLATE_ENDPOINT to:
Without the "/translate" on the end. I restarted the web service and cleared the cache and it started working perfectly.
It'd be nice if any of this was actually documented somewhere.
@gnulinux
> Vielleicht kann diese kurze Vorstellung dazu beitragen, damit ein wenig mehr Leben in das Forum und die Chatkanäle kommt.
Das wäre auf jeden Fall echt nice
#fediadmins #fedimods #mastoadmin #mastoadmins #mastomod #mastomods #fedimins
*insert that Bernie Sanders meme here where 'Once again' he asks us to support our Mastodon instance admins*
#MastoAdmins's can easily help the #Tor network by installing the Tor daemon on the linux server and configuring their web server to be a #WebTunnel bridge
disobey.net does it (https://metrics.torproject.org/rs.html#details/7E12D6CACBA1051FD23A48482E091257CD4701BC), you can too!
"Hiding in plain sight: Introducing WebTunnel"
https://blog.torproject.org/introducing-webtunnel-evading-censorship-by-hiding-in-plain-sight/
Attention Beige Party-goers!
Ok! Streaming service appears to be working now! Long story short, I think I misinterpreted some of the upgrade steps for 4.3.0. One of the major changes is that the streaming service got moved over to a separate docker image. Well I updated the yaml file to point to the new image, but I missed a step because the build for the streaming service also has to point to a separate streaming docker file.
Ok, long story even shorter: pretty sure the streaming service was broken since the last update, but due to the nature of docker containers it was continually restarting, so it would work in fits and starts and then die again.
I did hear some reports that feeds seemed to be "stuck" and then would update after several minutes, so that would seem to fit with that theory. Weird thing is that every time I checked myself it seemed to be working, but I didn't go into docker and actually check the status of the streaming service. I have done so now and everything seems to be up and healthy, so I think we are good.
Anyways, welcome to version 4.3.1, and thanks for bearing with me while I figure all this out!
Beige-bless
PS: If any #MastoAdmins, are having this issue, this is where I found the solution:
Question for #MastoAdmins. I just did the upgrade to 4.3.0 and everything seems to be working except for notifications. I ran the pre and post deployment database migrations, and the old notifications got pulled over, but no new notifications are showing up. Anyone else have this problem?
Editing this because I was able to resolve this issue by rebooting the web server. I'll leave this post up in case anyone else has this problem.
Hurrah! I've greenified the PKU Talk mastodon server - massive thanks to @TangerineUI - the code was so nicely organised, it was a breeze to CTRL-F relevant colours and replace.
Now thinking about making a tool to help generalise Tangerine UI into something users can provide their own colours...
You can get Tangerine UI here for your Mastodon server: https://github.com/nileane/TangerineUI-for-Mastodon
Need help please!
I'd like to know, if it is possible for a Mastodon server admin to add or remove followers from an account other than its own, without the person (the account owner) knowing/being notified?
Maybe someone out there or @FediTips knows and could give me some insights?
@zvavybir
You may change length limit and add markdown depending on the #Mastodon flavour that you have in your server. Here is an example: https://climatejustice.social/
To help you choose if you install and maintain a better instance, you may read my considerations on flavours and forks there: https://social.coop/@eric/109421900837608818
It's a bit tempting to give Mastodon Glitch a try.
- https://glitch-soc.github.io/docs
- https://github.com/glitch-soc/mastodon
Seems like switching back and forth between Glitch and regular Mastodon should be pretty seamless.
Curious to hear about other people's experience, things to watch out for.
Hey #MastoAdmins!
We've recently seen a fairly large uptick in racist/troll accounts and instances surfacing over the last week or so (thankfully, away from here for now). We're interested in sharing work with others, and we've figured a shared/maintained block list of these would help reduce duplicate work. We're aware of the @oliphant block lists, but we're curious if anyone's also setting up a "US Election Gaming” list as well.
If this is helpful to anyone, I recently made a tool that lets you copy blocklists from Mastodon servers that publicly share this information in a format that can be imported to your own server, if you're an admin.
A use case for this would be: I trust the admin of XYZ.social, l want to block all the same servers they're blocking.
https://stefanbohacek.com/project/mastodon-domain-block-exporter-script/
Hey #mastoadmins I run a small server for friends and me. I noticed when I click on trending hashtags I never see much. I feel like I should see... something. Have I configured my server wrong? #mastodon #sysadmin
Das ist sicher etwas für #Mastoadmins und Moderator:innen, was das @nawik hier teilt. (Auch wenn ich hoffe, dass wir das selten bis nie anwenden müssen)
@mastodon_mobile_apps Nice! I hope this will be extended to third party servers as well.