twentydradt @twentydradt@qoto.org
#Mynewt Main Event Loop is extremely Time-Sensitive for handling #NimBLE #BluetoothLE messages... Don't insert anything here! (Especially Semihosting Logging)
https://github.com/lupyuen/pinetime-rust-mynewt/blob/timesync/rust/app/src/lib.rs
Arm Announces Cortex-R82: First 64-bit Real Time Processor
https://www.anandtech.com/show/16056/arm-announces-cortexr82-first-64bit-real-time-processor
Go2 examples in the official repository #golang
https://github.com/golang/go/tree/dev.go2go/src/cmd/go2go/testdata/go2path/src
software licensing long post
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
Earth’s nearest supergiant is cooling down at the end of its life
Scientists now believe the dimming of Betelgeuse was caused by a giant sunspot ...
On Tuesday, we're hosting a live stream that'll explore gaming’s impact on the non-gaming world, in areas as widespread as microbiology and fashion. Register now to receive updates about the broadcast: https://bit.ly/3gEx2RN
https://twitter.com/techreview/status/1300386084623388673 #Tech #MIT
--
Full-List of bots: https://joejoe.github.io/mastodon
