

Nope - there’s no setting to change this behaviour.
I am also ‘Andrew’, the admin of this server. I’ll try to remember to only use this account for posting stuff.
Nope - there’s no setting to change this behaviour.
If you imagine what it would look like without the merging, the one shown would be the one nearest the top of the screen - so if you’re sorting by ‘New’, then it’ll be the newest, by ‘Top’ and it’ll be the most upvoted, by ‘Active’ then the most active. Because of how much LW dominates, it’ll pretty much always be that one.
There’s a good chance that the person has automated the activity (it certainly doesn’t appear to be done with any thought), but they’re technically not a bot.
It’s a relatively new feature, but PieFed merges up crossposts that it sees into one post - whether the post you see within a topic is yours or not will depend on the sort type - there’s a ‘layers’ icon beneath relevant posts, and clicking that can get you to the other posts if the visible one isn’t the one you want.
That modlog entry is actually for the LW community - it’s a bit clearer here: https://lemmy.world/modlog/31408?page=1&actionType=All&userId=13663964
The posts being made to the LW community aren’t being made by someone who cares about this comic. They’re not genuinely providing anything, they just have a stupid tedious beef with lemmy.ml, and so mindlessly crosspost everything they see posted to an ML community to a non-ML community. This means that if you don’t post first, the comic is unlikely to appear at all.
What is the update delay for Fediseer?
I don’t know. It’s not something I’m familiar with - it might just default to saying ‘closed’ if it doesn’t have the data.
It’s interesting that the obvious bot accounts on those instances were set up in mid-March last year, so I’m guessing that these are somebody’s army that they’ve used before, but overplayed their hand when they turned it on the DonaldJMusk person. The admins can reasonably be blamed for setting up instances with open registrations and no protections and then forgetting about them, but I’d be wary of blaming them for being behind the attack directly. The ‘nicole’ person is unlikely to have used their own instance - it’s probably just someone with the same MO as whoever owns the bots, finding and exploiting vulnerable instances.
lemmy.world recently updated from version 0.19.3 to 0.19.10. This change - for Lemmy communities to federate out posts with the community name as a hashtag - was introduced in 0.19.4, so that might be the other reason why this has only just become an issue for you.
The attacker seems to be the admin of those two instances. Both instances have their registrations closed.
The alternative theory would be that these instances had open registrations, but rightly closed registration down after the admins noticed the bots. chinese.lol is on 0.18.4 with an admin with a 2 year old account, lemmy.doesnotexist.club has an admin with a 1 year account, and it was also that instance that the ‘nicole’ person has used before. This downvote attack would need to be a long time in the planning for what you’re suggesting to be true.
It’s probably best to keep the first +1 for your own post or comment, as that’s what’s expected from people’s experience on other platforms, and that’s how it will appear on platforms that the content has federated to. Whether a user’s reputation score should give them an additional and visible +1 is debateable, but PieFed might be stuck with that decision now.
I don’t think that blog author is male, btw.
Lemmy logs its outgoing federation activity (rotating every 7 days I think), but not their incoming activity. That was a PieFed feature to aid debugging and development (I say ‘was’ because it’s not enabled by default anymore - you have to add LOG_ACTIVITYPUB_TO_DB = True
to .env to get it back).
Nothing currently exists to help migrate DBs. Not yet anyway (other Lemmy admins have also expressed an interest in changing over).
I noticed that a new community - !fedistream@lemmy.world by @Cattail@lemmy.world - has been launched, so maybe there’s been an increase that at least one other person has noticed.
I think that’s what he meant, yeah (no existing DB migration scripts, etc). I don’t know much about it, but I imagine it was probably always going to involve someone more familiar with Lemmy diving into the trenches.
He’s mentioned this before, but I’ve never been able to find an actual PixelFed Group (it doesn’t appear to be the same thing as what they call Collections). I’ll have another look when pixelfed.social enables them this weekend (but I suspect parsing titles for the posts will be a nightmare).
Also, ‘smithereen’ is tagged but I’m not sure of its status (all I found was 1 private instance run by the dev, federated with 1 “explicitly-free-speech” Akkoma instance).
Rimu has now added the option to ban users via the drop-down menu next to their comment.
It’s maybe not a good idea to make it too easy to ban people who haven’t created any content, as it’s the kind of thing that often causes a lot of boring fedi-drama. Though I realise that there still might be other reasons why mods might want to search through the subscriber list.
If they’ve made a post, there’s an option to ban them in the 3-dots drop-down menu. If not, you should be able to find them in the ‘subscribers’ tab of the community settings (‘ban’ is in the Actions drop-down). If they’ve not made a post and they’re not a subscriber, then I’m not sure.
You don’t need to apologise. I wasn’t trying to give you a hard time (sorry if it seemed like that). The remote posts I linked to in my earlier comment have now gone (maybe I was being given a cached version before - that’s a possibility I often forget about).
The other posts from that user follow the same format (with the image, and then the credits below it) and they all seem to have appeared in the community okay. There’s nothing wrong with the original post on kbin.earth, so it looks like a very specific hiccup happened with the processing of that particular post. It’s the kind of bug that I think would be impossible to track down, unfortunately.
I forced an update for that post, and it’s rendering okay now at least.