Nothing4You
@Nothing4You@programming.dev
- Comment on Defederation issues between Lemm.ee and Lemmy.ml 4 days ago:
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
- Comment on Is it possible to get back a username of the account I deleted? 1 week ago:
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.
- Comment on Defederation issues between Lemm.ee and Lemmy.ml 2 weeks ago:
this seems more of a federation issue than a defederation issue ;)
- Comment on Feedback about our name: someone's concerns on sharing 3 weeks ago:
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.
- Comment on What's the deal with lemmy.world today? 2 months ago:
lemmy updates did some improvements on the receiving side, parallel sending on the sending side is not yet part of a new release. it’ll also likely take some time for that to be deployed on lemmy.world to have those changes be tested by other production instances first. my activitypub-federation-queue-batcher is currently used by at least 2 other high latency instances and would address the issue at the cost of a small (like 3 bucks or so) vps in Europe and some time investment for the setup.
- Comment on Please unban @i_am_not_a_robot@feddit.uk 3 months ago:
it contains turtle and crazy
- Comment on Please unban @i_am_not_a_robot@feddit.uk 3 months ago:
The ban appears to be caused by your post linking to a known blogspam site that has frequently been spammed to Lemmy in the past.
- Comment on Low Levels of Aussie Zone association with Lemmy in Search. 3 months ago:
Posts have a canonical reference to the originating instance, e.g. this post contains
<link data-inferno-helmet=“true” rel=“canonical” href=“https://aussie.zone/post/11962005”>for me. This is a hint for search engines to ignore this post and instead index the original one instead. The same also already works for communities, this community containing<link data-inferno-helmet=“true” rel=“canonical” href=“https://aussie.zone/c/meta”>. Not sure if DDG is just ignoring this or there’s another reason for it to show up multiple times. - Comment on I think thread deletion is problematic and needs some consideration and changes 3 months ago:
Except it wasn’t created on lemmy.ml, it was created on lemmy.world.
lemmy.world then informed lemmy.ml that it is intended to be published in the community that it was created for.
It doesn’t say “crossposted from lemmy.world” but “crossposted from canonical_post_url”. This is not wrong in any way, although it might be a bit confusing and could likely be improved by including a reference to the community. The instance domain should for the most part just be a technical detail there.
It should also be noted that this format of crossposting is an implementation detail of Lemmy-UI and other clients may handle it differently (if they’re implementing crossposting in the first place).
- Comment on I think thread deletion is problematic and needs some consideration and changes 3 months ago:
I’m not saying it’s technically impossible, although it would likely be a bit challenging to integrate on the technical level, as the community instance has no authority to modify the post itself other than removing it from the community at this point.
The existing fedilink is already present for technical reasons anyway, so this is currently only showing existing data.
Why would you want a lemmy.ml link though? On Lemmy you’re typically intending to stay on your own instance, which many third party apps already implement. For Lemmy UI there is already a feature request to implement this, although it might still take some time to get done. If you have the canonical link to an object (which will always point to the users instance) Lemmy can look up which post/comment you’re referring to in its db without any network calls when it already knows about the entry. If you were linking to the lemmy.ml version of that post then the instance would first have to do a network request to resolve that and then it would realize it’s actually the lemmy.world version that it may or may not know about already.
- Comment on I think thread deletion is problematic and needs some consideration and changes 3 months ago:
it doesn’t matter whether you consider it reasonable, as it’s this way for technical reasons.
when a post or comment are created they are created on the users instance. the users instance then tells the community instance about the new post/comment and the community instance relays (announces) this to other instances that have community subscribers.
the fedilink is an id and reference to the original item. this unique id is known to all servers that know about this comment and it is what is used when updates to the post are distributed. except for the reference to the item on the originating instance, no instance stores information about where to find a specific post/comment on a random other instance.
- Comment on I think thread deletion is problematic and needs some consideration and changes 3 months ago:
The “fediverse link” on a post always points to the instance of the person who posted it, not the community instance. When posting from a lemmy.world account this means the fedilink is always the lemmy.world post link.
It is only shown for content coming from remote instances in Lemmy UI 0.19.3, although a later version changed that to always show.
- Comment on Why do comments from lemmy.world users not appear until 4 days later? 5 months ago:
aussie.zone is just not keeping up with the amount of activities generated on lemmy.world.
it’s not going lower than a week anymore without actively doing something to improve this situation, and once a week all activities older than a week that haven’t been received from LW yet will be discarded on LWs end.
this is most likely mostly caused by latency from LW (finland) to aussie.zone, as lemmy only sends one activity at a time, requiring a round trip across the world for every single activity activity before sending the next one.
there are a couple things that can cause comments to show up on aussie.zone before they would regularly federate, such as someone searching the post/comment url on aussie.zone. some clients will do this automatically if you click a link to a post/comment from another instance.