Hey, during the server change, I would like to switch to the version used on lab2.kbin.pub - many backend errors have been fixed there. Does the current state of the frontend pose a problem for you?
Hah, it does break a few things for me, but I'm working on fixing it as we speak actually. Honestly, I don't think some third party tinkering should hold back your official deployments, so go ahead and deploy whenever you want.
If anything, it would be awesome if the version number or similar was available as a class on the body or as a JS object (like KBIN_USER and similar). Then it would be easier to make the transition more seamless by supporting both the current version and the next version when it releases.
No issues for me! though i agree with @Perry that things we do shouldn't hold you back from developing. it's our responsibility to adapt :) but its very sweet of you to consider people making scripts and styles (●′▾‵●).｡.:*♡
@Prouvaire Thanks for the reply. Kbin was just a few minutes ago offline for a short amount of time. Now I have over 400 Reputation (from 5 before update?). So is this now fixed? I can't say if this calculation is correct at the moment. If so, this would be incredible coincidence with my post just 2 hours ago. :D
@ernest Thank you! Sorry I deleted my reply you was answering to, because I thought my question was useless. I didn't want confuse anyone here. It's just good to know this is worked on and not something by design.
I could probably add something like that to KUP if you want, but note that the way things work, one would have to load the entire page as usual and then hide the respective articles. This means that you could potentially in the worst case scenario get a bunch of empty pages until you actually get to see more content (or more likely, pages with very few articles).
With infinite scroll loading turned on, this could of course be a bit less cumbersome, but still not exactly an optimal experience.
Would that be an acceptable compromise? If so, I can see if I can get something done over the weekend. I'm currently tinkering with a somewhat related feature, so I could probably fit this in too.
This is beautiful. I grew up in Miami and I’ve always been obsessed with the color gradation in the sky there, especially the eastern horizon when the sun is setting in the west. Leonov definitely knows what I mean.
There seems to be an overall problem with federation and rss though. Ideally, you would want rss feeds to come in as though you were viewing the content through your home instance in order to facilitate commenting on posts and what not. But I have not found a way to do so. I may wind up writing my own scraper.
A short but very nice article, and some good discussion about meta that isn’t just “press the ban button”. It’s important to note that threads and Lemmy probably won’t have much to do with each other since it’s a Twitter clone.
One big thing is what I always say: decentralization is strength. Spread out over different instances and start your own instances or what happened on Twitter will just happen again.
I think kbin and Threads will probably have more interaction than Threads and Lemmy because of the native microblogging support in kbin. That puts them more or less on the same field.
I still don't think it will be very prevalent though. I've been using Kbin for quite a while now, and I have not once really used the Microblogging feature, just because it's tucked away in a separate tab, and it's not really what I use Kbin for
I quite enjoy how microblogging is integrated in kbin.social at the moment. It brings life to smaller communities, and connects us with the Fediverse at large.
For example, /m/gardening only has 12 threads at the moment, but since the microblog follows #gardening there are hundreds of posts in the microblog; several of which are from the last hour.
It's not perfect yet (if you open gardening@kbin.social from another kbin instance you won't see microblogs using the hashtag) and it's not for everyone, but to me at least it's a great bridge between kbin and the microblogging universe. :)
Hey, a month ago I would have simply pressde the button and not thought too much about it. Now the situation looks completely different. I have bookmarked all the discussions I came across, and next week I will read every single post to have a complete picture. I owe you that.
However, we need to think about additional privacy features, as priorities have drastically changed in recent weeks, and I will have to carefully consider that. Now that I have dealt with infrastructure issues, I will focus on the most important matters.
KBin/Lemmy should provide a combined local view for duplicated magazines/communities across the fediverse. Treating the concept like a hashtag.
The point of the fediverse is to distribute content so no one has a monopoly. People squatting on communities/magazines don't understand there is nothing stopping people creating one on a hundred other instances.
Each kbin/lemmy instance decides to follow magazines/communities from others through activity pub and stores it locally for the instance.
Having the UI retrieve all local posts with the same magazine/community name (e.g. m/star_trek@kbin.social c/star_trek@lemmy.world). Wouldn't be hugely difficult, I believe Kbin uses postgres database as the local store and suspect it would be a tweak to the SQL query it runs.
Even if that wasn't an option, there is a means to get all of the magazines/communities from the kbin UI/lemmy REST API. As well as retrieve all posts for a specific magazine/community. So you could do it entirely in a web client, for KBin it would be more work.
The combined view wouldn't change how you comment on specific posts. The issue is where do you post and what view would take dominance (e.g. if a magazine had themed itself).
The solution here would be to default your local instance if it exists or the instance providing the most posts/comments. Perhaps with a drop down so users can choose.
I would also configure things so instances can select a site wide default if they can't moderate it effectively. For example pushing all posts to the star trek instance rather than local magazine with a mod who is MIA.
This would remove most of the concerns users have about the fediverse, since they wouldn't be confronted by different instances. To them the fediverse is <insert instance> it would also encourage distribution of content.
Random stuff from all over the fediverse
Más antiguo