🎓 Dr. Freemo 🇳🇱 @freemo@social.cleverlibre.org

This is my family with my cryptocurrency trading bot, lol

Mastodon is 20x more addictive than Twitter for me. How do you all handle it???

@freemo
If you are getting traction and are politically savvy, you might reach out to American politicians and discuss the anti-competitive angle of it. They're under a lot of political pressure right now
@chris

Something which I haven't heard about, but which I think is a good idea, is to license free software projects under a strong copyleft license, but add a clause so that it becomes public domain after X years (my preference is 10).

This would have a few advantages. One advantage is that it would be more consistent with my desire to reduce copyright term lengths.

Another advantage is that it would make re-licensing easier, while still being difficult enough that it couldn't be done on a whim. In the worst case everyone could dual-license every new contribution under both the old and new licenses for 10 years, and then 10 years later it would be under the new license. This is just the worst case, though. If you got every contributor for the past Y years to agree to re-license, then you'd only need to wait for 10 minus Y years.

A broad consensus would still be required to re-license the project, so it would still generally be safe from malicious re-licensing, but it would also be easier to fix licensing mistakes (for example, if the project was GPLv2 but the community wanted to switch to GPLv2+). It would also become less risky to experiment with different licenses, because it would be easier to correct the mistake if it became clear it *was* a mistake in the future.

This greater allowance for experimentation would also be useful, I think, because there exist interesting new copyleft licenses which might be a good idea or which might not, like the Parity license.

Technically I've already applied this idea today in some small things I uploaded to github, but they're not projects used by anyone else, so I'm not sure they really count.

Anyway, if anyone is curious, here's a link to the contents of a "LICENSE.txt" file applying this idea, for a project whose last contribution date was in 2019. The idea is that you'd bump up the year in this file each year, so older versions would gradually enter the public domain 10 years after their release. Note that I'm not a lawyer, so I can't actually vouch for this being legally valid.

https://raw.githubusercontent.com/ml-2/sslib/master/LICENSE.txt

A while ago I was inspired to try my hand at a more "explorable" periodic table online, in a new (to me) coding framework (sveltejs). I was slowed down by my embarrassing ignorance of chemistry. Any chemists have opinions on how to make a periodic table fun to explore? I was dreaming about drag and drop interactions...

https://mmlindeboom-periodic-table-svelte.glitch.me/

@freemo I thought it was really cool to find your post through Reddit. Thanks for bringing attention to this.

@freemo

Google is taking down some of the Fediverse clients (seems like the ones that dont ban Gab)

a fediverse post about it by @freemo is currently the most discussed thing on the front page of hacker news rn

https://hn.svelte.dev/item/24304275

#mastodon #hn #censorship

Google is trying to ban the entire fediverse by @NEETzsche; also cites @freemo, @Gargron, and @tateisu https://iddqd.press/2020/08/28/google-is-trying-to-ban-the-entire-fediverse.html

@freemo Excellent. Lobster will be sure to advance pro-HAM radio agenda, by requiring all operators to have hams available at all times.

@freemo Listen, Lobster is very, very, very, very, VERY, very, VERY important. You should vote for Lobster in 2020.

Remember what Lobster say about Hometown: Avoid Philadelpha.

#Lobster2020

@zleap @freemo on the plus side, I have never heard of Mastodon until today, so the article is bringing in new people