@ada I used to mostly go with GPL, nowadays mostly EUPL for new projects, I like the compatibility clause cause it lets people reuse the code in projects with many similar foss licenses
Posts
-
Ah yes, the 3 genders:- exclusively uses permissive licenses - "has licensing something under GPL ever helped my friends?"- exclusively uses copyleft licenses - "if companies use it they better contribute back"- exclusively uses anticapitalist and simi... -
Ah yes, the 3 genders:- exclusively uses permissive licenses - "has licensing something under GPL ever helped my friends?"- exclusively uses copyleft licenses - "if companies use it they better contribute back"- exclusively uses anticapitalist and simi...I can't tell you which of these is right but I'm in the second boat
-
Ah yes, the 3 genders:- exclusively uses permissive licenses - "has licensing something under GPL ever helped my friends?"- exclusively uses copyleft licenses - "if companies use it they better contribute back"- exclusively uses anticapitalist and simi...Ah yes, the 3 genders:
- exclusively uses permissive licenses - "has licensing something under GPL ever helped my friends?"
- exclusively uses copyleft licenses - "if companies use it they better contribute back"
- exclusively uses anticapitalist and similar licenses - "fuck companies" -
Towards Federated Key TransparencyI say “limited” because it will only not support editing or deleting messages provided by another instance. It will only append data. [...] contains an Asymmetric Public Key, the user and instance that hosts it, and other metadata
that's enough data to count as PII under GDPR, you'd need to handle the right to be forgotten somehow
see keys.openpgp.org/about for a pgp keyserver that solved this by separating the identity data from the public key data and letting you delete the former -
If your site or blog runs on WordPress, people can follow it through RSS. Some examples of feed URLs:@talksina @homegrown Atom is significantly better than RSS and supported by basically all readers BTW (it's also properly standardized in an RFC4287)