ij (@ij@hofra.rocks)
I'm having a hard time trying to figure out why follow requests from e.g loops.video to my instance are replied with 401s from mastodon-web.
Secure Mode is off...
mastodon-web logs in DEBUG show various "Signature verification failed: Verification failed for..."
I'd love to hear your ideas on how to investigate further.
This seems to be only a problem with non Mastodon Instances...
thank you in advance 🥵
#fediadmin
Show Original Post
kevin (@kevin@fedi.kevinisageek.org)
During all of my server touching, I somehow managed to munge the emoji I had imported locally (dunno why I did that), missing things everywhere. A quick `tootctl emoji purge` and wait for them to resync from remote servers is sorting it.
Show Original Post
notes (@notes@enby.life)
Content warning:unsolicited advice for fedi admins of instances with accounts dedicated to instance announcements, mentions spam bots and CSAM (but separate incidents)
(🤍 Nova) PSA to Fedi admins: If you're going to have an announcements account that is not monitored for DMs, please consider linking one or more personal accounts of your instance's moderation team!
My system occasionally checks on instances for activity from their admins (simply because we're on fedi and are neurodivergent ​
​), and there have been times where we found instances with announcements accounts or personal accounts of instance staff that show no signs of activity (last post is more than a year old), which is bad if an instance is open-registration. We have seen open-registration instances with no visible activity from staff become infested with spam bots as well as CSAM, so we personally put possibly-abandoned instances up for review by the rest of enby.life staff, especially if the instance is a public instance (more than 50 active users per month).
#FediAdmin #PSA #Moderation
Show Original Post
snail (@snail@mstdn.crmbl.uk)
Getting fed up with spam/scam comments from #pixelfed (pixelfed.social) accounts. @pixelfed #FediAdmin
Show Original Post
AliveDevil (@AliveDevil@tauri.earth)
Want a cursed User-Agent?
Opera/9.71.(X11; Linux x86_64; uk-UA) Presto/2.9.177 Version/11.00
IP is not from Ukraine, but from Côte d’Ivoire (AS 36924).
Show Original Post
fedilore (@fedilore@mastodon.social)
An instance admin who I trust has tested this and confirmed that it does work.
This is only a PARTIAL fix, but it can prevent users of your instance from contributing to these harms.
https://mastodon.pnpde.social/@spielleitung/116296598330620006
Show Original Post
fedilore (@fedilore@mastodon.social)
Taking the block-evasion one step further, according to the thread the service doesn't set a user agent so it's not possible to block that way.
Again, according to the thread it does specify an ActivityPub client named "Zeigeist".
Would appreciate any feedback from admins about how to block a specific ActivityPub client.
Show Original Post
fedilore (@fedilore@mastodon.social)
The creator is making pretty clear that it's designed this way to make it harder to block.
Normally, you'd expect an LLM scraper to have a single (blockable) ActivityPub account doing the scraping.
This is designed so that everybody who uses the service has their identities harvested to steal people's data on the app's behalf.
Show Original Post
fedilore (@fedilore@mastodon.social)
If you feed somebody's posts into your shitty LLM without an explicit and reversible opt-in, you are violating the consent of fedi users.
This "Zeitgeist" app not only violates consent, but it also doesn't have a centralized ActivityPub identity that can be blocked or defederated.
https://alpaca.gold/@seldo/116229243453108157
Show Original Post
jaz (@jaz@toot.wales)
I would love it if I could query the database to find the account using a given app so that, for example, I can pin down whoever's using "SEO Article Bot" and politely nuke them from orbit.
As a managed-hosted service I don't have easy access to the database or command line, and none of the frontline moderator team will ever have access to the database.
Show Original Post
ij (@ij@nerdculture.de)
Sodele… nach der Umstelljng auf S3 Storage bei https://baltic.social/ war nun auch https://fedisocial.de/ mit der Umstellung dran.
Wenn man erst einmal ein funktionierendes Setup gefunden hat, das mit #Mastodon, #S3 Storage auf #Ceph radosgw und #haproxy auf der #pfSense funktioniert, ist das eigentlich dann relativ straigth-forward…
Als Nächstes kommen dann die 1.2 TB hier auf der Instanz dran. Das ist allein schon wegen der Datenmenge nicht ganz so fluffig…
Show Original Post
kongtol (@kongtol@gts.sangeunahna.com)
Strange, looks like this #gotosocial can't do federation with #threads
#fediverse #threadiverse #fediadmin
Show Original Post