andrew_s

Hi, no sorry, I'm not active on Reddit. I don't have backend access here either, so wouldn't be able help out if something went wrong.

You should listen to the voice that's telling you not to add more spoons to this already heavily-stirred bowl of shit.

'us' seems a mite too conventional for a plural pronoun if you're intent on re-inventing singular ones.

Anyway, you could at least commit to the bit, and actually mark your account as a bot, instead of just saying you are one. There's likely some instances where bots that aren't marked as bots are against their terms of service.

More so 'other Fediverse socials'.

Here's an example on PieFed, that's a PixelFed user tagging their photos with 'dailyphoto' and then sharing via a.gup.pe on Mastodon: https://piefed.social/tag/dailyphoto

Lemmy has mangled that script a bit.

Where it says '%24%7Bpage%7D', it should a dollar sign, an open curly bracket, the word 'page', then a close curly bracket.

It displays a bit better at the source (click the multi-coloured fedi-link thing).

The only way I can think of is to use the API to get all communities, and then filter out the ones without local subs. So a basic BASH script would be:

#!/bin/bash  

echo -n '' > /tmp/allcomms.txt  

page=1  
while true  
do  
  communities=$(curl --request GET --url "https://walledgarden.xyz/api/v3/community/list?type_=All&page=%24%7Bpage%7D&limit=50" --header 'accept: application/json' | jq .communities[])  
  if [ "${communities}" == "" ]  
  then  
    break  
  fi  
  jq -r '[.community.id, .counts.subscribers_local] | @sh' <<<$communities >> /tmp/allcomms.txt  
  page=$(( page + 1 ))  
  sleep .5  
done  

while read id count  
do  
  if [ $count -eq 0 ]  
  then  
    echo "$id has no local subs"  
  fi  
done < /tmp/allcomms.txt  

(It'll take a few minutes to run)

After that, how you purge the communities with those IDs I'm less sure of. My guess would be:

Get a login tokin:
JWT=$(curl --request POST --url https://walledgarden.xyz/api/v3/user/login --header 'accept: application/json' --header 'content-type: application/json' --data '{"username_or_email": "YOUR_USERNAME","password": "YOUR_PASSWORD"}' | jq -r .jwt)

Use Admin/Purge from the API:

curl --request POST --url https://walledgarden.xyz/api/v3/admin/purge/community --header "authorization: Bearer $JWT" --header 'content-type: application/json' --data "{"community_id": ${id}, "reason": "no local subs"}"  

As long as purge lets the community be recreated again (which it should do), then that should be okay.

Don't take my word for any of this for an in-production Lemmy server, though. Test first!

Whatever the views are about MBFC, Tesseract integrated it better than LW's bot. If you don't like MBFC, it's just an option in your user settings to turn it off for Tesseract, whereas the bot caused a bunch of problems that weren't even related to concerns about accuracy and bias. Drive-by bots can be annoying, because it leads people to believe there's legit content where there isn't, and not every client respected LW's bot use of spoiler Markdown, so they ended up with a massive comment from it that dominated the screen.

That's what they're doing though, isn't it? They have an account on Friendica, and they've used it to make a post within a Lemmy community (the community being [email protected] in this case).

I saw a post recently that was from Friendica to Lemmy: https://libranet.de/display/0b6b25a8-2267-afe6-6e6e-34b123429965 was to https://beehaw.org/post/18472167

Maybe you can copy whatever they did (or ask them).

For Season 1. (Season 2 has different credits.)

Some non-Lemmy Groups that are interesting or might get interesting:

PieFed: [email protected]
MBIN: [email protected]
PeerTube: [email protected]
WordPress: [email protected]
NodeBB: [email protected]
a.gup.pe: [email protected]

How well they backfill and inter-op is very platform-dependent, obvs (your platform and the remote platform)

It's okay. I got brave and looked at my bank account, and things aren't as bad as I was imagining. I'll buy one tomorrow.