keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
902 stars 37 forks source link

Keybase.pub doesn't resolve in DNS #4208

Open spitfire opened 8 months ago

spitfire commented 8 months ago
nslookup keybase.pub 8.8.8.8
Server:     8.8.8.8
Address:    8.8.8.8#53

Non-authoritative answer:
*** Can't find keybase.pub: No answer
GwynethLlewelyn commented 7 months ago

I guess you missed their announcement; the keybase.pub service was discontinued on March 1, 2023. Here is a thread on Reddit about this, including the original note sent out by the Keybase team: https://www.reddit.com/r/Keybase/comments/10xeqbw/keybasepub_shutting_down_on_short_notice/

That thread also notes some alternative ways of accomplishing the same, using the kbpbot (which is still operational!)

spitfire commented 5 months ago

I guess you missed their announcement; the keybase.pub service was discontinued on March 1, 2023. Here is a thread on Reddit about this, including the original note sent out by the Keybase team: https://www.reddit.com/r/Keybase/comments/10xeqbw/keybasepub_shutting_down_on_short_notice/

That thread also notes some alternative ways of accomplishing the same, using the kbpbot (which is still operational!)

Thanks for info, the app is still saying this ¯_(ツ)_/¯

image

Do I understand it correctly and I could point my (sub)domain to it to replace keybase.pub?

GwynethLlewelyn commented 4 months ago

Ha! I have no idea where exactly you see that on the app — I guess this ought to be an issue by itself, i.e. a request for removal of a banner/callout which is outdated.

Do I understand it correctly and I could point my (sub)domain to it to replace keybase.pub?

Depends on what you mean with "pointing your (sub)domain to it".

You can certainly mount your public directories on your own webserver, and point a domain or subdomain to such a subdirectory. That should work, at least on the Unix world, but requires a bit of tinkering, since the mounted directories usually are mounted-on-demand while you, the user, are logged in to the system — and unmounted as soon as you logout.

You can thwart that behaviour, although it's not immediately obvious on how to do it. Still, it's within the capabilities of the command-line tool(s) provided with Keybase.

Depending on your own server's setup, and the level of caching you can perform (as well as external CDNs such as Cloudflare), you should even get pretty reasonable performance that way. Don't expect miracles, though: accessing a mounted Keybase directory is slow (for many reasons, such as dealing with the complex encryption system used by Keybase, as well as the limitations imposed on their own network infrastructure).

The question is more why you would want to do that. One possible reason is that you might not have 250 GBytes free on your server's disk (because, say, your "server" is actually a cheap VPS with virtual storage of "only" 20 or 40 GBytes), and this would be a neat way to "extend" your available disk space. That would make a lot of sense to me — 250 GBytes are not an infinity of space these days, but they're far more than you get from cheap VPS providers.