aka freamon

Codeberg: https://codeberg.org/freamon?tab=activity

Anything from https://lemmon.website/ is me too.

  • 13 Posts
  • 531 Comments
Joined 1 year ago
Cake day: March 27th, 2024
  • Andrew@piefed.socialtoLemmy Support@lemmy.ml•Purging communities with no local subscribersEnglish
    2·
    4 months ago

    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!

  • Andrew@piefed.socialtoFediverse@lemmy.world•The Tesseract Lemmy app shows a news source ranking from MBFCEnglish
    283·
    4 months ago

    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.

  • Andrew@piefed.socialtoFediverse@lemmy.world•Fights about Lemmy.world policy changes explainedEnglish
    41·
    4 months ago

    The first link in the cross-post chain is to https://piefed.social/post/413111, which is for the channel, and shows that it was made 4 weeks ago, and includes a comment from the main LW admin.

    Your suspicions about this video seem off, but if you want to keep them, they should be directed at person who posted this old video into Lemmy, not the video’s author. As well as a PeerTube instance, Jeena has a PieFed instance, and it seems reasonable enough for him to use his own channel to discuss things that have affected him and are relevant at the time.

    What’s even weirder is that this video was already posted to !videos@lemmy.world by Jeena a month ago, and OP commented on it then. It doesn’t get picked up as a cross-post (by either Lemmy or PieFed) because PeerTube has 2 different formats for its URLs (a recent change to PieFed means they get they will do from now on, but it doesn’t apply to old posts).