Blocking a magazine does not keep it from appearing on your sidebar random thread/post feed. I blocked an NSFW mag and reloaded the page and it was still present.
This comment thread is behaving very strangely right now: comments with the same ID are showing up multiple times in different places, and I just received a notification about a reply that I don't see in the thread.
Checking "Hide Adult Content" doesn't actually seem like it blocks threads from nsfw magazines. When browsing threads by "newest", I definitely have multiple explicit pictures from explicit magazines (gfur, petplayyiff, & feralyiff?) I'm not subscribed to show up.
Yep, having this problem too. Just had NSFW magazines showing up in the Random list, plus still seeing porn showing up in search results. The "Hide Adult Content" box is definitely checked, and saved.
Both. I'm using the site on mobile and on desktop, not an app. My settings reflect that my default feed is set to Subscribed, but it gets reset to All whenever I go back to the home page, regardless of whether I change it to Subscribed from the home page or in the settings.
Hey not sure if this is the proper venue for this, but is the REST API expected to be functional? The root endpoint (e.g. curl 'https://kbin.social/api') works, but then all the others (e.g. curl 'https://kbin.social/api/magazines') fail with a 500.
At first I figured it was just a "kbin.social is overloaded" issue, but the behavior seems consistent across a few different instances (karab.in, kbin.lol, some others I forget).
Figured I'd check if the API is, y'know, implemented/enabled/whatever before I try and repro/submit an actual useful bug report.
I've been trying to set up my own kbin instance but without success. Is there a way to diable SSL? I'm running the instance on a raspberry pi at home behind a reverse proxy which already handles all the certificates for https. This already works great for my mastodon instance.
I tried installing the docker container and also manually but both times it expects https instead of simple http and I can't seem to find the place to change this. There's no mention of SSL in the nginx configuration file and I don't really have any experience with docker and where to change the configuration in such a container.
Weirdly enough, the manual installation seems now to work (the website is reachable) but kbin shows me a server error 500 for every site. I don't have mercure installed because I couldn't figure out how (it isn't mentioned in the kbin doc and the mercure website is not really helpful), could that be the problem?
@ernest wanted to report a beehaw thread being broken. See here. apparently they used hashtags in their thread title which is allowed there, and it broke for some lemmy users and ended up in kbin's microblog section rather than showing up as a proper thread.
Has anyone tried creating a KBIN server using the Docker instructions since Saturday? I got a development server running on Saturday and I decided to bring up a production ready version on Sunday, but now I'm running into two errors while creating it.
I have tried creating an instance on both Debian 11 and Ubuntu 22.04 with both Docker and the manual steps.
I can get the build to work fine. But at best I get 500 errors with no signs of logs as to why, not in postgres, not in nginx, not in redis or rabbitmq or even syslog.
On Docker i have both the kbin_messenger and kbin container boot looping with an error about creating cache directories. But since the containers are restarting I cant even get into bash on them to see why.
I finally said fuck it and ran the compose for "prod" and the containers start but again, 500 errors.
At this point....i give up i feel. I would love to host an instance and I am familiar with some of these modules (ie: NGINX, redis and postgres) but with how this is built, I dont see where the breakpoint is.
I operate my own homelab and have a background in SRE, so I figured I'd try out the same. I've wrangled a Mastodon instance install before, so this couldn't be too hard, right?
My approach started by using containers via lxc as a quick and dirty way of getting a development environment that enabled me to figure out if it worked and then see if I could then wrap it into a proper docker container and look at potentially publishing that.
On my first attempt, I did the manual route. I skipped the redis, rabbitmq, and postgres installs as I already operate those elsewhere on the network, but I got everything else running. Unfortunately, I also experienced the 500 errors. Most of the front page loaded, except for the content where the 500 error was displayed. Even with some digging around, I couldn't find a clear path to figuring out what was causing the 500 error, as the Mercure hub was seeing subscribers connect and disconnect. Gave up.
I then figured maybe the docker route might be easier/streamlined. I'm not a fan of duplicating services, but I thought that if the core workflow was solid enough, I could put effort into splitting them apart and go from there. Unfortunately, I don't even get past the docker-compose build for dev. Docker compose hangs forever.
Yeah. Kbin install made me eat some humble pie for sure. I think someone called me a normie in a lemmy thread describing my troubles. Lol.
To be fair some of the parts like mercure and rabbitmq im unfamiliar with. But it was a stone cold stumper for me and that’s rare. I’m fairly familiar with Linux admin, and even some of the tooling like docker. But I just couldn’t get it to work in a cohesive way. I ran plenty of Linux servers from Drupal instances, Postgres, nginx for all sorts of shit, etc etc.
My lemmy instance took….45 minutes to roll out. Though I already had an Ansible box sitting in my lab.
When I do an action on the site after like an hour, it takes me through the dumb cloudflare thing. I'm already logged in, why do I need to go through it every freaking hour?? This is an AWFUL user experience. I say "remember me" not "forget me in an hour"
I am not enjoying kbin.social right now. The latency is beyond atrocious, at 10+ seconds to load each page. The UI reminds me of 2004 forums that don’t know how users work. The mobile UI is just the worst.
Some pain points:
I’m a software engineer so I can figure this shit out, but how the hell do I subscribe to a magazine? If I go to it, there should be a “subscribe” or context menu at the top to subscribe/favorite/mute. (I found it, but it's so weird on mobile to click the logo then scroll to get to the subscribe.)
Why is the comment box all the way at the bottom? Where’s the “add comment” button on a post?
Why are comments paginated like a forum? Why not just a “load more” like Reddit? What’s the point? It's not to decrease the response because you can do that with "load more" buttons.
Selecting the comment box should NOT zoom slightly into the page. The mobile web UI needs a lot of work from people who know how to do mobile UIs.
Is there no “homepage” button? Clicking the Kbin logo at the top just brings up a menu, which requires another click on the homepage button to get back. This is weird and unintuitive.
Edit: And you can't collapse comment threads? What even...
I really want a Reddit replacement, but this is not it with this terrible UI.
Add issues to the codeberg.
RN there are users scripts and userstyles over at m/kbinStyles to add collapsing and move text box to the top. Users are already adding requests for these functions natively. The infinite scroll rather than pages is available in the gear icon on the side or in your profile
if you're a software engineer you should had known to make constructive comments and also most importantly realise that you are on a Non-commercial open source one-man-project. Your attitude is disgusting and you sound like the guys that nobody wants to work with. Nobody forces you to be here and you're welcome to go and please take your cancer with you on your way out.
This. Why?? This is a terrible user experience. I don't care if your little machine has case sensitive folders, it's bad form to have URLs be case sensitive with things users should be able to easily input (not like IDs like how YouTube does).
Not great that this requires a new account on a service most people won't already have :( I tried logging in with GitHub and it did that thing that I really hate federated logins doing where they go "yeah go ahead log in with your credentials from another site SIKE YOU HAVE TO TELL US YOUR EMAIL ANYWAY"
Add comment