Mostly just used for moderation.
Main account is https://piefed.social/u/andrew_s

  • 1 Post
  • 33 Comments
Joined 3 years ago
cake
Cake day: July 24th, 2023

help-circle
  • Not really.

    Gup.pe groups were genuine ActivityPub Groups, like Lemmy communities, whereas these ‘FediGroup’ things are just Mastodon bots. They’re a ‘Service’, aka the automated version of a ‘Person’, so they’re no use to anyone on platforms (like Lemmy) that can only follow Groups.

    The most similar recent thing to gup.pe is https://ovo.st/

    Compare:

    curl --header 'accept: application/activity+json' https://lemmy.world/c/fediverse | jq -r .type   
    => Group   
    curl --header 'accept: application/activity+json' https://ovo.st/club/askfedi | jq -r .type  
    => Group
    
    with
    
    curl --header 'accept: application/activity+json' https://fedigroups.social/@audiofiction | jq -r .type  
    => Service
    



  • freamon@lemmy.worldtoMemes@lemmy.ml"content curation"
    link
    fedilink
    arrow-up
    4
    arrow-down
    3
    ·
    23 days ago

    I’ve contributed code to PieFed in the past, but nothing recently. If someone comes across something I’ve written and finds it amateurish, then that’s a reasonable assessment. There’s no need for you to delete your comment, as I’m not a fan of features over fixes approach either.

    The “People’s Front of Judea” remark relates to a Monty Python sketch from the The Life Of Brian (youtube link) - it’s a swipe at leftist infighting (swap out “The only people we hate more than the Romans is the Judean’s People’s Front” with “The only site we hate more than Reddit is PieFed” I suppose).


  • freamon@lemmy.worldtoMemes@lemmy.ml"content curation"
    link
    fedilink
    arrow-up
    9
    arrow-down
    15
    ·
    23 days ago

    The OP linked to the function with the ‘enoughmuskspam’ filter in it: it’s here (line 352 if it doesn’t auto-scroll down).

    As mentioned, it’s a bulk-community import function, that new admins can optionally use to kick-start a new instance.

    The code you’ve linked to is another convenience function, for users this time, that will optionally add the relevant values to their content filters for the ‘All’ feed. It’s also not a federation block, and it’s common enough for fediverse users to want to hide posts about those people that it’s value arguably overrides any perceived messiness about ‘hard-coding’ their names.

    Anyone who takes the time to understand PieFed’s codebase could find plenty of things to legitimately criticise. To my mind, though, it seems against the social contract around open-sourcing one’s hobbyist project, only for people to then be snarky about it online. If there’s bits of code that look like they were written on someone’s lunch break, that’s because they were.

    The frustrating thing about this post, and the (now deleted) post before it, is that someone has taken more time to create some shit meme than they have reading the code they’re haphazardly attacking. I’ve no idea why PieFed has suddenly come under some Lemmy users sights, especially since the whole point of federated social media is that it shouldn’t matter what client someone uses, and how much it reeks of “People Front of Judea” bullshit.


  • freamon@lemmy.worldtoMemes@lemmy.ml"content curation"
    link
    fedilink
    arrow-up
    33
    arrow-down
    15
    ·
    23 days ago

    This has come up before. Hopefully you’re just not understanding the code, rather than deliberately misrepresenting it to others. Even a casual scan should clue people in to the fact that the linked function isn’t concerned with federation blocks (the same list that ‘enoughmuskspam’ is in also contains ‘memes’ and ‘piracy’, which every PieFed instance has without any overrides required).

    I’ll copy-paste my comment from last time (I can’t link to it 'cos is was in reply to a deleted post). The first 2 paras are the most relevant bits:

    The code that OP has linked to is part of a convenience function for admins to add content to their new instances. It can query individual remote instances (e.g. lemmy.world), or it can query lemmyverse.net, and fetch communities that look to be popular and active.

    It’s completely unrelated to routine federation, and doesn’t prevent anyone subscribing to communities that may have those words in their names.

    The admin function could potentially be used to fetch hundreds of communities. It runs as a background process, so you don’t know what they were until after they’d been followed. The “bad words” list acts as a safeguard against bringing in things you might not want or expect. One reason is that you may want to curate the first impression you give new visitors, as there as some that will be put off by the “fuck this” and “shitpost that” reddit-isms. Another is that you don’t typically want communities that are disproportionately popular than others (e.g. if you bring in the default 25 communities, and one of is 196, then it completely dominate your front page).

    If there’s a particular community that you are interested in (e.g. because you moderate it), using this function isn’t an efficient way to add it. In addition to the “bad words” filters, it will also exclude communities that are NSFW, or below thresholds for popularity and activity. Rather than fetching a bunch of communities at the same time, and hoping that the one you want is included, it’s better to just add it manually (via a ! link or by using the “Add remote community” link) in much the same way as you would on any other platform.


  • It’s mostly annoying me because it’s affecting federation - not just the ability for new instances to backfill content, but for established instances to even be able to fully resolve a new post’s details before the author nukes themselves. For example, the previous post (titled “Paranoia”) isn’t available on lemmy.ml or lemmy.dbzer0 because they would have been a few seconds “too late” to fetch the details for the author.

    @lawrence@lemmy.world - if you’d like another mod to help out in the short term, I’m happy to volunteer. I realise people in the comments are being a bit defeatist about the ability to reckon with this problem, but whoever this person is should at least have to do a bit more work than they’re currently doing.


  • freamon@lemmy.worldtomemes@lemmy.world*Permanently Deleted*
    link
    fedilink
    arrow-up
    26
    ·
    edit-2
    2 months ago

    The code that OP has linked to is part of a convenience function for admins to add content to their new instances. It can query individual remote instances (e.g. lemmy.world), or it can query lemmyverse.net, and fetch communities that look to be popular and active.

    It’s completely unrelated to routine federation, and doesn’t prevent anyone subscribing to communities that may have those words in their names.

    The admin function could potentially be used to fetch hundreds of communities. It runs as a background process, so you don’t know what they were until after they’d been followed. The “bad words” list acts as a safeguard against bringing in things you might not want or expect. One reason is that you may want to curate the first impression you give new visitors, as there as some that will be put off by the “fuck this” and “shitpost that” reddit-isms. Another is that you don’t typically want communities that are disproportionately popular than others (e.g. if you bring in the default 25 communities, and one of is 196, then it completely dominate your front page).

    If there’s a particular community that you are interested in (e.g. because you moderate it), using this function isn’t an efficient way to add it. In addition to the “bad words” filters, it will also exclude communities that are NSFW, or below thresholds for popularity and activity. Rather than fetching a bunch of communities at the same time, and hoping that the one you want is included, it’s better to just add it manually (via a ! link or by using the “Add remote community” link) in much the same way as you would on any other platform.







  • “active users” are defined by lemmy: posts + comments + votes

    The bot is trying to catch upwards trend in the amount of active users. This tends to be communities that were dead or fairly dead, and then one or two posts got some engagement and spiked the number up.

    In terms of absolute active numbers, there’s no need for a bot because lemmy can tell you that. The bigger communities tend to swing up and down in terms of activity (cancelling themselves out).

    For example, tenforward@lemmy.world had 65 posts this week, but active users ended up pretty much where it was. The table below has 28 entries as the crawler at lemmyverse usually reports 4 times a day, so it’s for about 7 days:

    posts subscribers active users
    903 2466 3233
    902 2461 3259
    902 2461 3259
    895 2453 3194
    894 2447 3455
    894 2447 3455
    888 2443 3392
    888 2443 3392
    883 2440 3447
    883 2440 3447
    879 2437 3493
    879 2437 3493
    875 2434 3467
    872 2424 3631
    872 2424 3631
    868 2426 3588
    868 2426 3588
    863 2413 3457
    863 2413 3457
    856 2407 3446
    856 2407 3446
    854 2402 3247
    854 2402 3247
    847 2391 3188
    847 2391 3188
    844 2386 3081
    844 2386 3081
    838 2384 3235


  • I’ll automate this in the future. ‘now’ refers to when the crawler at lemmyverse got the info, so it trails a bit behind.

    Raw numbers for Subscriber Growth (7 days ago to now)

    101 firsthrust@lemmynsfw.com         
    094 redhead@lemmynsfw.com         
    082 amazingbum@lemmynsfw.com         
    070 neonhairporn@lemmynsfw.com         
    056 short_hair_babes@lemmynsfw.com         
    055 pale@lemmynsfw.com         
    054 eroticphoto@lemmynsfw.com         
    049 public_flashing@lemmynsfw.com         
    046 gooner_girls@lemmynsfw.com         
    045 outdoor@lemmynsfw.com         
    044 pronebutg@lemmynsfw.com         
    044 petgirls@lemmynsfw.com         
    043 nsfw@lemmynsfw.com         
    043 clit@lemmynsfw.com         
    042 booknymphs@lemmynsfw.com         
    040 ebony@lemmynsfw.com         
    037 groupsex@lemmynsfw.com         
    036 research@lemmynsfw.com         
    036 femabs@lemmynsfw.com         
    036 euroteenmodels@lemmynsfw.com         
    034 pialoof@lemmynsfw.com         
    032 hentaigif@lemmynsfw.com         
    022 eyecontact@lemmynsfw.com         
    018 hotwomenincars@lemmynsfw.com         
    008 lewderhentaicaptions@lemmynsfw.com         
    003 hentai_irl@ani.social     
    

  • I’ll automate this in the future. ‘now’ refers to when the crawler at lemmyverse got the info, so it trails a bit behind.

    Raw numbers for Active User Growth (7 days ago to now)

    407 tinytitties@lemmynsfw.com         
    336 asklemmynsfw@lemmynsfw.com         
    236 desirablewomen@lemmynsfw.com         
    227 xparadisio@lemmynsfw.com         
    196 anklepanties@lemmynsfw.com         
    191 ifyouhadtopickone@lemmynsfw.com         
    188 nsfw_gifs@lemmynsfw.com         
    171 juicyasians@lemmynsfw.com         
    159 glasses@lemmynsfw.com         
    153 yiff@lemmy.smeargle.fans       
    146 rearpussy@lemmynsfw.com         
    146 cameltoe@lemmynsfw.com         
    126 lipsthatgrip@lemmynsfw.com         
    115 ecchi@lemmynsfw.com         
    111 plastt@lemmynsfw.com         
    108 creampie@lemmynsfw.com         
    107 hentai@lemmynsfw.com         
    101 afrobull@lemmynsfw.com         
    098 bodypaint@lemmynsfw.com         
    095 beachfun@lemmynsfw.com         
    094 masturbationhentai@lemmynsfw.com         
    094 girlsmasturbating@lemmynsfw.com         
    084 coffeegonewild@lemmynsfw.com         
    081 fauxbait@lemmynsfw.com         
    079 pegging@lemmynsfw.com         
    077 frillysocks@lemmynsfw.com         
    068 bustypetite@lemmynsfw.com         
    067 deepthroat@lemmynsfw.com         
    063 sensualbdsm@lemmynsfw.com         
    059 hotandsexywives@lemmynsfw.com         
    059 ftvgirls@lemmynsfw.com         
    053 gonewild@lemmynsfw.com         
    052 mommy@lemmynsfw.com         
    050 fanslygirls@lemmynsfw.com         
    049 bigasses@lemmynsfw.com         
    048 misogyny_xxx@lemmynsfw.com         
    048 gentlefemdom@lemmynsfw.com         
    048 erotic_photography@lemmynsfw.com         
    047 pornstars@lemmynsfw.com         
    046 buttplug@lemmynsfw.com         
    045 lewdanimegirls@lemmynsfw.com         
    043 curvy@lemmynsfw.com         
    040 nudedudes@lemmynsfw.com         
    040 humiliation@lemmynsfw.com         
    038 shibari@lemmynsfw.com         
    037 cuminmouth@lemmynsfw.com         
    036 blindfold@lemmynsfw.com         
    035 asiancumsluts@lemmynsfw.com         
    034 futanari@lemmynsfw.com         
    031 massivecock@lemmynsfw.com         
    031 fitgirls@lemmynsfw.com         
    030 skinnytail@lemmynsfw.com         
    028 angelawhite@lemmynsfw.com         
    025 azurlaner34@lemmynsfw.com         
    023 bondage@lemmynsfw.com         
    021 blowjob@lemmynsfw.com         
    020 domestic_discipline@lemmynsfw.com         
    018 orgasm_denial@lemmynsfw.com         
    017 wooden_horse@lemmynsfw.com         
    017 facial@lemmynsfw.com         
    015 ass@lemmynsfw.com         
    011 tentaclehentai@lemmynsfw.com         
    008 spanking@lemmynsfw.com         
    


  • Suggestions are very welcome (it’s still a work in progress).

    The way it currently works is that raw percentage change is then mulitplied by the actual change and then divided by 100.
    So, for small community:
    10 => 22
    (22-10)/10 * 100 = 120% change
    22-10 = 12 actual change
    (120*12)/100 = 14.4% change

    For a big community:
    10000 => 10380
    (10380-10000)/10000 * 100 = 3.8% change
    10380-10000 = 380 actual change
    (3.8*380)/100 = 14.44% change

    This weights the changes by community sizes, so - for these examples - a big community growing by 380 is the same as a small community growing by 12, meaning that the final list is hopefully a mix of both.