• 0 Posts
  • 97 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle


  • One thing I’m trying to keep an eye on is sup. Not much information at all besides a snippet of 1 to 1 encrypted messaging for activitypub, but the tidbit of working with any fediverse account is interesting. Potentially that could help deal with the different fediverse implementations of messaging. Of course, like I said, this is just me making up assumptions, it could not work the way I envision it at all. The creator just posted something 5d ago about it with “soon” though, so I’m hoping to read more about it




  • I don’t want to give false information, but on fedia the majority of 500 pages seemed to stem from the image media cache causing issues (our instance admin detailed the issue here). People were able to mitigate it by disabling images everywhere they could, but one place they can’t be disabled is the user avatars on the notification page. I could be wrong, but it’s my belief it’s those images causing the 500s, and that pushed me to add https://codeberg.org/Kbin/kbin-core/issues/1039 in hopes that if it was possible to disable them the 500s would stop. All this could be wrong though, maybe it’s something else like deleted messages or anything else, or maybe there’s a better way to solve issues with cached images


  • he’s eventually going to make sure abandoned instances have admins

    I think he meant magazines on kbin.social in this context. I don’t think he has any way to control another instance and change who runs it, besides a kindly worded letter.

    I do try to keep track of kbin instances and how up to date they are and their admins, but I can’t really advertise in their place. One thing I’ve kind of been thinking about is it’d be nice if nodeinfo had information next to current user count of like: desired user count, max user count. Otherwise you have no idea what an instance admin is hoping for, whether it’s just their personal instance or they’re willing to support tens of thousands of users. Without that I don’t want to send people to x instance and suddenly the admin being in for a surprise. But I just looked up nodeinfo and it looks like there’s plenty of worms in that can about it being too complex already, so maybe I’ll avoid opening my mouth about it… for now.





  • I’m not sure if this is a good suggestion, are you able to delete it via moderation as you’re the magazine owner? Someone mentioned having issues deleting their own posts but still could via moderation recently, but I’m not actually sure what that difference means as I haven’t moderated any magazines myself.


  • Definitely, you’re right that new timeframe doesn’t matter, I meant to type hot all time xD I would expect that to potentially grab like whatever was boosted most in the past but then again the algorithm does tend to show newer things even under hot.

    Yea the tag system might need a bit of work. It works great for some magazines, but for others not so much. For example m/help is supposed to be a magazine for kbin help but it pulls in everything under #help which can be anything in the fediverse. I did see someone suggest a way for a magazine to remove it defaulting to using the tag of its name, which doesn’t seem like a bad idea to me


  • Interesting, I’ve heard people say the same before. I do always sort by newest myself, but I sub to a bunch of magazines and also, say, three mastodon accounts, and that page is basically just solely the mastodon posts, very rarely do I see microblog posts in lemmy/kbin. I guess a filter of magazines vs users would be useful

    Edit: Also, is the default view all time for you? I could see that causing a problem as well if it’s hot / all time. I mainly have three bookmarks: /hot/12h, /sub/newest/24h, /sub/microblog/newest/1d. Getting all results for all of time by default seemed a bit weird to me, especially for microblog posts



  • Just to follow up on this, contributors to kbin investigated and found that startrek.website appears to block user agents that contain “curl” in it now.

    Example:

    curl -v --user-agent "curl" https://startrek.website/pictrs/image/3ff1b940-75da-4e6b-8948-834ebd4b454c.jpeg
    
    

    times out while:

    curl -v --user-agent "anything-else" https://startrek.website/pictrs/image/3ff1b940-75da-4e6b-8948-834ebd4b454c.jpeg
    
    

    works. kbin apparently sends User-Agent: Symfony HttpClient (Curl) in its requests for images, which is different than how it handles other fetch requests. they’ve made a PR to change kbin to send the user agent it uses elsewhere in those image requests https://codeberg.org/Kbin/kbin-core/pulls/1098 once that is approved / merged they should start working again as instances update. It’d be nice if, assuming this is all accurate, the block on curl could be removed so people don’t have to wait for the PR / instances to update but I understand if that is difficult


  • I do rarely see it on other kbins. Honestly kind of surprising considering kbin has no API. Not that it’s super difficult to do some headless browser automation but it sort of seems like whoeever is doing it must be super dedicated to targeting kbin.

    Do you mostly see it on m/random or other magazines? I’ve seen it elsewhere but it mostly seems to be from there. I kind of don’t quite see the point in allowing threads / microblogs to be made from a local kbin instance to m/random. Threads especially, at least. I sort of am thinking it might be nice if m/random was locked from local posting so you had to file it under a magazine with moderators, but spam bots would likely just make their own magazines or spam others and that wouldn’t really solve the problem.