Nothing4You

ugh, i didn’t notice they’re even hiding domains of remote communities for “simplicity” in most cases. that seems so much more dishonest tbh.

this isn’t entirely true, they do have some comments on lemmy as well, here are some examples:

• https://programming.dev/u/[email protected]
• https://programming.dev/u/[email protected]
• https://programming.dev/u/[email protected]
• https://programming.dev/u/[email protected]
• https://sh.itjust.works/u/[email protected]

it seems to be primarily about their communities not federating though i guess?

and either nobody from there posted a post to a lemmy community yet or maybe it doesn’t federate posts currently?

lemmy.ml doesn’t use cloudflare, that’s strange.

i’ve also never had issues with this when looking at instances that do use cloudflare.

pretty much, yeah. lemmy has a persistent federation queue instead of fire and forget requests when activities get generated. this means activities can be retried if they fail. this allows for (theoretically) lossless federation even if an instance is down for maintenance or other reasons. if mbin has a similar system maybe they could expose that as well, but unless the system is fairly similar in the way it represents this data it will be challenging to integrate it in a view like this without having to create dedicated mbin dashboard.

lemmy has a public api that shows the federation queue state for all linked instances.

it provides the internal numeric id of the last activity that was successfully sent to an instance, as well as the timestamp of the activity that was sent, and also when it was sent. it also includes data like how many times sending was unsuccessful since the last successful send. each instance only knows about its own outbound federation, but you can just collect this information from both sides to get the full picture.

there is also https://phiresky.github.io/lemmy-federation-state/site to look at the details provided by a specific instance.

it’s not just lemmy.world.

of the larger instances, the following have trouble sending activities to lemm.ee currently:

• lemmynsfw.com -> lemm.ee: 2.81d behind
• sh.itjust.works -> lemm.ee: 1.04d behind
• lemmy.world -> lemm.ee: 22.5h behind

i pinged @[email protected] on matrix about 30h ago already about the issues with federation from lemmynsfw.com, as it was the first one i noticed, but I haven’t heard back yet.

at least the image resizing topic has recently been fixed in lemmy, thumbnails sizes are limited (at the time of thumbnail creation) in the latest release. I’d have to look closer at the other stuff, the api part is unlikely to have changed and will affect all frontends, but js part should differ depending on the front end. some instances already use other frontends by default and there is also a replacement for lemmy-ui being worked on (lemmy-ui-leptos), but I don’t know how they compare. either.

it should be taken into account though how much of this is cacheable as well, as it will then typically only affect the first load for the static files.

I can totally understand the issues in general though, I’ve been living with a 64kbps uplink for several years in the past.

requires sending ~25-fold less data per post

what are you referring to with this? AP traffic?

do you have some more information about this?

verification emails are usually sent immediately. if there are delays you should check your junk folder, and if it’s not there it probably won’t arrive anymore. depending on the instance you signed up on there may be alternative methods to reach out to the instance admins about this. note that private messages from mastodon to lemmy do not work unfortunately.

this isn’t true. it was incorrectly stated in the upgrade guide but has been removed a while ago. it was supposed to be a recommendation due to some issues with postgres 15. there is no postgres upgrade required between 0.19 releases.

account names cannot be changed.

you can only change your display name, which is available in the settings.

whether display names or usernames are shown depends on the interface/client and user settings where available.

the only way to change the username is to create a new account.

it seems to have become more frequent recently.

i’ve been experiencing the same on firefox and i’ve also heard other people report the same on firefox, which happened around the time of the firefox 129 release. i didn’t see anything noteworthy in the release notes though that’d explain this. it seems like it might be related to enhanced tracking protection and cookie isolation.

this is a lemm.ee limitation, not a Lemmy limitation, so this is the wrong community.

if you look at the instance sidebar at https://lemm.ee/ you can see that it’s 4 weeks.

for sure, but they’re neither mentioned on https://join-lemmy.org/docs/users/02-media.html nor on the linked CommonMark tutorial.

It’s not even just that. It seems that the extra @ acts as a separator, so you can’t even autocomplete e.g. @threelonmusketeers@sh as that’ll try to autocomplete @sh instead of taking the instance domain as part of the mention.

I’ve raised a GitHub issue for this now: https://github.com/LemmyNet/lemmy-ui/issues/2652

on firefox, if i type @gedal and click or press tab once it replaces the text with [@gedaliyah@lemmy.world](https://lemmy.world/u/gedaliyah) . the behavior is the same whether i hit tab, enter or click the text.

just as great as lemmy-ui

it does, but only if you use the autocomplete feature. it’s also a bit delayed without any indicator that it’s loading.

if you type @gedal and wait a moment it’ll load @[email protected] to be selected:

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).