For now, I’m just preparing the groundwork, but first, I need to get some sleep :p
You are killing it. Keep it up and take care of yourself!
just kidding
You’re the man!
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
deleted by creator
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.
deleted by creator
So far I’ve used kbin entirely from my laptop web browser. I haven’t tried accessing it with my phone just yet.
deleted by creator
Definitely been more stable than reddit.
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”.
I don’t know why but the “you broke reddit” message always frustrated me. I didn’t break shit lmao, it’s the site that’s broken
deleted by creator
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 [email protected], 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-scriptI 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.
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’m still not able to subscribe to magazines on here from Lemmy, which is interesting. Maybe federation needs some time to catch up.
Same. I’ve tried searching for kbin from lemmy, but nothing ever pops up. Not sure if I’m doing something wrong or it just isn’t fully working yet.
Figured it out - you have to put the entire URL into the Lemmy search bar. For example, to find @modeltrains, you need to search Lemmy for https://kbin.social/m/modeltrains.
Once one person subscribes, then the community will show up in searches for “modeltrains”.
What about for Lemmy from Kbin? Like on the Lemmy page it says to type [email protected] into your search to get the result, but when I enter that in the Kbin search bar it errors out.
@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.
