Jump to content
You must now use your email address to sign in [click for more info] ×

LondonSquirrel

Members
  • Posts

    1,487
  • Joined

  • Last visited

Posts posted by LondonSquirrel

  1. 6 minutes ago, MikeW said:

    The point of this thread is Serif is not staying within the law. By Serif even making a copy of the cloud font, they are in violation of the Adobe cloud font license. I would argue even giving the user a choice to make a package using (at least) Adobe cloud fonts makes Serif complicit.

    So what about any photo editing app which opens a copyrighted photo? If the copyright information is embedded in the photo, why am I allowed to open it at all?

  2. 1 minute ago, Old Bruce said:

    Back in the bad old days it was simple in that copying a font meant a good chance of lead poisoning.

    I had an Adana when I was 12. I felt like I was king of the world when I started printing things. An early mistake of mine which I still remember: setting the word 'services' as 'sevices'. It taught me a hard lesson after I had printed about 200 of these...

  3. 21 hours ago, R C-R said:

    Just to be clear about this, are you saying that wherever an EULA is "basically" (whatever that means) considered part of a contract, if you are not explicitly a party to it, then you personally have no legal obligation to abide by its terms?

    An EULA is a contract. This is different to copyright, which is covered by imposed laws. 

    If you are not party to a contract you are not obliged to obey any part of it. Think about it: your neighbour buys a computer and clicks the 'I agree' button. What affect does that have on you? None whatsoever.

  4. 21 hours ago, Old Bruce said:

    Then you cannot use the software. To use the software you have to agree to the EULA.

    That is very debatable to say the least. As in the examples I have given, in a corporate environment I have no idea if the software is licensed or not, nor what that license is, or if somebody gives me a computer already set up for use. They may well have broken the EULA as they presumably clicked the 'I agree' button, but I did not.

  5. 1 minute ago, Old Bruce said:

    Okay, valid point, apples and oranges.... The EULA is applicable whether or not you have actually read it.

    In Europe (and the UK still), EULAs are basically considered part of a contract. If you have not agreed to that contract then you are not a party to it. If somebody gives me a laptop already set up, and I have no EULA is presented to me when I use it, I am not the one who clicked the 'I agree' button, and I am not a party to the other person's contract. It could be the person who clicked the 'I agree' button is in breach of the EULA, but I am not as I was never a party to it.

    But once again, don't confuse EULAs with copyright. The copyright still exists.

  6. 6 minutes ago, Old Bruce said:

    We are getting into the "Ignorance of the law is no defence." I have not read the copyright notice on most of the books I've read, yet I know that I cannot copy the words and expect to not wind up in court with, oh lets say... Anne Tyler suing at me.

    Do not confuse copyright with EULAs. They are completely different things. An EULA my or may not include permission to copy. E.g. SIL fonts (https://software.sil.org/scheherazade/). Snippet: 'This font software is free to use, modify and redistribute according to the terms of the SIL Open Font License.'

  7. 2 minutes ago, LibreTraining said:

    The whole concept of rented fonts is just as bad as rented software.

    Agreed. I have no idea what the terms are if you create a PDF using a rented font, then end your subscription, now pass the PDF to somebody else with the font embedded. Perhaps that is included in the licence.

    This is just about companies (in this case Adobe) keeping its hooks in its users. Remember the not-yet resolved story of the Pantone swatches being removed from CC? I think that Pantone thinks it invented the whole concept of colour.

    In this case of the Adobe cloud fonts, we're talking about a subset of Affinity users - those with Affinity and with CC. I wonder what the percentage of Affinity users that is.

  8. 4 minutes ago, MikeW said:

    The discussion is about one specific act of copying files that breaks the user agreement.

    Anyone could do that anyway. Which is why I am saying again that some people are getting on their high horses about it. 

    5 minutes ago, MikeW said:

    I feel, believe, that if the user really wants to copy those restricted fonts they are free to do so all by themselves. Serif doesn't need to enable them to do so.

    Exactly my point. It's just another way of doing it, so why are you complaining about this instead of the far easier method of just copying the files using any other tool?

  9. 6 minutes ago, MikeW said:

    If I had been in charge of the decision to include cloud fonts or not to ever include them, we wouldn't be having this discussion. If/when a user complained, Serif would/could simply state that to do so violates the agreement one makes when using cloud fonts. 

    And if you had been at Apple or Microsoft or wherever, you could have disabled all file copying. Because the ability to copy is what you are talking about here.

  10. 27 minutes ago, Lagarto said:

    But IMO accessing the hidden locations requires specifically written hard coded paths

    I disagree with that argument. A path is just a path. The fact that it might be 'hidden' is neither here nor there. The paths to all kinds of things can be considered 'hidden', but merely accessing them is not a problem in itself.

    The other side of that coin is that an app can install files in a place which it knows about but which I cannot find. To me, as a user, and having dealt with security issues over the years, is 100% unacceptable. I should know about every single file which an app is installing on my system. As mentioned, I've dealt with this sort of thing from a security aspect - files with unprintable characters in names, files with the 'hidden' flag set on *BSD UNIX (this flag is available in macOS too - man 1 chflags), and other methods to attempt to hide files which should not be there (e.g. creating files, opening a file handle to it, then deleting the file), and so on. These are all old tricks amongst many others. The point is, if a file is trying to be hidden, it makes me look for it even more. 

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.