Is it possible to directly post to a Lemmy instance with your domain name?
Is it possible to directly post to a Lemmy instance with your domain name?
My idea is this: I just want to send to a server like this a request from my domain name and username, but I don't want to run a full instance. Is this technically possible?
You're viewing part of a thread.
Let's say I just sent a request from my non-existent server with my user id, and just every time I wanted to check whether I got replies I would query the other server (which a Lemmy server would do to get notifications about replies or upvotes)
If I subscribe to [email protected] I could just... check [email protected] without actually loading any data to a server, I could just literally load it from lemmy.ml
I COULD host an instance, but why bother to store that data if I'm only going to be using it myself?
Let's say I just sent a request from my non-existent server with my user id...
Who or what is going to send this request if not some server that implements ActivityPub? This could be a Lemmy or Mastodon or Kbin instance... Or anything else that implements ActivityPub.
...and just every time I wanted to check whether I got replies I would query the other server (which a Lemmy server would do to get notifications about replies or upvotes)
ActivityPub works via pushes. So there's nothing to query. There HAS to be some server for it to send and store that data.
Who or what is going to send this request if not some server that implements ActivityPub?
Me, directly
ActivityPub works via pushes. So there’s nothing to query. There HAS to be some server for it to send and store that data.
Great, this is what I wanted to find out, so there has to be something listening for pushes
Not just listening, but also sending. Your instance also needs to be able to send your stuff elsewhere.
Yes, I now understand I need to have a server listening for the notifications being pushed to me
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: [email protected], [email protected]