Nothing4You

this doesn’t really change anything for how remote users are displayed, it’s a change to properly support hosting lemmy-ui on a different domain than the lemmy backend/api.

what are you referring to with mastodon short.domain handles?

the unban itself federates, but on community bans the user gets unsubscribed from the communities, which deletes the associated subscription in the db.

skimming over the code it seems to be only happening in case of community bans (including the ones derived from instance bans on 0.19), but it should also remove your local subscription on your own instance. as long as that federates it should still be picked up by lemmy-federate eventually, as your local instance should also have removed that when receiving the community ban.

it might be debatable whether subscriptions should get removed with community bans for public communities, but overall the code logic seems to be there. i haven’t tested this end to end yet.

instance bans currently generally don’t federate and won’t show in the modlog of your home instance, but recent lemmy versions are automatically issuing community bans for all communities on that instance that you participated in, which allows you to at least see this in some cases indirectly.

1.0 will federate instance bans, but i haven’t looked at the implementation in detail yet and i’m not sure if this is already implemented to be shown in the modlog.

I didn’t mean only showing Anubis to unauthenticated users; this was in response to OP mentioning to add this before posting or commenting, which would be the opposite of removing it for authenticated users.

slrpnk.net has some first hand experience for this, as @poVoq@slrpnk.net already deployed anubis in front of lemmy-ui.

it wouldn’t be that complicated to add it to lemmy-ansible if people are interested in having the option.

i don’t see the argument for having this before user interaction though; the main goal of this is to fight malicious crawlers. for authenticated users, solutions like this are completely unnecessary as these can simply and much more efficiently be addressed through rate limits without putting users on low end hardware at a disadvantage and contributing to global warming.

it’s literally explained in the post that it uses admin credentials

it should cover all federated actions.

any instance admin can decide to ban you on their instance or remove your content on their instance, but unless it’s a local community or they’re mod of the community these actions won’t federate and will only apply to that specific instance.

the most useful one to look at is generally the one on the user’s home instance, as that should list all actions that federated.

instance bans currently generally don’t federate and won’t show in the modlog of your home instance, but recent lemmy versions are automatically issuing community bans for all communities on that instance that you participated in.

it’s also the case for deletions without account deletions, but iirc there is some delay before it gets rewritten in the db to allow the user to undelete it for a bit of time.

there seems to be a codeberg mirror but it’s not updated continously: https://codeberg.org/LemmyNet

instances get added automatically once they reach a threshold of monthly active users. iirc it’s >6 mau, you could check the code to confirm.

you can find your user info in the /api/v3/site response. the /api/v3/user endpoint requires a name or person id.

i recommend checking out https://join-lemmy.org/api/classes/LemmyHttp.html

you can only set a community to only allow local users, not prevent users from interacting with remote communities.

you’d have to either disable federation or set up a script to automatically remove all remote communities, but that also won’t be a per user thing, just a per instance thing.

You basically can’t if your instance was set up before 0.19.4, as there won’t be any association between users and uploads for older uploads. You also can’t do this without breaking thumbnails everywhere unfortunately.

The latest Lemmy version has a fix where thumbnails now are actually stored at a reasonable resolution for thumbnails, but old thumbnails may be quite large, and this does not retroactively shrink older thumbnails.

It’s possible to pull image aliases from the DB and ignore them when iterating over aliases within pict-rs, but you these will only be manual uploads, not automatic uploads like generated thumbnails. For posts by local users, deleting thumbnails will also end up breaking them for 0.19.5+ instances, as they should reuse the original thumbnail url.

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

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 @Xyre@lemmus.org 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.

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.

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.