> [A]pps you install from F-Droid are signed by F-Droid rather than the developer.
Having recently gone through the F-Droid release process, I learned that this is not necessarily the case anymore.
F-Droid implements the reproducible builds concept. They re-build the developer's app, compare the resulting binary sans signature block, and if it matches they distribute the developer-signed binary instead of their re-built binary.
This is opt-in for developers so not all apps do it this way. I'd sure like to know how common this is, I wonder if there are any statistics.
I'm working on a Git GUI for myself, in which one of my top priorities is making it more understandable than Git's own UI.
I usually dislike animations. I used to disable transitions whereever possible, as they made the UIs feel sluggish. And I still do.
But working on the project made me for the first time really appreciate in practice how much amimations help with understanding. I paid a high price in complexity to add transitions whenever the state of the visual graph changes, and suddenly it was really obvious what was happening. Commits and whole branches were sliding into their new position, and I would go "a-ha! I see" instead of "wtf just happened, what am I looking at now?".
We already have a Push API specification that supports arbitrary push server URLs and self-hosting. It's called the Web Push API, although it can be used for mobile push as well.
This is a day later now, but for posterity I'll add that thanks to this thread I learned that there is a concept of "OSI approved licenses"[1], and that those licenses include MIT No Attribution License (MIT-0), and that MIT-0 is also a supported license in the GitHub UI.
It is likely I will be moving from Unlicense to MIT-0 in the future.
Actually I read through your links, and they seem to imply, that there does not exist (can not exist?) a license that you could use if you want to release your code to the public domain. That's a bummer if so.
I stand corrected then. I had heard a similar comparison that you should prefer Unlicense over WTFPL, but I had not heard it is impossible to dedicate works to the public domain. What a weird world.
If I want to use Unlicense, can I dual license as MIT and Unlicense?
I know most of these sort of licenses are just for fun, but on a serious note, if you don't care about licenses, and you don't care what people do with your code, I would recommend you use The Unlicense, instead of one that sounds funny.
The Unlicense is almost like MIT License but without any burden on those using your code.
On the other hand it offers you the same (perhaps handwavy) protections from liability as MIT License does.
If you're familiar with Creative Commons, it is similar to a CC0 license, but for code.
Basically it's a legitimate way of saying "I don't care about licenses, stop bothering me, do whatever".
If you use GitHub, then Unlicense is one of the choices you can select when setting up a repository.
I needed an online card sort tool for another hobby project, and I just couldn't find one that fit my needs, so I built https://github.com/indigane/cardsort
One requirement I had if I were to build it myself was that it would be maintenance-free and still work years after I have forgotten about it, so having a server was a no-go.
In case someone reads this in search of another tool, I did a search again, and found one I had missed, that actually has a usable free tier as of writing https://uxmetrics.com
Having recently gone through the F-Droid release process, I learned that this is not necessarily the case anymore.
F-Droid implements the reproducible builds concept. They re-build the developer's app, compare the resulting binary sans signature block, and if it matches they distribute the developer-signed binary instead of their re-built binary.
This is opt-in for developers so not all apps do it this way. I'd sure like to know how common this is, I wonder if there are any statistics.