Fedia Discussions

Hi all. I was recently made aware that people have been getting error 429's and other error 500's when visiting fedia.io. My hope/expectation is that those will no longer happen now that I've moved back to a bare metal install, but if you do experience that, please comment below, or if that doesn't work, send me an emai to jerry@infosec.exchange.

Thank you!

Hi all. It took a while for me to get to it, but I have just completed rehoming fedia.io from containers back to a bare metal install. This should fix the issue with federation stopping. I'll keep an eye on it, though.

It seems like sh.itjust.works is the only defederated instance. Any reason as to why?

Hello. I will be taking fedia.io offline on Saturday, Feb 3 to rehome it to a different server. Since moving fedia.io to a container-based platform, federation has been very unreliable and slow. I'll be moving to a non-container-based/bare metal install, which should address the federation issues.

I get the threads, but there's no votes, no replies. Nothing. None of my comments show up anywhere if I look at the original instances. Ever since the 26th of December it's been a complete shitshow.

Edit: Didn't get any reply notifications for this thread either...

Assistência profissional para reparação e manutenção das caldeiras SAUNIER DUVAL

Assistência caldeiras CHAFFOTEAUX ET MAURY, serviços de assistência técnica especializada na reparação e manutenção de caldeiras e equipamentos para aquecimento central

Serviços de assistência tecnica profissional das caldeiras VAILLANT.

Centro de assistência técnica para reparação e manutenção de caldeiras e equipamentos termicos Ariston, venda de peças e componentes.

Assistência técnica caldeiras Ariston, serviços de reparação e manutenção.

Assistência técnica caldeiras CHAFFOTEAUX ET MAURY, serviços de assistência técnica especializada na reparação e manutenção de caldeiras e equipamentos para aquecimento central

Assistência caldeiras CHAFFOTEAUX ET MAURY, serviços de assistência técnica especializada na reparação e manutenção de caldeiras e equipamentos para aquecimento central

Assistência e manutenção de caldeiras, aquecimento central e energia solar térmica

Venda, comercialização e instalação de caldeiras, aquecimento central e energia solar térmica, assistência técnica profissional venda de peças e componentes.

Hi,

Every so often, when I try to browse to https://fedia.io through my browser bookmark, I receive an error resolving the domain. Firefox suggests https://www.fedia.io but navigating there gives me an HSTS error (picture attached, hopefully.)

Usually, if I check back 15 minutes or so after this occurs, https://fedia.io will load normally, and then https://www.fedia.io actually loads the landing page for:

Books.Infosec.Exchange A Bookwyrm Instance for Infosec.Exchange

I'm not quite sure if this is an issue with my network or a problem with the instance itself. However, I thought I would report it. Let me know if there is any other information I can provide that will be helpful in figuring this out.

I’m blocking probably hundreds of mags (all mags on Cloudflare sites like lemmy.world). The results of search queries are rich in posts from blocked mags. When I visit the post the sidebar shows that indeed that mag is blocked.

Note that if I simply browse the main timeline, the blocks work as expected.

I would normally report this to the kbin bug tracker but Codeberg deleted my account and it’s hard to create a new one.

When I look at https://fedia.io/all/newest right now there seems to be very little getting through today, with only 3 new threads in the past 10 hours.

Edit: 4 now that I've posted this one, and now I notice that they're all from local users.

I tried to block a couple communities from reaching my timeline and got the 500 error. These are the URLs the browser tried to visit when clicking the “block” button:

• https://fedia.io/m/castiron@lemmy.world/block
• https://fedia.io/m/humor@lemmy.world/block

I’ve had no problem blocking lemmy.world communies in the past. It’s just a problem today. And today I had no problem blocking communities on other Cloudflare instances (e.g. lemmy.zip) and non-CF instance lemmy.ml.

Confession: I still don't know what boost does here. It must do something bad because so rare do I see on a post "boost(1)" or "boost(anyothernumber)" for that matter. Should I also avoid "boost"? Or does the interface only show when our individual boosts?

#fedia

Uploading GIFs on this site has been hit-or-miss for the few months I've been here, but where they used to fail with an error page a while back, the GIF is now quietly discarded from the thread. Posting GIFs to this instance is broken from kbin.social as well (where the whole post fails) so it's not a front-end issue.

Sorry to bother you again jerry 😅

For a few days I've been noticing very long delays on both incoming and outgoing federation. I've noticed the delay on submissions, comments, and votes. Since it's happening on both incoming and outgoing it seems to be a problem on our end rather than remote instances.

For example, five hours ago a new submission was posted on @australia@aussie.zone (title: Therapeutic Goods Administration...), but this hasn't yet federated in as of posting this thread.

Around the same time I made a test comment out to @test5677754@lemmy.world, but the comment is yet to reach the external instance.

When I try to DM someone on the jlai.lu lemmy instance, I get “403 Forbidden”.

This is over Tor but doubt that’s relevant since jlai.lu permits tor, and most likely my msg takes this route:

my PC → Fedia server → jlai.lu (server)

That instance also seems to be federated with Fedia (users from there post on fedia mags). So for that reason I expect DMs to work.

I have ensured that I am not subscribed to any mags on centralized instances. E.g.

• lemmy.world (centralized by Cloudflare and by disproportionate user count)
• lemmy.ml (centralized by disproportionate user count)
• lemm.ee (centralized by Cloudflare)
• sh.itjust.works (centralized by Cloudflare)
• lemmy.ca (centralized by Cloudflare)

yet the main landing timeline is polluted with junky content from centralized instances. Apparently it’s the federated timeline of fedia not my home timeline with just my subscriptions. I found the subscriptions timeline in the top right corner to the left of my userid. very useful!

I would still like to browse the federated timeline but to filter out the above-listed domains. The user settings has a “blocked »domains” tab, but I see no way to add to that in the control panel. And from the content there is no “block domain” option, just a “more from domain” option. So overall there are bugs to fix and features needed:

• ~~(BUG) cannot add to settings»blocked»domains~~ (works, just undocumented.. must add one mag at a time)
• (feature request) the main federated timeline filter (a funnel icon) could use a way to filter out centralized instances
• (feature request) the expanded menu of a post should have a “less from domain” option
• [new] (feature request) add support for blocking whole instances configurable by each user, not just specific mags.
• [new] (feature request) ability to still see mentions in blocked mags. If I post something in a mag then later block that mag, mentions still trigger notifications (good) but the post cannot be visited.

Fixing the bug would not exactly accommodate all the needs because although I don’t want to see new posts originating from lemmy.world, I still want to see comments from lemmy.world users.

Looking at the (short!) list of defederated instances, I tried looking through this magazine to read about what caused some of the defederation actions -- unfortunately it looks like some of that information might've been lost in the mbin migration and subsequent cleanup?

Given the list's short length, would it be possible to create and vaguely maintain a list with a brief reason for the defederation and whether each is expected to be a temporary or permanent situation? There's a couple of communities I was interested in on lemmy.ml which for better or worse don't seem to have a great in-fediverse alternative.

Cheers!