this post was submitted on 05 Mar 2024
3 points (100.0% liked)

Fedia Discussions

1 readers
1 users here now

founded 1 year ago
MODERATORS
 

I’m trying to access this community from fedia.io:

https://sopuli.xyz/c/french

Searching for that URL or [email protected] yields nothing. If I manually visit this URL:

https://fedia.io/m/[email protected]

I get a 404.


btw, this post would be better suited in

https://fedia.io/m/[email protected]

but when I try to post there I get:

This page isn’t workingfedia.io is currently unable to handle this request.
HTTP ERROR 500

Which makes this post herein relevant to the fedia magazine after all.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 8 months ago (1 children)

Thanks. That seems to resolve the issue. Though, for a lot of smaller communities, no one is going to subscribe to them here, effectively making them invisible here.

[–] [email protected] 3 points 8 months ago* (last edited 8 months ago)

I don't completely disagree, hopefully the PR I linked, once complete, will make it a lot more obvious to people when this scenario occurs. I think from an instance owner perspective, they wouldn't want to constantly be paying the overhead on communities no one has an actual interest in viewing (edit: this isn't worded well, so forgive me, obviously people may want to view it but not have it show up in their sub feed, so perhaps another action item is a way to split subscription lists, which I think was already requested), as it has a very real financial cost to them. But I will keep this in mind, I meant to investigate how lemmy works (whether they also require a subscriber, I mean they do because this is how AP works but they might make a fake user or something, I never had a chance to look, but I'd be curious what tools they have to stop incoming messaging for when an instance owner wants to save bandwidth)