Where there such complaints in kbin? In kbin if they downvoted you usually they would explain their reasoning promoting discussion. Anonymous downvoting creates in my opinion less positive environment for civil growth and discussion.
You mentioned that fedia has a very small number of active users. Is there a place I can learn more about this? What is large amount, and what do you consider to be active?
Fedia.io has 422 monthly active users - basically, 422 accounts have logged in within the past 30 days. I suppose I am comparing it to infosec.exchange, which has about 15000 monthly active users. I do believe that fedia.io is the most active mbin or kbin instance, by a factor of 2 or 3, but relatively quiet in comparison to Mastodon and Lemmy.
Hetzner makes their own servers in a form factor that works for their rack space. There are lots of YouTube videos on that. I don’t know specifically why these are failing, but being an old time engineer and knowing the CPU they are running, I am going to bet it has something to do with cooling. Either the main board is getting too hot (I monitor CPU temp and that seemed fine) or it is related to either vibration from the certainly larger CPU fan it needs, or somehow related to how the CPU impacts the power supply - possibly creating noise that ultimately burns out capacitors or something similar.
Apologies for having registrations closed. The moderation tools in Mbin/kbin are very very basic and I keep experiencing large numbers of spam signups, with no meaningful way to handle them until they sign up and start spamming
Hey! Thanks for the response and no worries I figured out spam was likely the reason behind he temporarily closure of new sign up's.
Btw let me know if you are in need of more admins, id gladly contribute to help the server as I have a long experience as mod already on reddit and the fediverse.
The cause is unclear to me, but the processes that manage incoming and outgoing federation were "stuck" until I manually intervened. It's running now. I'm adding to my to-do list for after my job ends in 10 days to implement some sort of detection and hopefully automated restart for when this happens again.
You generally seem to need to have at least 1 account from that instance subscribed to your magazine for federation to kick in (which then still can take a bit of time). Same works the other way around. The unfortunate thing is that you kinda have to use external community / magazine indexers to search for them, unless you know the exact name & instance domain they're in, since a search won't find non indexed ones by itself.
Imo one of the largest issues regarding the fediverse.
Yeah, I hope it gets "fixed" at some point ("fixed" because I guess it is by design). For now, I created an account to most large Lemmy servers and subscribed to the magazine so future users find a fuller community :P
I was wondering if the language settings in a user's profile meant that they cannot see your posts. I enabled Greek but it doesn't seem to have made any difference.
So, I created a lemmy.world account just to subscribe and check if the federation now works. It works, but only for new posts, which is not ideal either. Hopefully federation can be fixed for older posts as well (I know that comments need someone from your instance to have subscribed to that community, but posts should always be visible to others)
Which lemmy instance were you not seeing it on? One of the challenges with all fediverse applications (mbin, lemmy, mastodon, etc) is that posts and comments don’t federate with other instances unless someone on the other instance follows the person or the magazine.
I do not believe existing posts and comments will federate to a different instance after someone on that instance subscribes to the magazine. Only new posts and comments will.
I see. Too bad, but hopefully this is something that may get fixed in a future ActivityPub protocol update (don't know if it is sth the applications can fix themselves)
fedia
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.