I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

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

help-circle





  • While I like it conceptually, the two times I tried to install it I felt it was far too opinionated for me to get it to work correctly, like other software “bundles” of its kind that want to take control of the entire process of setting up ports, networking, storage, certificates etc…, instead of just hanging down from stuff that I have already prepared for it (like my own domain with my own cert).

    Like, as a piece of software it’s something I’d absolutely use… if someone else sets everything up for me.


  • Here’s two things:

    1. You can not steal an idea. (aka “just because you had an idea doesn’t mean it’s yours”)
    2. You can not steal profits that were never had or intended to be had in the first place (aka: piracy vs “abandonware”)

    Considering that:

    It’s open source, but you can’t redistribute binaries of it you can only compile it for your own personal needs and you can’t commercially use it for free

    Then it’s not Open Source. So, which is it?

    OK, in that case, let’s say I reimplement Fraunhoffer’s FDK-AAC. It’s open source, but you can’t redistribute binaries of it, you can only compile it for your own personal needs and you can’t commercially use it for free.

    The only midly-relevant question here becomes: did you use their source code to implement yours, or did you use public knowledge of the algorith etc (up to and including “white boarding”) to reimplement it? If the former, if the software is actually Open Source at best I could see a case for misrepresentation, but not for theft, because the source code is made available openly, you are not breaking that (that’s what “steal” is).

    Second, if your implementation is better than theirs, including eg.: because of having a better license, then the rules of the market apply: the better product wins (that’s the same argument corps would use to try and break you if the case went the other way around, so it’s only fair you can also use that; at least, law’s supposed to be blind to order-of-parties). You are also not stealing profits because, besides the fact that potential profits by definition can not be stolen, you are also aiming at a different market eg.: people who wouldn’t have bought Fraunhoffer’s in the first place because of the license etc. If you are selling cheese sandwiches, you can not sue “stolen profits” from someone who is selling bacon sandwiches just because their clients asked you for bacon sandwiches and you said no.









  • I hear this all the time, but to be fair it wasn’t even them. It was Google putting up “framework defenses” (with RCS, and now they’re doing the same with the native Android phone dialer).

    Where Signal dropped the ball was their marketing: it was as easy as picking up their old app (TextSecure) so that they didn’t have to worry about feature clash with current Signal, then rebrand this old app as “Signal SMS” and boom, instant adoption because it’d be fairly trivial to “migrate”. And they get to steal the thunder from the apps that slowed down development.