• 1 Post
  • 64 Comments
Joined 4 years ago
cake
Cake day: February 15th, 2021

help-circle
  • You share public keys when registering the passkey on a third party service, but for the portability of the keys to other password managers (what the article is about) the private ones do need to be transferred (that’s the whole point of making them portable).

    I think the phishing concerns are about attackers using this new portability feature to get a user (via phishing / social engineering) to export/move their passkeys to the attacker’s store. The point is that portability shouldn’t be so user-friendly / transparent that it becomes exploitable.

    That said, I don’t know if this new protocol makes things THAT easy to port (probably not?).


  • Yeah, it protects Jimmy from having to unconditionally contribute to society & its many organizations.

    It allows Jimmy to set conditions and control who can use it and who cannot. For example, he can ally with one particular big corpo (or even start building one himself) so they can hold that thing hostage and require agreements/fees for the use of that thing for a long long time.

    So now, instead of all people, including big (and small) corpos, having free access to the idea, only the friends of Jimmy will.

    The reality is that if it wasn’t for Jimmy, it’s likely that Tommy would have invented it himself anyway at some point (and even improved on it!). But now Tommy can’t work on the thing, cos Jimmy doesn’t wanna be his friend.

    So not only does it protect Jimmy from having to contribute to society without conditions, it also protects society from improving over what Jimmy decided to allow (some) people access to. No competition against Jimmy allowed! :D

    Even without patents, if the invention is useful I doubt the inventor will have problems making money. It would be one hell of a thing to have in their portfolio / CV. Many corpos are likely to want Jimmy in their workforce. Of course, he might not become filthy rich… but did Jimmy really deserve to be that much more richer than Tommy?


  • There are many games that had that mechanic before Arceus.

    In particular, Craftopia (which is from the same developers of Palworld) had capsule devices that you can throw to enemies in a “virtual space” while characters “engage in combat” before Arceus was a thing.

    Just because they wrote a patent does not make it enforceable… patents don’t really mean anything until they are actually tested in court so they are just tools to try and scare people away whenever a company wants to bully with the prospect of a lawsuit.

    I feel that Palworld is likely to win this, this actually is an idiotic move from Nintendo and a win for Palworld… now they will get more publicity, perhaps another spike in sales, and they are finally given the opportunity to prove how they are in the right, so they can shut up all the naysayers who complained about it. I’m hoping all the paranoic empty claims about “blatant asset theft” will be settled once and for all.


  • Yes, that’s why im saying that this kind of problem isn’t something particular about this project.

    In fact I’m not sure if it’s the case that the builds aren’t reproducible/verifiable for these binaries in ventoy. And if they aren’t, then I think it’s in the upstream projects where it should be fixed.

    Of course ventoy should try to provide traceability for the specific versions they are using, but in principle I don’t think it should be a problem to rely on those binaries if they are verifiable… just the same way as we rely on binaries for many dynamic libraries in a lot of distributions. After all, Ventoy is closer to being an OS/distribution than a particular program.


  • Yeah, it definitely is more appealing from a marketing perspective.

    I do understand why some projects might wanna use the term, it’s to their advantage to be associated with “open source” even if the source code itself has a proprietary license.

    The problem is that then it makes it harder / more confusing to check for actually openly licensed code, since then it’s not clear what term to use. Already “free software” can be confused with “free as in free beer”.


  • That discussion concluded essentially the same thing I said: that both the OSI and the FSF have essentially the same conditions and that “merely having the source available is not enough to meet what the OSD defines as open source” (sic).

    Don’t police perfectly innocent and common use of language please.

    Using “open source” for all kinds of source, regardless of how restrictive its license is, is definitely not a common use of the term.

    People aren’t gonna start using “open source” like that just because a few people find it more convenient for the marketing of their projects. To me it sounds like they are the ones policing to push for a particular language standard against what people commonly use, which is what makes language prescriptive, instead of descriptive.



  • According to the definition from the Open Source Initiative, “open source” also requires free redistribution. See the first point (emphasis mine).

    1. Free Redistribution

    The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.

    It also requires freedom to distribute modifications:

    1. Derived Works

    The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.

    CC-BY-NC-ND is not “open source” (both due to the NC and the ND), it’s more of a “source available” type of license (when applied to source code). The difference between “free software” and “open source” is more ideological than anything else, they both define the same freedoms, just with different ideological objectives / goals.



  • That’s ok if we are talking about malware publicly shown in the published source code… but there’s also the possibility of a private source-code patch with malware that it’s secretly being applied when building the binaries for distribution. Having clean source code in the repo is not a guarantee that the source code is the same that was used to produce the binaries.

    This is why it’s important for builds to be reproducible, any third party should be able to build their own binary from clean source code and be able to obtain the exact same binary with the same hash. If the hashes match, then you have a proof of the binary being clean. You have this same problem with every single binary distribution, even the ones that don’t include pre-compiled binaries in their repo.




  • My worry is that the other 20% might actually come from other forms of partnerships and integrations not unlike what they probably had in mind with this, and that dropping Google might actually make them more dependent on seeking this kind of initiatives, not less.

    I don’t know how many people you actually need to maintain a browser. But if it’s actually possible to do it without any kind of money from any of those sources in a way that can be sustained, then it would make more sense to make a fork (or alternative, like Ladybird) and just use that.

    Like I said, I think it’s too late for Mozilla to shift course, I don’t expect they’ll ever do that. At least not until they are forced by a competing project if it happens to become successful (or a similar huge wake up call that leaves them no alternative).



  • Is “intent” what makes all the difference? I think doing something bad unintentionally does not make it good, right?

    Otherwise, all I need to do something bad is have no bad intentions. I’m sure you can find good intentions for almost any action, but generally, the end does not justify the means.

    I’m not saying that those who act unintentionally should be given the same kind of punishment as those who do it with premeditation… what I’m saying is that if something is bad we should try to prevent it in the same level, as opposed to simply allowing it or sometimes even encourage it. And this can be done in the same way regardless of what tools are used. I think we just need to define more clearly what separates “bad” from “good” specifically based on the action taken (as opposed to the tools the actor used).


  • I think that’s the difference right there.

    One is up for debate, the other one is already heavily regulated currently. Libraries are generally required to have consent if they are making straight copies of copyrighted works. Whether we like it or not.

    What AI does is not really a straight up copy, which is why it’s fuzzy, and much harder to regulate without stepping in our own toes, specially as tech advances and the difference between a human reading something and a machine doing it becomes harder and harder to detect.


  • Yes, I don’t think it’s just about the execution of Win32 code, but also the possibility of MS using marketing techniques and dirty manipulation methods to give themselves advantages within the Windows platform to sway the general public to their store in a similar manner as how they push their browser, their MS Teams communication platform, their One Drive Cloud Storage, their search engine, their data-collection tech, their assistant, etc.


  • Content curated by “the core geeks and nerds” might appeal to “geeks and nerds”, not to those consumers.

    They want “consumer” content. And if one day they get tired of it then I doubt any amount of “steak” would have stopped them leaving anyway, since that was never what they were looking for. It’s not like reddit has to be the only place they visit in the internet, nor is the internet their only source of consumption. Just because you go to a snack bar does not mean that’s the only place you go for meals.



  • Which is why you should only care about the personal opinion of those people when it actually relates to that reliability.

    I don’t care whether Linus Torvalds likes disrespecting whichever company or people he might want to give the middle finger to, or throw rants in the mailing list or mastodon to attack any particular individual, so long as he continues doing a good job maintaining the kernel and accepting contributions from those same people when they provide quality code, regardless of whatever feelings he might have about whatever opinions they might hold.

    You rely on the performance of the software, the clarity of the docs, the efficiency of their bug tracking… but the opinions of the people running those things don’t matter so long as they keep being reliable.