Hmm I probably have the most ridiculous #robotstxt for a #Misskey instance right now lol. I just want to let #Mojeek and #Marginalia crawl #Makai and make sure to keep out #Google and the AI scrapers... :satrithink:
A thread on the lack of courage of some #fediadmin that I will name because they have step over one of my limits. @thurisaz has enacted a ban of the instance (mastodon.projetretro.io) with the following messages : "Admin is nazi apologist" (see https://fba.ryona.agency/?domain=projetretro.io)
To say that I'm shocked to be so carelessly called a nazi will be an understatement. I tried to reach over to polyglot by mail to understand the reason of the the ban to no answer so far .
1/?
While my original proposal to hide images in order to highlight the importance of well-written alt text did not gain a whole lot of traction, I'm still glad there was some conversation, and grateful to everyone who is still interested in joining in.
If you do participate, I would love to hear from you!
I've received my first "report" on hugs.lgbt and I'm very confused ....
Two posts were reported ... neither were from hugs.lgbt posts ... one was a reply to one of my posts by a mutual, the other was a post by that mutual without any hugs.lgbt involvement ...
Did I receive the report because one of those was a reply to a post of mine?
But why the other one?
Also very confused as to why ... the first was a thank you reply to a post from me.
The other was a meme.
The category was "other" but no notes or any other information that I could discern 🤔 🤷♂️
for a year and a half, images from mstdn.social have been unloadable on my instance
pings and traceroutes to mstdn.social from inside of my network die right at the router:
Request timeout for icmp_seq 4
92 bytes from 192.168.0.1: Destination Port Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 5400 178b 0 0000 3f 01 1e6d 192.168.0.200 116.202.14.219
no changes i made on my network fixed it, and i began to suspect my isp had blocked the ip
............
................
............ it turns out, my ipv6 was disabled and mstdn.social needs it for its cdn 😭
as I alluded to yesterday, I actually wrote something about the problem with #fediverse link embeds, how they potentially DDoS servers, and how we can (kinda) fix it.
#fediadmin friends: are there any downsides to turning on the "Content cache retention period"? I've noticed that my database's content cache table is very large, and I realized I hadn't set a retention time for it.
Is there an all in one "So you want to run a fediverse instance" type guidebook in relation to legal, moderation and long term sustainability tasks?
Things like templates for Privacy Policies, Server Rules and About sections, understanding moderation tasks and the importance of having multiple administrators, funding plans.
Is there an all in one "So you want to run a fediverse instance" type guidebook in relation to legal, moderation and long term sustainability tasks?
Things like templates for Privacy Policies, Server Rules and About sections, understanding moderation tasks and the importance of having multiple administrators, funding plans.
:heart_trans: Request for IT assistance :heart_trans:
Hi friends! Our SysAdmins are still blocked by a network issue that prevents our migration to the new servers. We are running out of ideas and would appreciate any possible support. If you have or know someone who has experience with IPv6 networks, then please contact me or another member of our staff. We would earnestly appreciate any help or advice!
The problem, as I understand it, is that traffic fails to pass through our OPNSense firewall. We have a /48 block allocated on the WAN side, and want to expose a public IP from the LAN. See this reply for a longer description and some discussion.
IFTAS releases a practical guide for fediverse admins and platform creators (among others) subject to the EU’s Digital Services Act. Which would be…everyone.
Remember, hosting a fediverse instance is a collaborative effort, not just with your co-admins, but your users and admins of other instances. Any knowledge you can share about your experiences serves to strengthen the larger federated community.
New spam bot wave with multiple accounts - search for hashtag x4 to find them all. Some of them also include auth links to mastodon instances, looks like a phishing attempt or something.
HIGHLY recommend Fediblock for user '@MKULTRADiamond' as they're tagging random users and spamming porn with no CW. Receipts attached in the screenshot.
Edit: The whole instance is Freeze Peach. Toss it in the trash.
So....I keep thinking about this Sharkey migration and as I see it, I have 2 options:
Attempt to re-migrate to beaware.live (my main domain) even though I briefly already had an instance there and risk potential federation issues.
Migrate to beaware.social (new domain) and redirect beaware.live to it which shouldn't cause issues.
In all honesty, if I could be almost positive I could do the first option with little or no federation issues, I'd rather go that route. BUT, if I can't get a definitive answer on if that would work or not, the second option is always there....any advice?