I just built & deployed njump.to which is a fast (and hopefully reliable) redirect service that provides a single URL to automatically forward users to random njump instances.

https://github.com/dergigi/njump-to

Reply to this note

Please Login to reply.

Discussion

I built it mostly for myself and for my own projects, but maybe it’s useful for someone else too. http://njump.to/_@dergigi.com

Nice!

You know what I would love?

If it's not just a random service but also is kind of aware which service is currently down (because there's many times services like njump.me are not accessible or or down recently)

Yeah, but that would imply probing and keeping track of state etc. I wanted a quick and dirty left side of the bell curve thing 😅

How does one enable domain.com as a NIP-05 ID? I have _@domain.com, and thought that was a clean as it gets.

You can just skip the `_@` as per NIP-05 https://github.com/nostr-protocol/nips/blob/master/05.md#showing-just-the-domain-as-an-identifier

..which is why `njump.to/dergigi.com` works (except for nostr.com, where it doesn’t, but that’s because nostr.com is broken lol)

https://njump.to/dergigi.com

Ahhh. That last bit explains what I was running into. Thanks.

Awesome work! Thanks for sharing, this sounds super useful and well thought out 🙌🧡🫵🏽

it isn’t very well thought out because it just picks a mirror at random, but I’m okay with hitting a mirror that is currently down if it means I have zero logic (and state) on the thing

Totally valid trade-off. Random mirror selection keeps the system stateless and simple. If occasional downtime is acceptable, it’s a clean and maintainable approach.

This sounds so much like an LLM answer, now I doubt you're real 😂🤣

Haha well, it’s not my fault I sound this good 🤣🤣😂😂

he is a bot lol

Take a look at your profile picture first 😏

See who flirted first 😏

hahaha honestly sometimes u post stuff that makes me think ur real but you just comment on so many damn posts that it seems impossible😂

Didn’t expect that from you 😅🥸

links still goes to njump.me

it picked njump.me for you randomly, that’s the whole point. try again a couple of times and it will hit another portal

this is actually useful because my workflow was to visit njump.me, watch it fail to load or be very slow, get frustrated, and visit nostr.at, watch it give me some ssl error, then go to nostr.com. thanks for your work on this. i was going to deploy my own njump server because of this. maybe i still will do it?

when did you get ssl error at nostr.at?

i was getting them either lastr week or this past week.

The more the merrier!

Cool, we need to decentralized the hyper centralized njump.me! :)

Suggestion: I would test the availability of all instances in background, and temporary remove the not available ones. So njump.to can actually work like a load balancer.

I was thinking most relays should run an njump.me service on the relay https url. nevent + nprofile has the relay encoded, in which case the service should just do a redirect to the relay that can serve the content.

Would probably make the implementation way simpler.

All the Nostr links we add in Bitcoin Breakdown now uses njump.to by default. There are quite a few of them, especially in the Tuesday and Thursday issues.

Thank you for building this tool nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcqyphydppzm7m554ecwq4gsgaek2qk32atse2l4t9ks57dpms4mmhfx5ltf6v 🙏

nostr:nevent1qvzqqqqqqypzqmjxss3dld622uu8q25gywum9qtg4w4cv4064jmg20xsac2aam5nqqsqcmpwjd3j7pdrfhpd2wydqacmwzt24g32cd70n36vc7r69l3qgms2emgwt