I changed kbin.earth from kbin to Mbin, and it’s been working great. It definitely helps that Mbin is a fork of kbin.

Hello, this is actually a good place to post. We officially keep track of bugs & features with our GitHub issues, but you can always make requests here as well.

As for the feature itself, I don’t see any reason why we couldn’t look into adding that option. Honestly, I feel like we need an overhaul in general related to post/comment appearance options. I will add though, this is not the priority ATM, so it will probably be a while.

There is no way to hide NSFW posts client side in the app ATM. The expectation is that your Lemmy/Mbin/PieFed account would be configured with whether you want to allow NSFW posts or not, and the API would reflect that configuration. I guess it’s not working correctly on PieFed though.

I agree that jwr1 comes across as a bit passive aggressive here

Man, I really wasn’t trying to; I was just trying to have a friendly/helpful tone, which backfired I guess.

Well, a simple DB query gives us the answer.

There are 661 total local users ATM, only 32 of which have 2FA enabled. That gives us a measly 5%.

If you’re talking active (monthly) users, there are 161, only 19 of which have 2FA enabled. That turns out to be 11% (of active users).

Either way, it seems like 2FA is not generally used among users 🤷.

Not just this sentence but your whole reply is slightly passive aggressive and you’re asking ME to keep a nicer tone?

I am very sorry that I came across that way, I was certainly not trying to sound passive aggressive.

And the reply you gave to both of these are “I’m actually surprised that’s happening” and “I’m not really sure what the issue is there”.

I only mentioned I was surprised about it just because I’ve never had any other users report the error to me, that’s all. I also haven’t encountered either of the two issues myself.

You can’t seem to pinpoint on how a specific error pops up

That is true. I run this Mbin instance, but I’m not necessarily an Mbin dev, so I wouldn’t say I know the ins and outs of everything.

And you have no right to tell me not to use Mbin

That wasn’t what I was trying to say. I was just suggesting that maybe it’s not for you, but of course, you can use whatever you want.

Honestly, I wouldn’t worry about it. It’s likely just a technical issue, like bentigorlich mentioned in your other thread. I’d say as long as you’re able to access your account, then you’re good to go on that aspect. My only guess as to why the message popped up is due to some sort of delay in the system after you actually verified your account through your email.

Hello @BubblyRomeo! It is true, like @green_copper said, I have a life outside of Mbin, but I have now seen your comments (please try to keep a nicer tone though). I’ll try to help you where I can.

Interstellar uses kbin.earth as the default instance, mainly because they were both created by me. But you are most certainly not forced to use kbin.earth with Interstellar, you can add/switch to any Mbin, Lemmy, or PieFed account by going to the settings. And once you have added a different account (and switched to it), you can even remove the default guest kbin.earth account from the app.

As for your kbin.earth issues, are you saying anytime you try to log in, you get an “email not verified” message? I’m actually surprised that’s happening just because usually if an account on Mbin is not email verified yet, then it wouldn’t even let you make comments or posts yet. And for the 2FA problem, I’m not really sure what the issue is there, I tested it just now and was able to enable 2FA on my own account just fine; is it possible your phone’s (or whatever device you have the 2FA app on) clock is slightly off? Which could definitely cause issues for TOTP based 2FA.

You shouldn’t have made kbin.earth the default instance when signing up from the Interstellar app if your instance has some serious security issues!

kbin.earth is just an Mbin instance. The only thing I’ve really customized is the kbin.earth branding. If you think kbin.earth has security issues, then you probably shouldn’t use Mbin at all. That said, if you’d like to migrate to a different Mbin instance, Mbin doesn’t really have a good way to do that. If you have tons of magazine or user subscriptions, then you could try using Interstellar’s account transfer feature, but otherwise, you’ll just have to manually copy over your settings to your new account.

It’s all good! Honestly, I didn’t even learn about the issue from a post in this community, it was actually from a comment in the fediverse community.

I have commented in the Mbin matrix about it, but so far neither Melroy nor bentigorlich has seen it.

Thank you, this is actually already an issue I’m aware of and will try to fix for the next update.

I’ll say within the past few months there hasn’t been as much activity as there usually has been, so there’s not like a lot of new features coming in like there is for PieFed. Part of that is likely due to the fact that Mbin’s low on devs ATM, especially since one of the previous devs went AWOL. Still, I’ll say Mbin is already quite polished and works well, even if the dev team isn’t as active as they once were.

Luckily, I was able to mitigate it within the week it started, by setting up specific Cloudflare firewall rules. I just haven’t remembered to downgrade the server since it happened :)

The experience for setting up an Mbin server has greatly improved with the latest Docker setup rework. So now, it shouldn’t take more than a few minutes to get a simple Mbin setup running.

As for resource usage, my server (kbin.earth) doesn’t have anywhere close to the user base fedia.io does, but I’ve been able to run my server (which has ~150 active and ~600 total users) on a decently low-resource server. In the past month or so, it’s been a server with 16 vCPUs and 32 GB RAM, but previously it was running on 8 vCPUs and 16 GB RAM (had to upgrade due to DDOS).

I’ve been running my server for about 1.5 years (since December 2023), and most of the time it is a set-and-forget type of thing, of course, until you need to update things or troubleshoot some issue. But overall, it’s been working great, and when you do run into an issue, the Mbin devs are usually quick to help troubleshoot with you.

It is true that Mbin doesn’t have an “official” instance, but there are multiple servers that are run by the Mbin devs, including thebrainbin.org, gehirneimer.de, and kbin.melroy.org (and kbin.earth if you count me).

Well, sorry about that again. Really Lemmy should have never let it happen though.

Oh lol, is that still a problem?

Thank you for the report! Unfortunately, this is not enough context to be able to fix. Is it possible you could tell me exactly what you were doing? Were you literally just scrolling through the comments? Which post were you seeing it on? And are you seeing this consistently?

Yes, in parallel, both at the same time. Sorry if I hadn’t made that clear.

Considering there wasn’t anybody interested yet, I’m not even sure if I will set it up. I’ll just have to see.

What is the difference between the three options within Settings > Feed Defaults > View. There’s Threads, Microblog and Timeline options, but I can’t see what effect they have on the feed.

That sets the default Feed View for when you’re on an Mbin account. Mbin has options to view threads (the Lemmy side of the fediverse), microblogs (the Mastodon side of the fediverse), and timeline (combined threads and microblogs), whereas Lemmy and PieFed don’t have microblog support, only threads.

When viewing comments, some replies are shown and nested, but others require tapping Open x replies. What determines whether a reply is shown automatically or needs a tap to open?

That’s totally dependent on the API’s response. If Interstellar sees the API returned a comment that has X listed as the number of children, but the API didn’t actually return those children, then it displays the Open X replies button.

I’ve made an issue for it on GitHub so we can track it: https://github.com/interstellar-app/interstellar/issues/207