this is early testing phase. I have created and deployed a lemmy server and mattermost modules successfully and it works great.
technical details: all this works via cloud instances kinda like architecture, i create a instance (container or vm based on software req) and launch automated scripts to setup everything so people don’t have to mess up working with insecure configurations. The backend api is golang and frontend is vuejs. I also have a WAF and security protocols to mitigate basic security flaws and botnet attacks. I need feedback on what our oss community surfers the most when hosting federated communities.
business side: I dont intend to charge for things in testing phase cause all i need is good feedback but as the server demands grows i’ll be working with whatever you’ll be paying for private instance (idk like $2 a month ?).
motivation: people use proprietary products cause they are already hosted and just avaiable. If we make this with oss products people will start using it. Making lemmy easy to setup will boost more community interaction and make lifes of current community mods easier :)
There’s no shadow bans. It’s possible that you’re interacting with an instance that has defederated from your home instance or vice versa. You won’t be told this. Everything just appears empty. Same if you’re banned from a community/instance. You won’t be told this unless the moderators message you.
Since I can see their content just fine it doesn’t appear to be defederation. But if they did ban me and there is no way for me to know, isn’t that a shadow ban?
What’s the instance and community you’re having problems with and I’ll tell you what’s going on. You would know you were banned by viewing your profile on that instance. You can find reasons in the modlog too if they added any.
The one I noticed it the most with is hexbear. I know they have a bad rep but I like to keep an open mind and tried a bunch of times to chime in whenever I saw one of their posts pop up on the all feed i felt I had something relevant to add to.
I also know they are a bit echo chamber-y so I assumed they might have a special hidden restriction in place for non-approved instances. I would be surprised if they actually banned my personal account because I don’t think I wrote anything they might consider controversial.
But the fact remains that (as far as I understand) my feed would not show any of their content if my instance was not federated with them, no?
This could be a long shot, but since your instance is running on a .zip TLD it could be blocked at a webserver level (the whole .zip TLD not your instance specifically) like a lot of admins did when they were launched.
Interesting, how can I see this for myself? I suppose using a client for Lemmy since day 1 made me not learn these basic things and I want to check some other instances where I suspect the same.
No idea what I did to offend but I guess I can safely block their instance from my feed then. It’s a bit annoying the user isn’t warned or straight up prevented from participating when banned.
Good mods/admins send a message along with their banning/removals. If you add /u/GregorGizeh@lemmy.zip to the end of any Lemmy domain you can see your profile on that instance. Scroll down, tap modlog and search for your name if you want a timeframe/reason.
This post, a day before yours on the lemmy_support@lemmy.ml community, is describing some similar behavior, with some CPU usage at start (at least on the first boot; not clear whether that is a one-off on migration from the text) and then federation problems with 0.19.1:
After upgrading Lemmy from 0.18.5 to 0.19.1, the lemmy_server process is taking up 200-350+% of my CPU…It seems like my instance isn’t federating properly now tho.
I got som weird behaviour, like nothing worked very well, with 0.19.0 so I updated to 0.19.1 and after quite a while (small instance, beefy PC) it starts to work again, it seems.
Except I am now a moderator everywhere. Maybe it doesn’t work, I won’t try, except asked, so can someone make a post that I can sticky or delete just to see what’s happening?
I just set my Display name to “Davel”. We’ll see if this propagates. Then I’ll delete my Display name, and see if “Dave” is retained by other instances. Then I’ll know that this is unrelated to the Markup table.
You don’t have a display name now, but maybe you did at some point?
Maybe it’s just the removal of the display name that didn’t federate properly?
Just a hunch
It seems to appear on sh.itjust.works as well, at least when accessed via a browser. Are you on a browser? If not, then this would suggest the functionality is in the lemmy-ui codebase.
I had a display name but it was a bit too long so I’ve deleted it locally.
Remote instances still display it.
Mine has nothing to do with the bio or pronouns, it’s just a federation bug.
I was having issues with outgoing federation to Mastodon on 0.19.0. I just did the update five minutes ago, so we’ll see if that fixes it. If you’re seeing this comment I guess it’s working at the moment.
What we are seeing is that outgoing federation of posts and comments works after a restart, but new posts and comments made on the local instance are not federating to other instances until the next restart. This is with version 0.19.1.
Also after a restart, the server eats a lot of cpu for several minutes. Im guessing this is normal with the federation queue being processed but cant be sure.
Either 19.1 or rc.1 fixes the bug from what I saw.
But the question then becomes when the last post was made to apocalyptic art. From my quick glance it was 4 days ago on the lemmy.ml mirror, which seems behind the most recent posts on the actual community. Lemmy.ml is on the newest version.
So my guess is that there’s some general federation issue, possibly on the feddit.de end, which is causing some things to get dropped.
If that’s not the issue, then there could be a similar bug that hasn’t yet been noticed.
We were just discussing some potentially-0.19.1-related federation problem that lemmy.today users were experiencing after the update; that’s how I ran across this thread.
The admin there, @mrmanager, restarted the instance again some hours later to attempt to resolve the problem, and it looked like federation started working at that point.
That might be worth consideration if any other instances are seeing problems with posts/comments/votes not propagating.
EDIT: Well, nuts. Now this comment doesn’t seem to be propagating either; visible from lemmy.today but not on lemmy.ml’s Web UI. Maybe if lemmy.today gets restarted again, it will.
Posting from a kbin.social account to avoid the lemmy.today issues -- on lemmy.today, the current behavior looks like the messages in the queue go out when the instance is restarted, but not until then. It's running 0.19.1.
I am not the admin there, but wanted to make that available in case other instances are affected and trying to diagnose similar behavior; federation problems themselves can cause communication problems in trying to understand the issue.
For anyone else wondering, btw, it’s because lemmy expects all ‘id’ fields to be unique, so it would error if the inner object actually was a copy of the original vote.
lemmy_support
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.