I watched Jurassic World: Rebirth the other day (it's alright). It's such an odd franchise - one that seems to have lost faith in its own premise. There's this meta assumption that audiences are bored with dinosaurs (I'm not), and that the solution to this imagined problem is to mutate them (it really isn't, it's invariably just silly).
I also don't care that dinos couldn't really survive in the modern climate - that's what the whole 'suspension of disbelief' thing is for.
Nope. I don't agree with cm0002's campaign of reposting everything posted to a lemmy.ml community to a community hosted elsewhere, so I don't want to run a bot that suggests there's genuine growth somewhere when I consider any growth there to be driven by bullshit. The bot was never sophisticated enough to distinguish between the two.
It ended up being more of a proof-of-concept than anything. I forked Thunder by banging my fists on the keyboard until it worked, rather than actually learn anything about Flutter/Dart or proper app development. As soon as another Flutter app came along (Interstellar), I leapt at the chance to abandon it.
afaik Andrew approves new registrations but mostly does coding?
You originally added me so I could debug stuff based on the status incoming activities, which isn't really relevant anymore.
That isn't my primary account atm, so I don't really do any other admin stuff. That said, it might be an idea to keep some permissions in place for that account, so I can help out in case there's a spam wave when it's night time in NZ or something.
Re: the Mentioning in multiple communities, PieFed does the same. Preventing spam is a nice side-effect, but the main reason is to handle the same activities being sent multiple times. The most reliable way to know if you've already received the activity for a post is to have a unique constraint on the DB field for the post's original URL (so once you've created the post for one community, you can't then create the same post for another community).
I was experimenting with adding other people's mastodon posts to a local PieFed community earlier. It's technically fine, not much different than another Mastodon user boosting the post. The slight difficulty is in getting Lemmy instances to accept them - you have to break their Group spec a bit to get it work. It might be worth doing anyways.
That codeberg issue is now fixed btw - I added a screenshot there to show what it'll look like when the code is deployed to piefed.social.
Re: 3. No. For sending, they need to be in that tags form field, and for receiving, they need to have been in the ActivityPub "tags": {"type": "hashtag"} section for a post. For both directions, PieFed isn't regexing any text anywhere to look for something that might be a tag.
cc: @wjs018@piefed.social
For this particular issue, perhaps not.
But the fact that both me and you are using PieFed instances and are participating in a comment chain started by a hexbear user demonstrates that there isn't much 'hard-coding' against other sites.
The commit that @davel@lemmy.ml referenced is for initial database setup. It's not an unreasonable default list to populate the 'banned_instances' table, and is trivial for admins to change after setup is complete.