/kbin meta

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.

Does the notification system work? I don't see any notifications even though I should.

minor issue but i can load "melbourne@aussie.zone" I can see their threads, but when I reply the reply does not appear on their end

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"

@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.

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.

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.

Quick note... some users are having issues with verifying registration if they miss the initial link. I was able to get kbin to resend mine by sending a password reset, but some users can't reproduce that. Just so you're tracking.

Too many posts weren't federating with kbin so I had to make a lemmy account to avoid missing comments from non-kbin communities, so hopefully the federation issues get fixed at some point.

Hi, not sure if this is the right thread but here goes.

Issue:
Threads do not seem to federate properly.

Description:
Until a month ago or so, submitting a thread to a federated instance (tested on: feddit.it, sh.itjust.works) threw an error page, but the thread was regularly posted. Example: https://feddit.it/post/1868675

As of at least 2 weeks ago, the error page remains but threads do not federate anymore. Example:
https://kbin.social/m/teoriamusicale@feddit.it/t/546143/Analisi-di-Pezzi-Pop-5-Faith-Hill-The-Way-You

If it can be of help, posts, links and comments seem properly federated to the same abovementioned instances, i.e. appear on target instances within a few seconds. No error displayed when submitting.

Hope this can be addressed sooner or later. Right now I'm using local accounts on those instances to work this around.

I'm begging for someone to take a look at the CSRF error that is still plaguing the site. Sometimes I can't upvote posts/comments withing 60 seconds of loading a page. I have to hit refresh every single time I want to vote on something or I'm taken to the error page.

The issue I had with Up/Down Vote, and Boost throwing errors appears to be resolved. Huzzah!!!

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.

First:

In these instructions:

$ sudo chown 82:82 public/media
$ sudo chown 82:82 var
$ cp .env.example .env

There is no directory "var" so the chown fails

Second:

When running docker compose build --pull --no-cache

It now fails with this:

=> [php app_php 20/21] RUN rm -Rf docker/ 0.2s
=> ERROR [php app_php 21/21] RUN set -eux; mkdir -p var/cache var/log; if [ -f composer.json ]; then composer dump-autoload --classmap-authoritative --no-dev; compose ...

This also seems to relate to the var directory, and so must be part of a recent change in the build that relates to the var directory.

Can anyone help?

Thanks

Tried to add my alt account on a different instance to the moderator list of the only magazine I own and got a nonsensical error message: Value isn't blank, but the error message says "This value should not be blank"