Hear me out.

SomethingAwful forums are notoriously "human," because they charge $10 for a user account. They don't have problems with spam/scam/shenanigans that exist on platforms where accounts are free.

Fediverse instances are not currently monetizable - and they should stay that way. But there are still costs to operating one, especially if it's very popular.

Instance admins charging a minimal fee to register a user account would address both of those concerns, especially the former, especially in light of how the Nicole thing has taken a horribly dark turn.

Over the past few days, I haven’t been able to access fedia.io over my cellular network, but it is fine over WIFI. I don’t know if the problem is on my end or Fedia’s. Its happening on every device and browser I’ve checked on or hotspotting through my phone.

I get a “SSL error”, “can’t securely connect to server”, “HTTP ERROR 408”, or “PR_END_OF_FILE_ERROR” depending on the browser.

Someone on that one site fixed a similar issue by updating the site’s DNS IPv6 configuration. I don’t know if that helps.

Hi @jerry@fedia.io -- seems like /active is broken again for some reason. Didn't see any upgrade news or anything so not sure what the cause might be. I can try to help troubleshoot, so please let me know if I can do anything to help.

Thank you!

Hi. Just shooting out a bugpost in case it's helpful.

Today, I engaged in some mild trolling and flew too close to the sun with my satire, and my post was removed from conservative@lemmy.world. The removal happened on Fedia quickly after the Lemmy removal.

A quick convo with the mod there had the post reinstated. It's now visible on the original instance. That reinstatement occurred about 10 hrs ago.

However, the fedia version is still showing 'removed by moderator' as the status.

So, seems like 'removals' are federated quickly. However, 'reinstatements' are not federating out or are doing so with substantial delays.

https://fedia.io/m/conservative@lemmy.world/t/1895138/Do-all-conservatives-hate-immigrants-Do-I-HAVE-to-hate

https://lemmy.world/post/26613790

It seems like whenever I post things to m/random there is a long pause and then sometimes an error message.

Error 503 first byte timeout

first byte timeout

Error 54113

Details: cache-lga21954-LGA 1741291495 2045459759

Varnish cache server

This time, the whole site was unresponsive for a minute afterwards. Did anyone varnish the cache server lately?

#fedia

Wondering if anyone has had success with an automod. This one was brought to my attention, which I'm told "should work," but I would be interested to know other people's experiences.

Sorry if I'm in the wrong place. Is there a setting where I can turn off people's ability to PM me? The spamgirl is annoying me, and I'm sure more will follow in her wake.

On other sites with spam issues, I'd turn off the ability for people to PM me and, if they asked on a thread I was on, I'd either re-enable PMs or add them to an approved users list. I thought I'd seen that ability here (I'm on the plain web version of fedia.io), but may well have been confusing it with some other site.

Thank you!

Folks in sopuli.xyz are not seeing posts to /m/santafe. It was suggested I go to https://lemmy-federate.com/ to submit m/santafe@fedia.io for federation. But I would need to be an admin on fedia.io to do that, it seems. Instead I am a clueless noob, trying to learn, as we all create the fediverse. Suggestions and assistance would be much appreciated!!

As mod of the Privacy mag I got an alert for this “thread”:

https://fedia.io/m/privacy/p/1332654/Hey-what-s-your-password-Nice-try-My-password-is-Tuta-MailDoesntLetThatHappen

I don’t quite have a handle on k/mbin’s relationship with microblogs. Seems bizarre that (IIUC) someone somewhere in the fedi used a privacy hashtag, which was then enough for the status to appear in the privacy mag microblog timeline, which then leads to a mod having power over it.

What does it even mean to moderate that? I guess the concrete question is, if I press the “reject” button, what happens? Does that remove a copy of a microblog status that is cached on fedia.io? If yes, isn’t it strange that a mod has the power to cancel a microblog that happens to use a hashtag that incidentally matches the name of a mag that the mod controls? Or does it just remove the content specifically from the privacy microblog timeline, and not the timelines of other hashtags used in the same status (e.g. security)

cross-posted from: https://lemm.ee/post/52454753

Since the last update I've not been able to log into my fedia-account using interstellar. I keep getting the 500 internal server error. I can log in with my browser. Is fedia.io/mbin not supported anymore? As far as I know interstellar is/was the only app supporting mbin/fedia.

My apologies for the recent spate of problems. I think I’ve narrowed the problem down to the /m/fediverse and /m/random magazines. For some reason, mbin is generating an enormous amount of outbound delivery messages for these two magazines. I first tried removing the hashtags from /m/fedivese, but that was only a quick fix. So I deleted the magazine. (Note, the notifications appear to be related to the “microblog” function, and were originating from accounts on lots of mastodon instances, so I think there is a bug somewhere).

I noticed /m/random doing something similar. I have removed all the subscribers from that magazine to try to reduce the number of notifications it is sending. I don’t know if that will help - I have a feeling the instance can’t keep up with that happening in both random and fediverse.

Anyhow, the queues are draining fast now. I purged about 600000 queued delivery messages that (based on a random sample) all appeared to be associated with fediverse and rando

This time it seems like federation to Fedia from elsewhere is working okay, but that federation from Fedia to elsewhere is not.

@jerry

Just noticed that my comments and posts from the last 24 hours don't seem to be appearing on outside instances at all.

Not seeing any new content for the last few hours, figured I would make a note of it.

The following instances will be offline briefly on Saturday, December 14 from 9am ET / 2pm UTC for approxmately 10 minutes: infosec.exchange infosec.town infosec.pub pixel.infosec.exchange books.infosec.exchange matrix/element.infosec.exchange relay.infosec.exchange meetup.infosec.exchange video.infosec.exchange infosec.press infosec.place fedia.io fedia.social elk,.infosec.exchange infosec.space convo.casa

The servers supporting these instances require a reboot. The Dell servers these instances run on take a very long time to boot, so I am estimating 10 minutes of downtime. It could be more, could be less.

We use live patches to minimize reboots needed for patching, however Ubuntu only provides livepatch support for a year, which is how long most of these systems have been running for.

This may be more of a client-side problem but the searching capabilities of mbin as a whole are so dreadfully bad. whenever i need to find a person or a community i first try fedia for good mesure yet most of the time it's not worth it as it doesn't show me what i want, afterwards i go into lemmy or mastodon find the thing i was looking for input it into the url and only then can i follow the person or community. And for apps like interstellar it's even worse since you can't input an url so you have to do it by logging into the browser version first. It's even harder to find people since for whatever reason magazines isn't showing them at all most of the time and the people option doesn't include a search option so your best bet is using global search for a chance that the specific person has been tagged in a post somewhere in the abise... Sorry for the gramatical errors btw. Oh and you can't follow hastags in mbin from what i have seen and tried...

We seem to be having trouble with a handful of the larger lemmy instances, as well as some misc other instances even though these instances aren't dead-dead: https://fedia.io/federation (at bottom of page - "Dead Instances").

I thought maybe it would've been a problem with a specific lemmy version, but there are several versions in the list and also some still-living Mastodon instances that are running reasonably up-to-date versions.