• 0 Posts
  • 24 Comments
Joined 8 months ago
cake
Cake day: March 24th, 2024

help-circle



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




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





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










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