Today, a technical server malfunction occurred. Unfortunately, it wasn’t the planned update yet. The upcoming one will definitely be much shorter ;)
For the next few hours, there may be some unusual errors. We’re still working on it. I apologize for the inconvenience.
I wonder how difficult it would be to have a “read only” version of kbin that replaces the full version when things go wrong or maintenance is being done. I’m sure there are other technical solutions, just one thought.
Interestingly, because of federation, this sort of happens anyway. If you’d hopped onto another kbin instance, or even Lemmy much of the content from magazines here was still accessable.
Exactly what he says. So you could use another kbin instance to keep viewing threads or posts.
Same logon / pass?
I do not know how to do that. How do I find other kbin instances?
Afraid not, each instance is independent in that sense so you need to go through the whole account creation again (although you can use the same username again, assuming it’s free).
That said, as with this instance, you can browse without needing to be logged in.
In terms of other kbin instances take a look here:
https://fedidb.org/software/kbin
Or here:
https://kbin.fediverse.observer/map
To give an example here is this thread on kbin.cafe:
https://kbin.cafe/m/[email protected]/t/154483/We-re-back
Cool. Thank you.
ha, honestly this was my experience. i run my own instance, so, except a few stale feeds, i didnt notice.