How to use:

The url must be the hostname only, NO SLASHES, like this: lemmy.dbzer0.com, don’t use https://, don’t append a slash afterwards (lemmy.dbzer0.com/), only the hostname including the subdomain if it has it (in this case, lemmy).

If the instance has blocked the IP address from the server, or it is stuck and its API is not working correctly, it returns “Not a Lemmy instance” (I am too busy to fix this right now).

If the url is not formatted in a way it can process it, it will say Invalid URL. Better processing can come in the future. I won’t be updating it now.

In the backend, it just scrapes https://fba.ryona.agency/?domain={url} and uses the api https://{instance}/api/v3/federated_instances

PRs welcome.

Honestly it works better when deployed locally in a development environment. I think Vercel’s IP address is just blocked by cloudflare and other blacklists that stop automated stuff? Idk. Can check back in a few days.

  • Spaceman Spiff@lemmy.fmhy.mlEnglish
    1·
    1 year ago

    Not OP, but my communities are homed on a number of different instances. At minimum, I need to be able to interact with them, both reading and widely distributing my posts/comments. Preferably all on the same account, but that’s gotten more difficult lately.

    For any communities I may create, I generally want to ensure that they can be accessed widely, by most users in the fediverse.

    All of this preferably without having to deal with tankies, Nazis, etc.