Yeah, I think it’s something only admins can see on their users’ profile, not something people can see on their own profile.

You’ll know if it’s low though, 'cos red triangles will appear by your username in comments (I made an unpopular comment recently, and - for some instances - that’s the only comment they’ve got by me, so I’ve got the triangles there).

Yeah - attitude is ratio of upvotes to downvotes you give out, reputation is ratio of upvotes to downvotes you receive.

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.

I asked in that issue whether Lemmy finds community via to/cc (it does). Does PieFed do the same?

Yes - PieFed does the same. It looks in ‘audience’, then ‘cc’, then ‘to’. It has to, to support all the platforms that haven’t adopted 'audience. It’s a convenient field, but PieFed won’t be affected if Lemmy goes through with removing it.

Would this also open up the possibility of a topic/context being part of multiple audiences/communities?

Not at present. If you do something like cc: [community1, community2] it will only go to community1 (on both Lemmy and PieFed). There’s so many activities that are effectively duplicates, both in normal operation and when platforms are bugged (both Lemmy and Mastodon have gone through phases of sending the same activity multiple times), that you need a way to make sure you’re only processing one. On PieFed, this is done by having a UNIQUE constraint of the ‘ap_id’ column of the Post table (the ap_id of your post is https://community.nodebb.org/post/103806), so it means you can’t have the same post in more than one community.

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 !chat@beehaw.org 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: !antisocialmedia@piefed.social
MBIN: !FloatingIsFun@fedia.io
PeerTube: !veronicaexplains@tinkerbetter.tube
WordPress: !dbzer0.com@dbzer0.com
NodeBB: !fediverse@forum.wedistribute.org
a.gup.pe: !photography@a.gup.pe

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.

If you’re trying to do this at feddit.org, it’s because the ‘Nimi’ field is too long. It looks to be about 22 characters, but the max length for an actor at feddit.org is 20.

For each instance, the restriction can be viewed from the command line with: curl https://feddit.org/api/v3/site | jq .site_view.local_site.actor_name_max_length

As things are atm, Lemmy users will likely also need to also fetch this video by pasting the URL into search (there’s no backfilling, and channels still don’t seem to automatically update - e.g. see https://lemmy.ml/c/thelinuxexperiment_channel@tilvids.com?dataType=Post&sort=New).

If Lemmy / PeerTube inter-op was better, there’d be less need for Lemmy users to be doing what they’re currently doing with posting them separately. (It’s good that more people will see this video, but it effectively leeches votes and comments away from the original creator).

Sorry. That’s my bot. There’s comments in the latest post it made about why it died (the SD card on which it was running went read-only). If it’s not pissing it down, and the thought of it all doesn’t seem overwhelming, I’ll mooch into town and see if any cheapie shops are selling 'em.

Fasting (for Ramadan)

Not sure about “slow poisoning”

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).