I’m a #SoftwareDeveloper from #Switzerland. My languages are #Java, #CSharp, #Javascript, German, English, and #SwissGerman. I’m in the process of #LearningJapanese.

I like to make custom #UserScripts and #UserStyles to personalize my experience on the web. In terms of #Gaming, currently I’m mainly interested in #VintageStory and #HonkaiStarRail. I’m a big fan of #Modding.
I also watch #Anime and read #Manga.

#fedi22 (for fediverse.info)

  • 0 Posts
  • 200 Comments
Joined 2 years ago
cake
Cake day: March 11th, 2024

help-circle


  • It isn’t currently treated as an upvote by Lemmy, yeah. But Mbin does count boosts to the score of a post when ranking them.

    My point I was trying to make was more that I think Mbin tried to address the issue you’re pointing out there. Boosts actually even used to be swapped with likes in the early days of /kbin, and upvotes are still called “favorites” even today. Boosts are also not in any way displayed as retweets on Mbin itself, so I doubt they were intended to be used that way by users. But yeah you’re right on the actual implementation of how they’re federated.

    When it comes to actually using them, I do stick to favorites for content I like and boost for promoting stuff I think should be seen by more people, but in most cases I ‘like’ what I want to promote (so I end up using both), and in the rare case where I don’t, I don’t really care that Lemmy isn’t counting my one upvote. I don’t upvote/boost my own content either despite knowing that Lemmy expects a self upvote.



  • There have been some users reporting they get ads despite being Premium users, especially in regards to Youtube’s efforts to bypass adblockers (even if they weren’t using one). I always assumed that’s because their measures were misidentifying the lack of ads as using an ad blocker, even if that lack was due to using premium.

    Just wanted to give an actual explanation. I’m not qualified to actually confirm or deny whether those user reports were factual or made up. But people usually consider them factual because of herd mentality.


  • Not just the premium part, but also it affecting descriptions makes me think this is some kind of bug. At least partially. There’s not really any point to disabling descriptions specifically, most people don’t read them anyway.

    “there’s currently no way around it” “The issue goes away with a refresh”

    The way I understand it, the issue only resolves if you refresh while on the video you want to watch. Navigating to another video would unfix it again. So it’s not really a real fix the way most people expect a fix to look like. They want something they can apply and then they don’t have to deal with the problem anymore. Which, based on this article, only disabling your adblocker achieves.


  • For people who only go off headlines and comments and don’t read the article, here’s the important bits:

    • This only affects some users, not everyone
    • The issue is that comment sections are disabled and video descriptions claim to be empty
    • The issue goes away with a refresh, you don’t need to turn off the adblocker, though you’ll have to refresh every video
    • It affects all videos
    • The link to adblockers is due to everyone who is reporting the issue being a user of an adblocker, and turning it off fixing the issue permanently until it’s turned on again
    • There’s no specific browser or adblocker mentioned in the article
    • It affects Premium users too

    edit: added “the article” after “don’t read” to clarify









  • You’re clearly cherry picking OP’s comment there, conveniently leaving out what makes what they saw problematic.

    I found that the members of r/luckystar were saying very sexual things about characters that, while 18, had very child like designs. And even if, they were saying shit like, “Cunny!” and, “Correction!” so, yeah.

    Those terms are specifically used by the pedo “roleplay” portion of the anime fandom, there’s not really any ambiguity there.

    Like, on the first sentence, I’d agree with you. But the second sentence makes it clear that they saw the disgusting part of the fandom.




  • The big problem with improving how this stuff works on the fediverse is that you want to stay compatible with other software and instances running older versions of your software. In general, ActivityPub projects expect the id of an actor to be dereferenceable. They expect it to point to a valid JSON-LD document describing the actor which they can request. If you break this expected contract by using a local file as your identity, or even just a non-https URI like did:, you’re going to lose intercompatibility with other instances that don’t handle that.


    Also, regarding your description of the three parts, I think you’re misunderstanding something that I see people misunderstand often.

    The identity provider basically only makes a proof that “you are you” : you give it your login credentials and it gives you a kind of token that authenticates (proves your identity) to other services. like, i’m on discuss.tchncs.de, but i can post to lemmy.world. this is because the discuss.tchncs.de server says to lemmy.world that i indeed have this account on this server. so they prove my identity in a way.

    So, I might be wrong here, but I interpret you as saying basically that you’re authoring posts on lemmy.world with your account provided by discuss.tchncs.de. That’s not really how this works. Your data hoster is the instance you have your account on, not the one the community is on. Your instance just shares the posts you make on it with the community, but all it receives is a copy. The canonical version is on your instance, discuss.tchncs.de.

    Again, data hoster and identity provider are currently the same thing. The fediverse is just a bunch of interconnected silos, you do things within your own instance and then other instances receive a copy of the thing you did. You never author things directly on another instance than your own.

    The token stuff there sounds like SSO (single sign on), but it doesn’t look like either of those instances support that. So not sure what you were referring to there. The public key to verify the signature maybe? That’s more meant to ensure that the object is actually authored by you iirc though.