@MrKaplan@lemmy.world avatar

MrKaplan

@MrKaplan@lemmy.world

This profile is from a federated server and may be incomplete. Browse more on the original instance.

MrKaplan, (edited )
@MrKaplan@lemmy.world avatar

Hi,

there seems to be an issue with the mastodon instance requiring https://docs.joinmastodon.org/admin/config/#authorized_fetch.

Lemmy 0.19.3 does currently not have a working implementation of authorized fetch, this should get fixed in 0.19.4 when that is released.

For now, the only workaround is to disable secure mode on mastodon.

edit: see also github.com/LemmyNet/lemmy/issues/4451

MrKaplan,
@MrKaplan@lemmy.world avatar

Keep in mind that this is the Lemmy.World support community, not Lemmy in general, so this post may not be seen by Lemmy devs.

If this was implemented, I doubt it would make it as a core Lemmy feature. This would like have to be built into either clients/interfaces (obviously each one would have to do this one their own), or it would probably have to be built on top of the planned upcoming plugin system.

MrKaplan,
@MrKaplan@lemmy.world avatar

other instances will need to have at least one subscriber to the community to be sent votes and new content

MrKaplan,
@MrKaplan@lemmy.world avatar

This is addressed in the upcoming Lemmy release 0.19.4 where contents will no longer be included in API responses. Until then it’s up to clients to actually hide it. Content is kept for a few days to allow you to undo deletion, but you can also edit your content before deleting it to remove that. There is also a scheduled task running once a week I believe that will replace contents of deleted comments with something like PERMANENTLY DELETED.

Regardless, as Lemmy is a public platform, you should be aware that people may be storing this information on linked platforms regardless and may not respect the edits/deletions at all.

MrKaplan,
@MrKaplan@lemmy.world avatar

Hi,

is this consistently happening with the same posts?
Do you see comments when you try the same post again later?
You mentioned this happens with both the default front end and also with Alexandrite, does it happen with the same posts on both of them?
Can you reproduce this in a private browser window?
If you can, would you mind sharing a post that this is happening with so we can take a look?
It would also be useful to see the associated error message.

MrKaplan,
@MrKaplan@lemmy.world avatar

ah, annoying that that seems to be happening accidentally so easily :/

MrKaplan,
@MrKaplan@lemmy.world avatar

you can’t report users yet.

there’s an email address for our ticket system in the sidebar of this community.
it’s either that or trying your luck by sending a private message to a random admin. tickets are often a better option.

MrKaplan,
@MrKaplan@lemmy.world avatar

the reporting endpoint is the same, doesn’t matter where you report from.

Website block randomly popping up from my virus protection while here on Lemmy

I’m not sure if there are certain images on here causing this popup to appear or what, and I wonder if someone can help me figure this out. I wonder if its something that will need to be blocked or an instance that needs to be de-federated until the admin of it agrees to remove the Malware that is causing it to happen. Here is...

MrKaplan,
@MrKaplan@lemmy.world avatar

lemmy.today maps to this IP.

It doesn’t look like any scanners currently flag this domain: virustotal.com/…/a47dfe5f17250f4fe029556c3f71672f…

MrKaplan,
@MrKaplan@lemmy.world avatar

Hi,

which community/posts is this about?

Comparing lemmy.world/c/kickasswomen?dataType=Post&sort=New to lemmy.world/c/kickasswomen?dataType=Post&sort=Hot I can still see both posts that were posted an hour ago, they’re just sorted further down currently, but still on the same page.

MrKaplan,
@MrKaplan@lemmy.world avatar

Hello,

the post was removed by a Lemmy.World admin.

Since the post is not in a Lemmy.World community and your user is not on Lemmy.World either, this removal is only affecting Lemmy.World users.

Our AutoMod is only notifying you about this happening, but the wording should be improved to make it more clear what happened.

MrKaplan,
@MrKaplan@lemmy.world avatar

if the missing NSFW mark is the only reason for removal we’re generally open to restore content after that has been fixed.

we will not actively search out content that has been removed and then was updated to include the nsfw mark, but this would be doable on request.

MrKaplan,
@MrKaplan@lemmy.world avatar

except it doesn’t work well for the rest of lemmy/the fediverse.

many other instances seem to be getting hit by this, but they don’t have as many activities generated locally for this to become much of a problem. additionally, this is mostly affecting instances with high latency to the instance that is being flooded by kbin, as lemmy currently has an issue where activity throughput between instances with high latency can’t keep up with too many activities being sent. the impact of this is can be a bit less on smaller instances with smaller communities often not having as many subscribers on remote instances, although we’ve seen problems reported by some other admins as well. this includes e.g. kbin.earth, which i suspect to have been hit by responses from a lemmy instance, while the lemmy instance was actually only answering the requests sent from that kbin instance.

during the last peak, when we decided to pull the plug for now, kbin.social was sending us more than 20 activities per second for 7 hours straight. lemmy.world can easily handle this amount of activities, but the problem arises when this impacts our federation towards other (lemmy) instances, as e.g. votes will get relayed by the community (magazine) instance, which means, depending on the type of activity being sent, we might have to be sending out the same 20 requests per second to up to 4,000+ other fediverse instances that are subscribed/following the community this is happening in. trying to send 20 requests per second, which lemmy does not do in parallel, requires us to use at most 50ms per activity total sending time to avoid creating lag. when the instance is in australia, with 200ms+ latency, this is simply not possible.

looking at the activity generation rates of some popular lemmy instances, anything that is significantly above lemmy.world is likely not just sending legitimate activities.

ps: if you’re wondering how i’m seeing this post, you can search for a post url and comment urls on lemmy to make lemmy fetch them, even if they haven’t been directly submitted through normal federation processes. this requires a logged in user on lemmy’s end.

MrKaplan,
@MrKaplan@lemmy.world avatar

so far this has been a single case with kbin.earth and lots and lots of cases with kbin.social.

no other instances have been observed behaving like this yet.

MrKaplan, (edited )
@MrKaplan@lemmy.world avatar

feel free to reach out to me directly via matrix at @mrkaplan:lemmy.world if you want

edit: fyi, mentions of @lwadmin will usually not be seen.

MrKaplan,
@MrKaplan@lemmy.world avatar

Hello, disposable email addresses are not allowed.

Quick video demonstrating that lemmy.world sends every activity out twice (i.imgur.com)

I realise this is a known issue and that lemmy.world isn’t the only instance that does this. Also, I’m aware that there are other things affecting federation. But I’m seeing some things not federate, and can’t help thinking that things would be going smoother if all the output from the biggest lemmy instance wasn’t 50%...

MrKaplan,
@MrKaplan@lemmy.world avatar

we’ve switched from using multiple federation sending containers (which are supposed to split receiving instances across workers) to just using a single one.

MrKaplan,
@MrKaplan@lemmy.world avatar

see lemmy.world/comment/8961882 for now.

we’ve been spending a bunch of time already during the last days to get a solution in place on our end that will allow us to selectively reject federated activities from kbin, such as allowing comments and posts while rejecting votes, which seem to be the main issue currently, but we’re seeing some stability issues with this currently.

we’re planning to unban the affected users from the communities once we have this stabilized, as we currently have to pick between

  1. defederate from kbin.social (and other kbin instances when they are affected)
  2. reject all inbound activities from affected instances
  3. temporarily ban affected users in the communities associated with the issue
  4. drop all activities with certain characteristics, such as votes, when coming from a specific instance
  5. drop all activities with certain characteristics, such as votes, when coming from a specific instance and exceeding a rate limit

1-3 are all options we can do with existing tools, 4 and 5 require a custom implementation on our side. as 3. has the least overall impact of those we decided to go with 3 for now, which seems to work out rather well so far, except for the individual user experience of affected users.

  1. has been our primary focus to implement currently, but it takes time to ensure this works as expected, as we’re essentially building this from scratch. 5. may be implemented afterwards if we want to spend additional time on it.
MrKaplan,
@MrKaplan@lemmy.world avatar

it is indeed mostly like related activities we’re seeing

MrKaplan,
@MrKaplan@lemmy.world avatar

for a magazine to show up on lemmy, a logged-in user needs to visit it first. afterwards, to ensure that new content is published to lemmy instances, someone from that instance needs to subscribe to the magazine. this needs to happen on every instance as far as i know. this is one of the reasons services like lemmy-federate.com or browse.feddit.de exist.

kbin.earth federation problems fixed (kbin.earth)

Recently, I've noticed federated threads/comments/votes were lagging behind, and it turns out kbin.earth was being spammed (hundreds in a minute, leading to a couple thousand queued messages after only half an hour) by a Lemmy server with the same exact activity pub message. After blocking the server (feddit.de), federation...

/kbin logotype
MrKaplan,
@MrKaplan@lemmy.world avatar

Hello @jwr1,

I just wanted to reach out to let you know that this may actually be a kbin issue, where your server has been spamming feddit.de and feddit.de has just been acknowledging/relaying your activities.

Since several weeks ago already we have been seeing various issues with massive amounts of activities being sent by kbin instances, primarily kbin.social. Today we (Lemmy.World) have also discovered a kbin.earth user being affected by this and have issued a community ban in one of our communities to remediate the issue and prevent thousands of activities sent from kbin.earth from being relayed through Lemmy.World.

We have so far been unable to establish any communication channel with @ernest, despite trying over multiple channels.

If you wish to perform some research about this, the user account we’ve seen this happen with from kbin.earth is @Oofnik, who we have banned from !world for the time being.

Feel free to reach out to me via matrix at @mrkaplan:lemmy.world directly if you’re looking for more details.

MrKaplan,
@MrKaplan@lemmy.world avatar

yes, really you.

i believe this is a bug in kbin somewhere causing (almost) endless loops for the same activities (data sent between instances to communicate your actions like votes) over and over again.

all the accounts i’ve looked at so far are (or at least look like) real users. we do not believe that this is a malicious action triggered intentionally by someone who has access to the account. you just happen to be one of the unlucky so far 37 users affected by this.

MrKaplan,
@MrKaplan@lemmy.world avatar

I don’t want to tell people not to interact with the platform, but it seems that it’s mostly votes triggering this issue currently.
Not voting kinda defeats the point of the platform in the first place.
I don’t think there’s really anything for you to do different, at least not until it’s known what exactly triggers this issue.

We’re currently evaluating a solution on our end to ignore all votes coming in from kbin.social, which we may consider extending to other kbin instances if necessary. That should mitigate most of this hopefully.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • anitta
  • thenastyranch
  • rosin
  • GTA5RPClips
  • osvaldo12
  • love
  • Youngstown
  • slotface
  • khanakhh
  • everett
  • kavyap
  • mdbf
  • DreamBathrooms
  • ngwrru68w68
  • megavids
  • magazineikmin
  • InstantRegret
  • normalnudes
  • tacticalgear
  • cubers
  • ethstaker
  • modclub
  • cisconetworking
  • Durango
  • provamag3
  • tester
  • Leos
  • JUstTest
  • All magazines