• Confused_Emus@lemmy.dbzer0.comEnglish
    29 days

    Lulz, imagine being so butthurt over people being upset that you were manipulating their online experience without informing them first.

  • rglullis@communick.newsEnglish
    11 months

    So, I’ve rewritten the search / search boxes in Tesseract to skip the search and directly resolve activity pub URLs for users, posts, comments, and communities. I’m loving this as it makes things so much faster and easier.

    Isn’t that the whole point of webfinger? Moreover, why would you paint yourself into a corner and hardcode the logic for all the different types of services, if ActivityPub uses JSON-LD and therefore provides a straightforward method for document dereferencing?

    I’m not trying to be snarky. It’s just that I’m writing ActivityPub server where the id of each object is just an ULID, because to the server there is zero difference between serving the information about an actor or an activity.

  • moseschrute@lemmy.worldEnglish
    11 months

    I maintain my own Lemmy client (Blorp), and this sounds like a cool idea. How do you get your known list of federated instances?

    I currently have my own threadiverse crawler I wrote, but I disregard any Lemmy/PieFed instance with <20 monthly active users. That brings the list down to about 63 Lemmy instances and 7 PieFed. I wonder if that list is extensive enough to implement the resolve object mechanism you mentioned.

      • moseschrute@lemmy.worldEnglish
        11 months

        Ahh that makes sense. I guess you couldn’t search anything your instance doesn’t federate with anyway.

          • moseschrute@lemmy.worldEnglish
            11 months

            I believe it bootstraps the object, not the instance. You still won’t be able to find an object from an instance you don’t federate with.

            This is based on an explanation from @MrKaplan@lemmy.world, unless I misunderstood MrKaplan?

              • moseschrute@lemmy.worldEnglish
                11 months

                Sorry to bother you here, but I send you a PM. I would love to collaborate more. I have a group chat with the other Lemmy/PieFed devs. Some of the devs are already working on shared logic/libraries between apps. I also 100% understand if you’re spread too thin and don’t want more messages.

  • Jayjader@jlai.luEnglish
    11 months

    From my own experience querying public mastodon timelines via API (edit: removed incorrect /api/v1s in the AP_IDs):

    • Mastodon user accounts have an ActivityPub URI of https://<instance.domain.tld>/users/<username>
    • Mastodon posts have an ActivityPub URI of https://<instance.domain.tld>/users/<post_author_username>/statuses/<post_id> (they also have a url property of https://<instance.domain.tld>/@<post_author_username>/<post_id> but that tends to serve the html view of the post)

    To see for yourself, pick an instance that allows viewing their public timeline without logging in (mastodon.social is perfect for this) and follow the “Playing with public data” section of the docs. That page ellides most of the info you’re looking for in the example payloads they give (as the JSON payloads themself are quite large and nested), but I can assure you that AP_IDs for user accounts and posts can be found pretty quickly from a single timeline query.

    I don’t think Mastodon has any notion of community, nor does it distinguish between posts and comments (when following a lemmy community, both posts and comments show up in my masto feed as “top-level” statuses (ie posts)).