74
submitted 9 months ago by usernotfound@lemmy.ml to c/lemmy@lemmy.ml

cross-posted from: https://lemmit.online/post/1047028 - because ironically this will not reach instances where Lemmit is blocked.

A few months ago, I launched the Lemmit instance and bot (@bot@lemmit.online). Primarily, this was to help me stay up to date with some of the content I'd leave behind on Reddi. Additionally, I wanted to give back to the community, so I made it possible for anyone to request the archiving of subreddits to the Lemmit instance.

However, this came with some unintended consequences. Notably, the most subscribed community on the instance has been !AmItheAsshole@lemmit.online. Even though it should have been obvious that there is no way to communicate with the Original Poster, given they're on Reddit.

The pushback against the bot and the instance has increased over time. A recent post, This bot is bad for Lemmy, highlighted these concerns. I've also received similar feedback from admins of major Lemmy Instances and through direct PMs.

As a response, last week I stopped accepting requests for archiving new subreddits. This weekend, I went a step further by discontinuing the archiving of a large amount of "interactive subreddits"—communities primarily centered around Q&A or communication with the Original Poster. This includes subs like !AskReddit@lemmit.online and !dating_advice@lemmit.online, as well as niche and support communities. Such discussions are better hosted on Reddit or Lemmy's equivalent spaces.

I've also adjusted the post karma thresholds to curb spam posts. While this probably won't appease everyone, it should reduce the bot's posting frequency.

Perhaps this might prompt some admins to rethink their choice to defederate from the Lemmit instance, or the banning of the bot. I'm not expecting anyone to, and won't take it personally if you don't, but I wanted to give the community this update nonetheless.

In !about@lemmit.online there's a sticky post of all the Actively archived communities on the server (including NSFW ones, since that is not public without logging in), as well as the list of communities for which archiving is now disabled.

Cheers!

[-] usernotfound@lemmy.ml 5 points 10 months ago* (last edited 10 months ago)

Removed as a protest against the community's support for campaigns to bring about the deaths of members of marginalized groups, and opposition to private entities working to prevent such campaigns, together with it's mindless flaming and downvoting of anyone who disagrees.

As a postscript for this discussion only, be aware that virtually all the replies to my comments quote me out of context, or claim I've made arguments I haven't. It's safe to disregard them.

Quoted verbatim here, just in case you choose to edit it again.

The only reason you got downvoted to hell in this thread is because you want to paint everyone who opposes corporate censorship as transgender murder supporters, in, what the article itself describes as a futile, neverending effort.

And now that you are time and time confronted with the fallacies you employ, you decide to edit all your comments "in protest". Stopping only to call everyone who opposed you even in the slightest an accomplice to murder. Very mature.


Edit: Ah cute. They delivered another show of their good intent in my DM;

Fuck off and die you harassing, lying, piece of shit.

Everyone who disagrees with you must be pro-kiwi huh? I rest my case.

[-] usernotfound@lemmy.ml 5 points 11 months ago* (last edited 11 months ago)

~~I agree that "fuck this" might be a bit too strong for some people, I don't think there's anything wrong with "uninstalling", as long as the reasoning behind it is mentioned.~~

Edit: I see now that you're talking about hypotheticals, because nobody in this thread is doing that.

[-] usernotfound@lemmy.ml 16 points 11 months ago

If its uncivilised to uninstall an app because it's bugs are invading your privacy, then I don't want to be civilised. If anything, I'm doing the author a favour by telling them why I'm using their competitors.

[-] usernotfound@lemmy.ml 66 points 11 months ago* (last edited 11 months ago)

Why is it called "Revoke consent"? Consent was never asked during setup, so how can it be revoked?

Edit: oh great. It doesn't even save your settings for objecting to "Legitimate interest". Uninstalled.

It's ironic, because the companies who claim to have a legitimate interest in tracking my behaviour are the ones I want to block from tracking me most of all.

[-] usernotfound@lemmy.ml 28 points 1 year ago

How many password managers have you been trying out this week?

[-] usernotfound@lemmy.ml 11 points 1 year ago

Hole in their pocket?

[-] usernotfound@lemmy.ml 9 points 1 year ago

Might be an idea to make your lemmy home on an instance that doesn't allow down votes (those exist). People on other servers might still downvote it, but you won't notice.

In fact, I think I'll go do that myself.

[-] usernotfound@lemmy.ml 8 points 1 year ago

🤔 The server spits out html when it cannot reach the backend. So one could argue it's a configuration issue because the admin didn't provide enough capacity / didn't set up a proper generic json error for backend failures.

FWIW, Liftoff doesn't handle these super gracefully either.

At any rate I think it's kinda awesome that we get to witness these kinds of infancy problems.

6

cross-posted from: https://lemmy.ml/post/1637526

@tateisu@lemmy.juggler.jp PING!

I just had to delete over 44.000 Users, Bans and Activity messages from my database and defederate from lemmy.juggler.jp. Somehow, all their bans get propagated to the rest of the lemmyverse.

I did a quick check, and it seems like not all instances liked are affected, but some definitely are. aussie.zone, for starters (PING! @admin@aussie.zone )

The good news is that, due to the relational database, you only need to delete the users, and the database cascade does the rest. BEFORE YOU DO ANYTHING, MAKE A BACKUP OF YOUR DATABASE I am not responsible for messing up your database. Don't ever execute commands given by a stranger on the internet if you don't understand them. Also, unless you defederate from them, the logspam will just continue. So maybe do that first.


To fix it, get database access somehow, and check your instance table. There, search for the id for lemmy.juggler.jp with the following query:

SELECT id FROM instance WHERE domain = 'lemmy.juggler.jp';

Write down that id, and execute the following query:

DELETE FROM person WHERE instance_id=<the id you just wrote down>;

This will probably take a while (over 2 minutes on my database),

Example log message:

{
    "cc": ["https://lemmygrad.ml/", "https://lemmy.ml/", "https://midwest.social/", "https://lm.korako.me/", "https://tabinezumi.net/", "https://lemmy.shrieker.net/", "https://bar.southfox.me/", "https://sopuli.xyz/", "https://slrpnk.net/", "https://feddit.de/", "https://lemmy.perthchat.org/", "https://baraza.africa/", "https://mander.xyz/", "https://lemmy.eus/", "https://lemmy.ca/", "https://lemmy.fediverse.jp/", "https://fapsi.be/", "https://exploding-heads.com/", "https://baomi.tv/", "https://fediverse.ro/", "https://lemmy.pt/", "https://szmer.info/", "https://feddit.it/", "https://jeremmy.ml/", "https://group.lt/", "https://beehaw.org/", "https://lemmy.rimkus.it/", "https://lemmy.tedomum.net/", "https://lemmy.coupou.fr/", "https://lemmy.blahaj.zone/", "https://community.xmpp.net/", "https://lemmy.simple-gear.com/", "https://lem.simple-gear.com/", "https://lm.gsk.moe/", "https://latte.isnot.coffee/", "https://lemmy.sdf.org/", "https://lemm.ee/", "https://sh.itjust.works/", "https://lemmy.fmhy.ml/", "https://yiffit.net/", "https://lemmy.world/", "https://lemmyfly.org/", "https://vlemmy.net/", "https://lemmynsfw.com/", "https://programming.dev/", "https://terefere.eu/", "https://discuss.tchncs.de/", "https://infosec.pub/", "https://lem.elbullazul.com/", "https://feddit.jp/", "https://lemmit.online/", "https://aussie.zone/", "https://social.fossware.space/", "https://social.sour.is/", "https://lemmy.management/", "https://lemmy.one/"],
    "id": "https://lemmy.juggler.jp/activities/block/51bd6d83-3780-45c6-b29a-1b3a9a0bb401",
    "to": ["https://www.w3.org/ns/activitystreams#Public"],
    "type": "Block",
    "actor": "https://lemmy.juggler.jp/u/tateisu",
    "object": "https://lemmy.juggler.jp/u/samydes225879",
    "target": "https://lemmy.juggler.jp/",
    "summary": "spam accounts created?",
    "@context": ["https://www.w3.org/ns/activitystreams", "https://w3id.org/security/v1", {
        "pt": "https://joinpeertube.org/ns#",
        "sc": "http://schema.org/",
        "lemmy": "https://join-lemmy.org/ns#",
        "expires": "as:endTime",
        "litepub": "http://litepub.social/ns#",
        "language": "sc:inLanguage",
        "stickied": "lemmy:stickied",
        "sensitive": "as:sensitive",
        "identifier": "sc:identifier",
        "moderators": {
            "@id": "lemmy:moderators",
            "@type": "@id"
        },
        "removeData": "lemmy:removeData",
        "ChatMessage": "litepub:ChatMessage",
        "matrixUserId": "lemmy:matrixUserId",
        "distinguished": "lemmy:distinguished",
        "commentsEnabled": "pt:commentsEnabled",
        "postingRestrictedToMods": "lemmy:postingRestrictedToMods"
    }],
    "removeData": true
}
2
submitted 1 year ago* (last edited 1 year ago) by usernotfound@lemmy.ml to c/lemmy@lemmy.ml

@tateisu@lemmy.juggler.jp PING!

I just had to delete over 44.000 Users, Bans and Activity messages from my database and defederate from lemmy.juggler.jp. Somehow, all their bans get propagated to the rest of the lemmyverse.

I did a quick check, and it seems like not all instances liked are affected, but some definitely are. aussie.zone, for starters (PING! @admin@aussie.zone).

The good news is that, due to the relational database, you only need to delete the users, and the database cascade does the rest. BEFORE YOU DO ANYTHING, MAKE A BACKUP OF YOUR DATABASE I am not responsible for messing up your database. Don't ever execute commands given by a stranger on the internet if you don't understand them. Also, unless you defederate from them FIRST, the logspam will just continue. So maybe do that first.


To fix it, get database access somehow, and check your instance table. There, search for the id for lemmy.juggler.jp with the following query:

SELECT id FROM instance WHERE domain = 'lemmy.juggler.jp';

Write down that id, and execute the following query:

DELETE FROM person WHERE instance_id=<the id you just wrote down>;

This will probably take a while (over 2 minutes on my database),

Example log message:

{
    "cc": ["https://lemmygrad.ml/", "https://lemmy.ml/", "https://midwest.social/", "https://lm.korako.me/", "https://tabinezumi.net/", "https://lemmy.shrieker.net/", "https://bar.southfox.me/", "https://sopuli.xyz/", "https://slrpnk.net/", "https://feddit.de/", "https://lemmy.perthchat.org/", "https://baraza.africa/", "https://mander.xyz/", "https://lemmy.eus/", "https://lemmy.ca/", "https://lemmy.fediverse.jp/", "https://fapsi.be/", "https://exploding-heads.com/", "https://baomi.tv/", "https://fediverse.ro/", "https://lemmy.pt/", "https://szmer.info/", "https://feddit.it/", "https://jeremmy.ml/", "https://group.lt/", "https://beehaw.org/", "https://lemmy.rimkus.it/", "https://lemmy.tedomum.net/", "https://lemmy.coupou.fr/", "https://lemmy.blahaj.zone/", "https://community.xmpp.net/", "https://lemmy.simple-gear.com/", "https://lem.simple-gear.com/", "https://lm.gsk.moe/", "https://latte.isnot.coffee/", "https://lemmy.sdf.org/", "https://lemm.ee/", "https://sh.itjust.works/", "https://lemmy.fmhy.ml/", "https://yiffit.net/", "https://lemmy.world/", "https://lemmyfly.org/", "https://vlemmy.net/", "https://lemmynsfw.com/", "https://programming.dev/", "https://terefere.eu/", "https://discuss.tchncs.de/", "https://infosec.pub/", "https://lem.elbullazul.com/", "https://feddit.jp/", "https://lemmit.online/", "https://aussie.zone/", "https://social.fossware.space/", "https://social.sour.is/", "https://lemmy.management/", "https://lemmy.one/"],
    "id": "https://lemmy.juggler.jp/activities/block/51bd6d83-3780-45c6-b29a-1b3a9a0bb401",
    "to": ["https://www.w3.org/ns/activitystreams#Public"],
    "type": "Block",
    "actor": "https://lemmy.juggler.jp/u/tateisu",
    "object": "https://lemmy.juggler.jp/u/samydes225879",
    "target": "https://lemmy.juggler.jp/",
    "summary": "spam accounts created?",
    "@context": ["https://www.w3.org/ns/activitystreams", "https://w3id.org/security/v1", {
        "pt": "https://joinpeertube.org/ns#",
        "sc": "http://schema.org/",
        "lemmy": "https://join-lemmy.org/ns#",
        "expires": "as:endTime",
        "litepub": "http://litepub.social/ns#",
        "language": "sc:inLanguage",
        "stickied": "lemmy:stickied",
        "sensitive": "as:sensitive",
        "identifier": "sc:identifier",
        "moderators": {
            "@id": "lemmy:moderators",
            "@type": "@id"
        },
        "removeData": "lemmy:removeData",
        "ChatMessage": "litepub:ChatMessage",
        "matrixUserId": "lemmy:matrixUserId",
        "distinguished": "lemmy:distinguished",
        "commentsEnabled": "pt:commentsEnabled",
        "postingRestrictedToMods": "lemmy:postingRestrictedToMods"
    }],
    "removeData": true
}
[-] usernotfound@lemmy.ml 7 points 1 year ago* (last edited 1 year ago)

Yeah, my instance doesn't have a lot of users, but it does have a lot of posts (few thousand per day). It might be all the updates it's sending out.

I guess I'll just have to give 0.18 a try then.

27

Lemmy starts out pretty chill, but the longer it is running, the more CPU it's using. Until I restart it again, and then the process starts over again. It's just /app/lemmy that's eating the cpu cycles. Looks like there are some threads that keep requeueing themselves, until eventually that's all it's doing.

Does anybody have any clues or pointers about this?

I'm running 0.17.4, haven't made the jump yet to 0.18.

[-] usernotfound@lemmy.ml 5 points 1 year ago

I wouldn't be surprised if they had, actually.

Still, a spam bot can just use the free license - they won't make nearly as much api requests as a proper app would.

The ones that make 60 posts per account per hour are easy to detect no matter how they post.

1
submitted 1 year ago by usernotfound@lemmy.ml to c/aww@lemmy.ml
[-] usernotfound@lemmy.ml 7 points 1 year ago* (last edited 1 year ago)

I fully understand and respect that, and would never run it on an instance that wasn't specifically set up for this purpose.

The intention is for it to be something people can OPT IN to, not OPT OUT of.

22
submitted 1 year ago* (last edited 1 year ago) by usernotfound@lemmy.ml to c/programming@lemmy.ml

Idea: Scrape all the posts from a subreddit as they're being made, and "archive" them on a lemmy instance, making it very clear it's being rehosted, and linking back to the original. It would probably have to be a "closed" lemmy instance specifically for this purpose. The tool would run for multiple subreddits, allowing Lemmy users to still be updated about and discuss any potential content that gets left behind.

Thoughts? It's probably iffy copyright-wise, but I think I can square my conscience with it.

view more: next ›

usernotfound

joined 1 year ago