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.
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.
@user_naa@mastodon.social I’m not sure if this was intentional, but both of your replies to the comments here seem to have been deleted by you.
simply put: no
most fediverse software has its own API specific to how that application works. in some cases different fediverse software may be sharing a common API, which is typically a result of either a reimplementation (e.g. the Sublinks project is working on a reimplementation of the Lemmy API) or the result of a fork, where the previous API has been inherited and is typically built on top of.
It should also be noted that while Lemmy and Mastodon both use ActivityPub federation for interoperation, they have significantly different internal structures for how data is stored and represented to clients. I don’t know if mastodon supports vote federation with Lemmy at this point, but if it doesn’t do that currently, then using an alternative frontend won’t help you. It would likely be possible to build a Mastodon client that has a better thread view though, but it’d still have to be something built for the Mastodon API specifically.
What do you mean by “finish federation”?
Generally, individual activities (subscriptions, posts, comments, votes, etc) are federated within less than a minute of them being created. Your instance learns about other instances e.g. from votes seen on other instances. You’ll need to start subscribing to some communities on other instances to get started. You may want to check out Lemmy Explorer or Lemmy Community Browser to find communities and Lemmy Federate to automatically subscribe to other communities and get content sent to you.
The allowed instances list means that the instance will only connect to those instances and will refuse to send activities to any other instance.
for content that was not federated prior to defederation, yes.
this is by design. actor ids (unique identifier for accounts) should not be reused due to undefined behavior for how other instances will deal with that.
if you want to have a more technical explanation, https://socialhub.activitypub.rocks/t/reuse-of-identity-channel-addresses-revocation-reissue-of-keys/2888 does a decent job at explaining some of the issues with this.
except instance A will actively reject such content from B users when it hears about it from C.
generally it should be expected not to see any new content from B, but historic content will still exist and basically be in a frozen state.
the main problem is still that reports are not reliably getting to remote moderators: https://github.com/LemmyNet/lemmy/issues/4744
other than that it should be working.
starting with 0.19.4, at least user settings will default to their browser’s accepted languages on registration: https://github.com/LemmyNet/lemmy/pull/4550
this doesn’t solve actually tagging content, but it some progress at least.
ah i was misreading your comment, i thought you were talking about the sending side. for the receiving side i agree, but the reason for the duplicate activities is yet to be found: https://github.com/LemmyNet/lemmy/issues/4609
records can’t be duplicated in the database, the activity id is a unique key:
lemmy=# \d sent_activity
Table "public.sent_activity"
Column | Type | Collation | Nullable | Default
-----------------------------+--------------------------+-----------+----------+-------------------------------------------
id | bigint | | not null | nextval('sent_activity_id_seq'::regclass)
ap_id | text | | not null |
data | json | | not null |
sensitive | boolean | | not null |
published | timestamp with time zone | | not null | now()
send_inboxes | text[] | | not null |
send_community_followers_of | integer | | |
send_all_instances | boolean | | not null |
actor_type | actor_type_enum | | not null |
actor_apub_id | text | | |
Indexes:
"sent_activity_pkey" PRIMARY KEY, btree (id)
"sent_activity_ap_id_key" UNIQUE CONSTRAINT, btree (ap_id)
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