Skip Navigation

Posts
10
Comments
225
Joined
2 yr. ago

  • Have you blocked anyone? There's a bug that causes certain threads, including your own, to not be visible to you outside your profile. It's caused by you blocking anyone at all iirc. Or maybe it's about blocking domains, I forgot the specifics, but try removing any and all blocks and see if that solved it.

    It's fixed in the latest code iirc, but there's not been a stable release yet that incorporates the change.

    Additionally, and I have no idea if this is related, I cannot send direct messages to anyone outside of kbin.social

    This is correct, direct messages only work on the same instance currently. If I remember the previous discussions about it correctly, this is intentional for some undisclosed (or lost to time?) reason currently. Like, the developer has specifically added code to cause this behavior, I assume because there were worse issues with it.

  • Loved this first episode, perfect adaption imo.

    I can see all the girls up to Rin in the visual, except for the next one after the ones announced to be in this season (aka the fifth girlfriend). If they're hiding her from us, could that mean we'll actually get her this season? Not going to say names since I don't want to spoil anyone, but manga readers should know whom I mean.

  • I've never been blocked, so I might be wrong there. But the last word problem was the main reason I've seen people hate the move to the current blocking system, so I assumed it didn't exist before.

    Edit: Reddit's official announcement for the new system does explicitly mention they're changing it so you can't interact with users that blocked you anymore. Which implies you could before.

  • It used to be possible on Reddit, and people didn't like the change to how it is now. Because of how it can be (and is being) abused.

  • Is this issue being actively fixed right now?

    I doubt it. They've had more important stuff to work on and probably forgot about that issue in the meanwhile. That said, best would be to just comment on it asking what's up with it. That'll bump it up in visibility.

  • You probably won't see this, but I've sent you a private message. Hopefully that one arrives.

    I assume it's the blocking bug, which is getting fixed this update I think.

  • Does it have an issue on codeberg?

    If not, I recommend bringing it up there. If you only bring it up here, you rely on ernest or another contributor writing it down and remembering it, which probably isn't too reliable. Better to put it on the issue tracker.

  • With regular search, I have to look through all kinds of results before I find something, and often I have to adjust my search parameters until the search engine even understands what I'm looking for.

    The AI still needs me to actually confirm what it's saying, but that's checking 1-3 links, not entire search result pages.

    It's also just waaaaay easier to talk to my search engine in natural language than keywords imo. I never know what keywords get me to my intended destination, I guess the difference is less big for people that do.

  • So, slight correction to my previous post (which I now deleted) thanks to @troplin.

    It seems that phrasing content like \ elements are allowed inside \ elements according to the spec, so Lemmy is actually doing the right thing there. It's on kbin to fix this, not Lemmy.

    I commented on one of the closed issues about this on the kbin code repository, asking for the issue to be reopened. Hopefully it will so this gets fixed, I'm not sure though how visibility works if the issue is already closed. I'll make a new one if it's neither reopened nor replied to until next week, if no one else does first.

  • You're right, I only read the beginning of article, the Mozilla docs also mention the phrasing content later on the same page.

    Guess it's really on kbin then to fix this.

  • The great thing about Bing Chat compared to other chatbots is that it sources its claims. I always check the sources before trusting it.

  • Only monetized games have to pay. If they stop selling the game, they shouldn't be affected anymore.

    Also

    Does the Unity Runtime Fee apply to pirated copies of games?
    We are happy to work with any developer who has been the victim of piracy so that they are not unfairly hurt by unwanted installs.
    (source)

  • I have definitely seen magazine CSS before, so it should work. That CSS in particular works as well when I use it as a userstyle in Stylus, so there's nothing wrong with the CSS.

    So I'm guessing the issue here is precedence. Your browser is probably preferring a different style over your magazine CSS. You should be able to check in the dev tools (f12 in chromium browsers) whether that's the case, as your style should be listed there when selecting an element it applies to, and, if I'm correct, the background should be crossed out.

  • @sparseMatrix

    I found something in a recent FAQ that says I should add an article instead of a post, but the option to add an article is not on the menu on my instance

    Looks like what you found was just outdated. It used to be "article" because of the whole magazine themeing, but people found that confusing so they changed it to "thread". Because, you know, it'll show up in the "threads" tab. So the correct option is "Add new thread".

    The short story is, the microblog here is essentially a right pain in my ass.

    If you get yourself a userstyle extension/addon for your browser (like Stylus for chromium ones), you can hide the tab if you don't want to see it.

    This should work:

     
        
    menu.head-nav__menu > li:has(a[href$=microblog]) {
       display: none !important;
    }
    
    
      

    Assuming your browser and version supports the :has() selector, as it's relatively new. You can check support here.

    This will remove the "Microblog" tab from the list, though other links to it will still get you there. So if you do want to see the tab for some reason, you can still just add /microblog to your url manually.

  • I agree, I also think kbin isn't doing anything wrong here. But it might still be able to take actions to prevent or mitigate this, so that's why I suggested posting about it to the codeberg repository.

  • This might be related to the artemis.camp post that showed an unrelated nsfw thumbnail there but not on kbin.social and other instances. Artemis is also running kbin.

    Referring to this post.

    I know one contributor to both artemis and kbin knows of the issue, but not whether it's a kbin or artemis.camp issue and what's causing it. This seems to suggest it is a kbin issue, as it looks like the same problem to me but on kbin.social.

  • I don't know why your browser treats this as a download, seems to be incredibly insecure.

    If I didn't know others already confirmed it to be a video, I'd assume this was a scam website, distributing a virus disguised as a video. The actual url is encrypted so you can't tell what it actually points to, while the file extension is mentioned in the url parameters to give the impression it's a video file when it could really be anything. And it's being downloaded from Russia.

    I think it was definitely a good idea to post this. You should probably look for a better browser that doesn't treat every shady url as a download. One misclick and you can get a virus on your phone like this.

    As for kbin, I recommend making an issue about this on the codeberg repository. That's the best way to get kbin to actually do something about this.

  • My best theory this point is OP's browser is cropping the URL for some reason, which means the ".mp4" part isn't seen. The browser is then trying to save the 404 response to the request for a file which didn't exist, and had no extension.

    I looked at the actual web request url it's doing for me.

    https://downloader.disk.yandex.ru/disk/dfc79ab0f88295834385d89e14b27d1f687e201bf8074f21e0d0d9972096319a/64dc8782/MuDSbA9z5TnczT15nZM5tfipdB2eZIesleov6SiJ-7hJ1g7sSwJpQ0lNHok396G53tTWxxKw4e4GuLUmFQ%3D%3D?uid=465360380&filename=7fed06c9.mp4&disposition=attachment&hash=&limit=0&contenttype=video%2Fmp4&owneruid=465360380&fsize=14161986&hid=9d62d8b95cb1158833293fffdf4deada&mediatype=video&tknv=v2&etag=a5f932a629c3d365ed6d74bd3ac546e6&expires=1692173809

    I don't know why they're getting a download offered in the first place for such a scam looking url, but the display on OP's image is clearly separating the url into its components and only displaying some of them (the domain and file name). The file extension isn't part of the url itself here but rather the parameters which aren't displayed here because there's usually no need to and they would take up way too much screen space on mobile.

    I think hiding the parameters is a good idea. While comments suggest this is a real video file, this could have easily been a virus disguised as a video. By hiding the parameters, you're preventing unsuspecting users from putting too much trust into those parameters.

    Edit: reworded the comment