The link in the notifications would always lead to the first page of a comment thread. If the linked comment was not on the first page of the thread, you'd have to look for it manually.
Arghhh... Sorry, I replied with a longer message from my phone at that time - at least that's how it seemed to me. Now I've noticed that the response didn't send. In short, there must be an application account on the specific instance due to limits, but catch me on Matrix - we'll discuss it in detail.
Not sure if this is a known bug, but any time I'm signed in and try to enter the "all content" view (on any page) i get the "We are working on resolving the issues" error.
If I sign out of kbin it works fine, so it seems related to the fact that I'm signed in as me.
Sorry for reporting bugs here - I realize it's a bit lazy and not ideal!
Open source, non-corporate instances should be able to grow, and that growth will be stunted if most people who want to interact with the fediverse are deciding to go to corporate, profit-driven instances.
The issue is, how does defederating not promote leaving for Threads or instances that federate with Threads?
I think it's a good argument against Threads federating at all, but a poor one for defederating from Threads.
If Threads produces 95% of content in the fediverse, and your instance defederates from them, then your instance just doesn't have access to those 95% of content. Threads and its friends will be a lot more attractive then because it has 19x the content of what you have access to on your instance.
I think this will still lead to people leaving for the threads fediverse.
Also, I get the argument for Mastodon, but does /kbin actually have anything at all to fear here? Sure, the user numbers and content would be way higher than the rest of the fediverse. But Threads is a Twitter contender, not Reddit like /kbin and Lemmy. We will only see their content in the microblog tab.
Is the microblog tab actually that important to most people, that the instance could become dependent on Threads for dominating it? I honestly don't see it happen, I feel like this is an imported issue from microblogging platforms that's just repeated here despite being a non-issue for us.
I assume that 99.99% of that 95% from threads will not be missed and the other .01% will be linked by someone from a non-threads instance just like how tiktok and other social media currently gets linked.
Well, for the span tags, I haven't seen other tags being an issue. If you see a code block where the same issue occurs with other tags, tell me so I can update it.
If there is another Reddit exodus, for example, or if we get a surge due to the Threads thing, I feel like many will just turn back due to the UI alone.
I don't know if ernest's views changed since the last exodus, but iirc people joining the platform wasn't really his intention, it just happened. Kbin hasn't even had a proper full release yet, it's still beta software, so I don't think people bouncing off is that big an issue yet.
With the abandonment of Artemis (formerly kmoon), kbin is now only really usable by the mobile site.
That's the case for now, but app development is still happening with other projects:
ernest has mentioned intentions to revive his kbin app project
I understood OP to be talking about mobile specifically. If there is a way to get the userstyles on mobile it's gotta be like 20 steps long. If someone could somehow wrap it all up in an easy package that would be one thing but idk if it's really a viable solution.
I understood OP to be talking about mobile specifically.
And that's why I said Firefox or Kiwi. Both of those are mobile browsers (the latter is chromium) that support extensions, so you can just install your favorite monkey and stylus and add userscripts/userstyles the exact same way as on desktop.
kbin.social
Gorące