this post was submitted on 05 Feb 2024
138 points (96.6% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54565 readers
486 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 1 year ago
MODERATORS
138
submitted 9 months ago* (last edited 9 months ago) by Deckweiss@lemmy.world to c/piracy@lemmy.dbzer0.com
 

I have bought a font with a really shitty license agreement and I have a couple of questions.

  1. How can I best share the font with the community? (I am afraid of metadata in the font files, which may be tied to my payment account etc. - I had to register and log in to download the ttf files)

  2. How can I remove the DSIG and other metadata from the ttf file while keeping it usable?

  3. Are they able to detect it if I use the font in a commercial product online by crawling my website and if yes, how could I prevent an automatic detection attempt?

To my (and possibly your) surprise, I didn't find any free downloads of the font online. Their license is tied to a personal account, you have to log into once a year to keep the license. As far as I understand they theoretically could use the DSIG to let the ttf files "expire", at least when used in software that verifies the signature. But I may be wrong, please let me know.

Thanks in advance and cheers-I mean ARR

you are viewing a single comment's thread
view the rest of the comments
[–] cuchilloc@lemmy.world 6 points 9 months ago (5 children)
[–] ThoGot@lemm.ee 3 points 9 months ago (1 children)
[–] remindme@mstdn.social 0 points 9 months ago

@ThoGot Ok, I will remind you on Monday Feb 19, 2024 at 10:53 PM PST.

load more comments (3 replies)