I’m the administrator of kbin.life, a general purpose/tech orientated kbin instance.

  • 0 Posts
  • 9 Comments
Joined 2 years ago
Cake day: June 29th, 2023
  • r00ty@kbin.lifetoFediverse@lemmy.world•Lemmy,Mbin, piefed, what even are those?
    6·
    2 days ago

    They send fake (non-existing) actor ids for votes to obfuscate the identity of the real user. It is “compliant”, but completely against the spirit of a public social network.

    There have been discussions about how to implement this before. But it has to be done in a way that is agreed by other threadiverse software. Unless they actually provide profiles for these fake actors there will be problems since some software will look up the profile info to cache it, even for likes…

    Personally I’m of the opinion of a standard header to mark a favourite message as a private one and use a random ID that the originating instance can use to validate the message as genuine. But, this needs to be adopted properly by all.

  • r00ty@kbin.lifetolinuxmemes@lemmy.world•Proprietary vs Open Source Backdoors
    27·
    3 days ago

    But this is the crucial thing. It wasn’t in the repository. It was in the tarball. It’s a very careful distinction because, people generally reviewed the repository and made the assumption that what’s there, is all that matters.

    The changes to the make process only being present in the tarball was actually quite an ingenius move. Because they knew that the process many distro maintainers use is to pull the tarball and work from that (likely with some automated scripting to make the package for their distro).

    This particular path will probably be harder to reproduce in the future. Larger projects I would expect have some verification process in place to ensure they match (and the backup of people independently doing the same).

    But it’s not to say there won’t in the future be some other method of attack the happens out of sight of the main repository and is missed by the existing processes.