It just casually says version .
.
…but behind that version number are not only the @Mastodon developers, there are also (real) people like @quartje and @twijs making sure everything stays up-to-date, tested, secure, accessible with a research and education Single Sign On have the luxury of entering the Fediverse with a personal account and functional group/company account!
Give your Mastodon heroes a high-five when you see them
Every year we ask the community builders on the social web to tell us how they're doing, and what tools and resources organisations like IFTAS and others can be working on to support decentralised communities.
Last year we heard from roughly half the Fediverse, plus voices from other social media and community builders across the web.
If you haven't filled out our ten minute survey, time is running out!
Massive npm supply chain attack
This did not hit Exquisite.social nor Exquisite.tube - but instance owners should definitely check if they upgraded their instance in september!
Gup.pe, qui gérait les groupes @gup.pe, s'est fait piquer son nom de domaine avant expiration (c'est possible avec les .pe ). Tous les groupes sont donc malheureusement amenés à disparaître tôt ou tard... dont notre groupe marseillais @marstodon. Voir https://social.growyourown.services/@FediTips/115164282623836102
J'ai fait une demande création de groupe auprès de https://about.fedigroups.social pour le remplacer, la demande va être revue et validée manuellement. À suivre vite :)
HEY LOCALS!
Are you in any a.gup.pe groups?
Because you aren't anymore. The domain got snatched BEFORE expiration, surprising everyone.
(DO NOT USE .PE DOMAINS, they ALLOW this. It's insane.)
Here are more details:
https://social.growyourown.services/@FediTips/115164282623836102
You should find your people and set up a replacement group. People who know are suggesting:
https://about.fedigroups.social/home
...as one possible replacement, but there are others as well.
Also, see announcements for our limit and suspend schedule, I'm not waiting for the buyer to set up a better spam engine, because they will.
Hi folks, we just took a really devastating action on gup.pe. Most know and love the valuable group sharing tool we have grown to know and love has been taken over by a domain squatter.
Out of an abundance of caution, #mstdnca has sadly taken the action of suspending this domain.
https://about.fedigroups.social/home may be an alternative.
I'm really sorry for this, I know that many have enjoyed a.gup.pe including myself.
Leider musste ich die Domains gup.pe (und a.gup.pe) sperren, weil der bisherige Betreiber sie verloren hat (Notiz an mich selbst: keine .pe-Domains benutzen).
Wann soll das #FediCamp 2026 stattfinden?
Wir brauchen eure Meinung! Macht mit bei unserer Termin-Umfrage und gestaltet das Camp mit: https://fedi.camp/news/2026/poll/
If you are a #MastoAdmin #FediAdmin, you may want to purge a.gup.pe from your server.
In Mastodon, go into admin > Moderation > Federation > Add new domain block. Create one for the domain name "gup.pe" (subdomains are included) with "suspend" severity. Once added, go into the details for the newly added block and you'll find the "Purge" button right at the bottom of the page.
Once the domain is purged, the list of severed follows will no longer be available to local users.
Question for Mastodon Admins/moderators:
If someone has unconventionally reported a large number of accounts, by simply providing their Mastodon handles via a textual DM, rather than using the usual report function within the web interface, and I search these remote accounts from the accounts page of the moderation section, every search comes up with "nothing here". I then cannot take any further action on the search, as my instance is not seeing any accounts to take action on. Is there something else I can/should be doing to be able to suspend these accounts?
Thanks everyone.
#MastoAdmin #FediBlock
Running a Mastodon instance? Keeping it healthy can be a hassle — but this can help!
Check out:
https://github.com/johndotpub/mastodon-maintenance/
- Clean up inactive/non-existent accounts
- Remove old/orphaned media files
- Export, purge, and audit blocks
- Rebuild feeds for optimal performance
Save time and prevent headaches. Contributions, feedback, and ideas are welcome — let’s make self-hosting Mastodon more reliable for everyone in the Fediverse
Buenas noches pues es de noche aquí en esta tierra #salvadoreña , #info #viral #toot #actualidad #fediverse #fediverso #mastodon para #tooters muy inteligentes #mastoadmin
You guys. Mastodon made it into Trivia Night.
We might be making it into the mainstream. This is not a drill.
NEW ART ALERT!
Hey Garden State Social! Thanks to everyone on the contributing to the cost of running the server I have commissioned more art for the server.
This new piece is by @VEXED and be sure to boost and give them some huge thanks for this work!
This will be our new server header image and can be found on our about page here: https://gardenstate.social/about
I'm curious about something while upgrading #glitchsoc
I keep getting this, or similar, during every upgrade. I've gone through the depends lists and tried to resolve this, but for some reason, these warnings will not clear.
What am I missing?
#mastoadmin #mastodon #selfhosting
➤ YN0000: · Yarn 4.9.4
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 1s 543ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ react is listed by your project with version 18.3.1 (p68bdc1), which doesn't satisfy what emoji-mart-lazyload and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 18.3.1 (p9d1adc), which doesn't satisfy what react-router-scroll-4 and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-router-dom is listed by your project with version 5.3.4 (p7a2e69), which doesn't satisfy what react-router-scroll-4 requests (^4.0.0).
➤ YN0002: │ @mastodon/mastodon@workspace:. doesn't provide postcss (pfe5f4d), requested by postcss-preset-env and other dependencies.
➤ YN0002: │ @mastodon/mastodon@workspace:. doesn't provide redux (p7bebfc), requested by react-redux-loading-bar and other dependencies.
➤ YN0002: │ @mastodon/mastodon@workspace:. doesn't provide rollup (p04c650), requested by @optimize-lodash/rollup-plugin and other dependencies.
➤ YN0002: │ @mastodon/mastodon@workspace:. doesn't provide terser (pf7324a), requested by @vitejs/plugin-legacy and other dependencies.
➤ YN0002: │ @mastodon/streaming@workspace:streaming doesn't provide eslint (p627553), requested by typescript-eslint.
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ 2 packages were added to the project (+ 2.27 MiB).
➤ YN0000: └ Completed in 58s 943ms
➤ YN0000: ┌ Link step
➤ YN0008: │ core-js@npm:3.45.1 must be rebuilt because its dependency tree changed
➤ YN0008: │ msw@npm:2.10.5 [15ffb] must be rebuilt because its dependency tree changed
➤ YN0008: │ tesseract.js@npm:6.0.1 must be rebuilt because its dependency tree changed
➤ YN0008: │ core-js@npm:2.6.12 must be rebuilt because its dependency tree changed
➤ YN0008: │ esbuild@npm:0.25.9 must be rebuilt because its dependency tree changed
➤ YN0008: │ @parcel/watcher@npm:2.5.1 must be rebuilt because its dependency tree changed
➤ YN0008: │ unrs-resolver@npm:1.11.1 must be rebuilt because its dependency tree changed
➤ YN0008: │ bufferutil@npm:4.0.9 must be rebuilt because its dependency tree changed
➤ YN0008: │ utf-8-validate@npm:6.0.5 must be rebuilt because its dependency tree changed
➤ YN0008: │ @mastodon/mastodon@workspace:. must be rebuilt because its dependency tree changed
➤ YN0000: └ Completed in 27s 507ms
➤ YN0000: · Done with warnings in 1m 29s
Weird behaviour in mastodon web client (v4.4.3) that I've noticed happening fairly often:
When I turn my laptop on in the morning and fire up the browser, I see my last post sitting in the compose box. This is not a draft, it's something that's already been sent and replied to.
Bug?
ways in which being a fediverse instance admin is a lot like being a cyberpunk edgerunner
• largely thankless job
• steadily upgrading hardware is necessary
• burnout is a certainty
• failure is guaranteed eventually
• it's just about how long you can keep going
• everything only ever lasts for so long
• you don’t make a name for yourself by how you live... but by how you die (aka whatever fedi meta drama ends up shutting down your instance)
ΩΩ
#FediAlgo v1.1.19 is deployed. Minor bugfixes and improvements to the customizable timeline algorithm / filtering system for your Mastodon feed.
* Link: https://michelcrypt4d4mus.github.io/fedialgo_demo_app_foryoufeed/
* Code: https://github.com/michelcrypt4d4mus/fedialgo_demo_app_foryoufeed
* Video of FediAlgo in action (slightly out of date): https://universeodon.com/@cryptadamist/114395249311910522
After upgrading the server, I enabled full text search. Give it a try. You can actually search for things properly now.
I appreciate the people who donate to keep this instance running smoothly: https://hcb.hackclub.com/donations/start/econ