Nothing4You

this doesn’t just affect lemmy.ml.

it seems that lemmy.ml -> lemm.ee was somehow fixed yesterday, but there are several other instances that also have issues sending to lemm.ee:

• hexbear.net: was broken since 2024-10-23, fixed since 2024-10-25
• lemmy.blahaj.zone: broken since 2024-10-24
• lemmy.ml: was broken since 2024-11-01, seems fixed since 2024-11-16
• startrek.website: broken since 2024-11-15

you’ll probably want to wait for 0.19.7, which will fix at least https://github.com/LemmyNet/lemmy/issues/5182.

https://github.com/LemmyNet/lemmy/issues/5196 is also something to keep an eye on.

peertube embeds are supposed to be fixed in lemmy 0.19.6, so when updating to that lemmy version they should start working again

does it work if you search again?

search for remote content sometimes doesn’t show up the first time you try, searching again just after that can help.

if the channel still doesn’t show up, does searching for an individual video work?

this is the important part.

when an account is deleted the associated private key used for signing activities is deleted as well. the activitypub protocol does not really define how software is supposed to deal with deleted and recreated actors (which includes users), so some software has been built with the assumption that any change of encryption keys for a user means it’s an invalid signature and will prevent activities involving that user to federate to that software.

If the sole moderator of a community was banned from an instance, does that make the community unavailable to the instance they were banned from?

yes, if the ban was with content removal and they’re the top mod.

If the community had multiple moderators and only one was banned, would that still be the issue?

the filter is whether the user being banned is the top mod.

this seems more of a federation issue than a defederation issue ;)

that is likely related to https://github.com/LemmyNet/lemmy/pull/5107, which limits the resolution of thumbnails.

the client you are using is probably only displaying the thumbnails to you, not the original images.

edit: this seems to include lemmy-ui as well

edit 2: raised a bug report for lemmy-ui

that is likely related to https://github.com/LemmyNet/lemmy/pull/5107, which limits the resolution of thumbnails.

the client you are using is probably only displaying the thumbnails to you, not the original images.

edit: this seems to include lemmy-ui as well

edit 2: raised a bug report for lemmy-ui

“Link in the post” is already in the post itself, and it’s a different one

it may be related to the older lemmy version.

the latest lemmy version has changed how metadata is fetched for posts coming from federation and it will no longer be processed while receiving the federated activity, instead it will be processed in the background. sometimes, metadata for urls cannot be fetched within the time limit and then the post will not federate properly if it’s not happening in the background.

I think most (especially mobile) clients simply don’t have this option and will always copy/share the “fedi link” - the url where the content is canonically hosted. all other URLs are simply cached representations of the original content.

https://lemmy.blahaj.zone/instances shows lemmygrad as blocked, maybe there are some older communities that were never removed on blahaj after defederation?

I’m not familiar with n8n but it’s fairly straightforward on the API side.

You’ll need a session token, also known as JWT, which you can get from logging in.

You typically don’t want to do a login for every post, so you’ll want to store that as a persistent value.
For authentication, you can pass the header authorization: Bearer {jwt}, with {jwt} being the session token.

https://join-lemmy.org/api/classes/LemmyHttp.html contains the API documentation.

You’ll need to figure out the id of the community that you want to post to.

If you need to look it up, you can use getCommunity to fetch its details. Afterwards you can use createPost to submit it.

The form links for the methods explain the request body json values that should be provided.

photos will never be pngs unless someone intentionally converts them to that format, as pngs are much worse than jpgs for storing this type of image. pngs are much better for computer generated images, such as screenshots, drawings, etc. you can also losslessly compress pngs with tools like pngcrush without converting them to jpg.

it’s like @[email protected] described. old content does not get federated unless there is new activity on it and someone on your instance is subscribed to the community it happens in.

this isn’t anyone’s fault, it’s just a matter of the instance not being around that long that some historic content will be missing.

das ist ein bug

so just dropping duplicates then?

are there no references to the duplicates from posts? if there are and the duplicate rows are just deleted it’ll cascade deletion and purge all those posts from the db as well

how are you planning to fix this?

delegating authentication to another service.

one of the more commonly known options would be sign in with google, but this is also quite useful for providers hosting multiple services. a provider could host a service that handles authentication and then you only have to login once and will automatically get logged in for their lemmy, xmpp, wiki and other services they might be providing.