Hi everyone, I was trying to create a link sharer that works across Lemmy instances. The idea was to convert the federated url to a local url by using the api. You would save your instance of preference with the website, and it auto directs after a few seconds. However, I ran into one major problem. Both the search and resolveObject endpoints require authentication to do what I needed it to do.
An alternative would be to redirect to the search page, but that wouldn’t be much more convenient than just doing it yourself.
Does anyone have other ideas for tools (or etc) that could benefit us Lemmy users?
I already got a domain for this project, lemmy.express, but in the worse case someone could use it to run an instance on it.
Your redirect idea would probably work excellently as a browser extension — there are are redirect extensions like that for Mastodon already, actually.
As for the domain… the only thing I can think of would be, like you said, a Lemmy instance.
Firefox already has the Lemmy Link extension to do this. It seems to work pretty well from what I’ve seen.
Ooh nice, and it is also available on chrome.
Yeah a browser extension could be a good alternative. I was initially hoping to use a website based tool so that it could work regardless of the users platform / browser. And specifically mobile.
I had to do something similar for the search engine I’m working on. What I’m currently testing is indexing the
api/v3/post/list
endpoint and matching on theactor_id
to the internalid
. The only major problem with this is that I now need to crawl the entire fediverse in order to support all of the different sites.(Sorry for replying to your root comment, your reply isn’t showing on my instance)
Ideally what I’d love is if posts worked like communities. For example you can navigate to https://lemmy.world/c/lemmy_support@lemmy.ml and you’ll be taken to the community page on Lemmy.world. But if we could link to something like https://lemmy.world/p/1543053@lemmy.ml and land on a particular post, that would make having to do a lookup completely pointless.
There is some good and some bad news for this. They are aware of this problem, and are having discussions to change it. But I don’t know when it is coming. And I agree that a lookup would be useless if we can simply create the url directly.
Oh wow, that’s also a huge undertaking! It is kinda sad that the
api/v3/resolve_object
endpoint was working without auth before the 0.18 release. Maybe I can see if we can get an api endpoint specifically for this? Without needing auth and without returning all the post information that we aren’t interested in.