I just saw some posts from beehaw.org and lemmy.world, looks like we’re back in business!
For now, I’m just preparing the groundwork, but first, I need to get some sleep :p
you’re the man too, the exodus is on? at least the ‘traffic is enormous holy shit’ prompt on the right is a good sign.
someone’s gotta help this guy though if it’s just one dude and his server rack in his spare room
*edit works looks like. yea this is cool, pretty much reddit, nice
The speed thing is interesting because for most of the time it’s actually not unusable. It’s a little delay here and there, but often fast or okay speed. it’s only sometimes that it gets kinda unbearably slow. But IMO as long as it’s up, I can deal with a slow speed here and there if it means I get to keep using kbin :). the dev/admin here is an absolute champ. kbin is awesome.
I prefer “sometimes it’s laggy/slow” over reddit’s “btw we’re gonna just die for an hour. lol you broke reddit, here’s a pic of a cat unplugging a computer”.
Indeed, pretty cool!
First thing I noticed though is that I’d really like to know which instance a thread is actually on.
For example, this post:
Going back to Reddit feels bad (kbin.social)
polygon, 2 hours ago to chat
… is actually on chat@beehaw.org, even though it says “kbin.social” and just “chat” below. Pretty confusing.
EDIT:
There’s at least one fix for this in the meantime – get this userscript:
https://greasyfork.org/en/scripts/468612-kbin-enhancement-script
I get what you’re saying – that the link source indicator should point to the instance that hosts the group – but it’s a quirk of how federation works that the thread is actually on kbin.social. And, well, any other site that’s following the thread.
Everything is actually local on the fediverse. It’s just that not everything has to originate from the local website. Federation works via content mirroring, which is why the URL for any given Magazine you’re viewing still starts with kbin.social. You’re not viewing remote content, you’re viewing local content that was imported from a remote source. And the link indicator is telling you where kbin has been told the content resides.
And that’s on kbin.social.
I think maybe the link source indicator just shouldn’t render if the thread doesn’t have a link purposefully attached to it, and the Magazine name should show the full name@host indicator.
Cannot tell you how much I appreciate things like this and how long it’s going to take me to get used to the idea of not being on a closed platform. It makes perfect sense, but it would seem to defeat the purpose of having the source there at all, like you’ve suggested. We know it’s on kbin, that’s where we are.
Threads are hosted on the instance that the magazine is on. I think instances viewing it also just make a copy?
You can check the @ to see the url for both users and magazines. I’m not fond of the fact that kbin often hides the @url for things. I’d much prefer to see it since it makes things feel bigger to me. @.chat@beehaw.org just ends up being shortened to @.chat lol. see? @chat @chat they are identical lmao. it’s annoying.
Also: I think usernames from other instances should show which instance they’re from.
There is a userscript for this now! Works a treat!
https://greasyfork.org/en/scripts/468612-kbin-enhancement-script
I think it’d make the comments a little cluttered looking. It doesn’t really matter what instance someone is from for regular conversation and if someone’s curious the can click through to the persons profile
It should be an option. Some people prefer the “clean” version of just showing username, with needing action to see url. while others prefer seeing the entire username+url even if it’s “messy”. I’d prefer the latter, while others might prefer the former. It should be a toggleable option.
I was thinking it should be included to avoid casual impersonation. I agree it would be a lop more cluttered though; maybe there’s another way.
Federation is back on the menu boys!
@ernest doing the business. What a dude.
If you have the means, sling him some funds
I mean seriously? This dude’s project has had hardly any downtime (like 100% inaccessible downtime) in the last few days during a massive migration. How impressive is that? He was able to find a solution with cloudflare where, sure things were a little slow to load and didn’t federate, but I never found myself unable to access kbin. On top of that, he’s communicating clearly and often. I hope this succeeds. @ernest has absolutely earned it.
Is slowly coming back, ernest is testing the waters, he said recently that he was working on upgrading the server and that federation will slowly come back.