You can go to "Settings" or "Profile" and you'll find a subscriptions tab.
Alternatively, you can install a userscript that adds a faster way of accessing them. Here's one I recently made and one made by raltsm4k.
Thanks, this is the best implementation idea for this I've seen yet imo, will definitely be using this from now on.
I haven't found any bugs yet, but I'd like to request two future improvements:
Changing the order of magazines and collections
::: spoiler Details
I have like three collections and a ton of magazines, so having to scroll through all the magazines to reach the collections is a bit of a pain. It's still much easier than before this script, but it would be even better if I could move the collections above the magazines.
On the other hand, someone else might have the opposite situation and would prefer it the way it currently is, so unlike the other user I'm not asking you to just swap the order.
I think the ideal solution would be adding a setting somewhere to determine which comes first. So every user can tailor the functionality to their needs.
:::
Support for turbo mode
::: spoiler Details
Ernest added turbo as an optional mode in the past months (you can find it in the sidebar options). It turns the site into a single page experience, which means kbin.social links don't open the website anew entirely but rather replace the page content, including the changes your script makes. This cuts down on loading time, but it also causes scripts to break.
It would be great if the script were to support turbo mode eventually, especially if Ernest makes it the standard in the future (it is marked as experimental currently, so that's probably the eventual intention).
To do so, you'd have to attach a MutationListener to the body element like I did here. But that will run many times more than just on navigation, so you'd also have to ensure your code does support being run multiple times without breaking.
:::
As an aside, I downloaded one of the Lemmy apps to get my fix while things were having issues here. And while it wasn't bad, I'm definitely glad to be back. Huge appreciation for the function and form of Kbin and the tremendous amount of effort put in to keep it awesome.
you need to have an honest conversation with yourself before you address any further issues publicly.
from “if the update isn’t out by september consider this project dead” to “i’ll be working on it for a few hours then it should be good to go” you clearly have trouble estimating the amount and scope of work necessary to maintain a site of this caliber.
i’m not trying to be insulting to you, but you need to understand it’s starting to get tiring as a user too. take stock of what you are doing and pause for a moment before you give your users a defined timeframe.
the post where you said it would be a few hours is still up and unedited. that was 3 days ago. i wouldn’t have minded you saying “it will be a few days, maybe a week or longer” at the get-go but now we’re approaching 1000% estimated time to recovery and it feels like you are no closer than you were 3 days ago. it’s insulting and it definitely doesn’t need to be that way.
Good luck trying to convince this man. I'm sad to say that what I predicted, now two months ago, is happening. My advice; don't rely on kbin.social, find another instance (I recommend Mbin) or make one of your own.
There are a lot of instances, just keep looking. Find the communities/instances you like, and subscribe to them from whatever quick, lightly-used, geographically-close to you instance you find to register on.
There's literally no location indicator for the instances servers so I'm not sure how you expect me to do that. And smaller instances are more likely to get abandoned, go down and vanish.
I don't quite understand what you mean. The problem is that in such a case, it's challenging to provide a specific estimate. That's why I occasionally provide updates in case the work is prolonged. It seems to me that this is how it works. Issues arose without any interference in the code or infrastructure. I addressed hardware problems, but it turned out that wasn't the only issue. Throughout this entire period, I've been attempting to ensure that the instance operates as smoothly as possible. It should be significantly better now, but I'm still actively working on it. Unfortunately, taking a holiday break here doesn't help either.
“I’ll be working on it for the next few hours” is different than “I’ll be working for a few hours today but have not identified root cause yet so I can’t say how long the fix will be”
“The update will come in September or consider the project abandoned” vs “I want to have the update out by the end of September but can’t guarantee any timeframes until I’m further along in the work”
“It should be back up in a few hours” vs “I’ll update everyone again once I’ve identified the issues and am working towards a clear resolution”
I’m not asking for more work or more communication, just honest communication.
Issues like the one that occurred are typically resolved within an hour, hence this post - mainly to quickly inform that work is underway on it. But you're right, I'll strive to improve communication in the future. Your examples gave me something to think about, thanks.
Honestly @ernest I don't think you have anything to worry about.
It is your platform. Make it at your own pace. Most of us are very happy to be invited on this journey and recognise that there are going to be ups and downs.
It's the biggest lie that there is "server upgrade and service will be recovered in couple of days" or something like that. Unless it is constant server upgrade.
I had commented on another post of yours that had the issue just now in case you werent aware it was happening but looking at your profile it seems like it’s only 50/50, some work just fine. Hopefully it’s a broken dependency (?) in an update on the kbin or lemmy side and gets fixed in the next update.
You mean Nijimiss? I'm running the searches for that within Kbin Social, and not the opposite, and tinkering with the VPN, Kbin doesn't seem to have problems with EU IPs (isn't it from Poland? I have the impression I read something on that previously).
yes, i mean the Nijimiss site is actively blocking european IPs, which would include requests coming from kbin.social, and might be the root of your 500 errors. i noticed lemmy.world (finland) also cant make those requests to nijimiss.moe successfully.
my instance is not in europe, so it seems like it can make those requests without error.
A few suggestions that may or may not be satisfactory for you:
Using KES, enable General > Hide sidebar elements > Random threads, Random mags, Random posts. The randomly populated sidebar is fundamentally flawed; I suggest disabling its content altogether.
Next, enable General > Filter advertisements. This second feature is by no means foolproof, but will reduce a lot of noise, and is periodically updated on a rolling basis.
Most of the content being federated to my instance from kbin appears to be mostly adverts for websites selling pharmaceuticals - usually advertising controlled substances.
After a couple from the same magazine(? kbin’s term?) I just block the community. But it’s pretty non-stop. I guess it’s not yet considered to be worth defederating, but yowsa.
Kbin got the same rexodus boost as lemmy but since then has many more atrophied communities and far fewer moderaters to do anything about it, hence spamalot.
I've only seen 1 or 2 pieces of spam in my feed and that was months back - interesting that you seem to be seeing more of it on a federated server. I only started blocking those magazines when I noticed the spam on desktop sidebars.
I just saw another one in random(@kbin.social), so I jumped in and scrolled back; there were only a couple in the past two days, but three days ago there was a series of several posts in a row (6? 8? Something like that).
I an not subscribed to any kbin magazines, so I don’t see them in my curated feed; they mostly show up in the uncurated “World.”
FWIW; you expressed curiosity, so I followed up with an example.
Unforcunately the admin\creator of kbin has personal issues and is missing. We need to leave, but that means migrating manually which is annoying. Too bad, there are some good idas here.
If your main goal is exporting your magazine subscriptions between accounts across instances, may I suggest trying EXIT tool. If you are looking for more complex export settings (friends/favorites?), unfortunately, only subscriptions are supported at this time.
I understand why they disabled public downvotes (since they're accepting incoming ones now, they don't want to expose everyone's downvotes from other instances), and I remember they gave some reasoning on Github for why it makes sense to not hide upvotes too, but do we really need incoming downvotes? I think that feature should be a toggle where you either have downvotes hidden but federated, or visible but not federated. And then the instance owner can decide what they prefer.
That's really my main issue with mbin. While I've gotten too used to the All Content view and collections, both of those are on their roadmap, so they'll be coming eventually.
kbinMeta
Ważne
Magazyn ze zdalnego serwera może być niekompletny. Zobacz więcej na oryginalnej instancji.