ssimono

Reminds me of something similar I made a few years ago: https://github.com/ssimono/hexliterate It still works, that's a multiplayer real-time game

+1 on this. I use to consider those Linux evenings as a waste of time. But with every bit of NixOS tracked within git with some history and context, I now think of it like an investment for the next 50 years, which has way more chances to pay back

This is a hack I put together to simulate a feature where you could exclude some lines from being tracked with git, based on some patterns

There is a /raw endpoint to make it easy. On a released pok you can do curl <pok-url>/raw | sha256sum

Very good point! We thought about it and should implement it rather soon

Hey, I am the main dev behind this. The poks are currently not encrypted because there is no way to fundamentally allow a decryption later without someone having the key the whole time, which defeats the purpose. But we're looking into potential with applications stored in Ethereum or something! In the meantime we are committed to not use, and not even look at the content before their release

Thanks. Some people sometimes post hash of a prediction on Twitter https://twitter.com/patio11/status/1241551327743770624. If some "influencers" can start using Futuure that can be a good driver

Web applications have lots of essential parts on the server-side even if they do client-side rendering. And each paying user is logged in when using it, so the company can accept/deny requests depending on the user.

Proprietary desktop applications are usually downloaded after a payment, and then the full software is available locally. By hacking the security parts of it one can then have a totally free version and distribute it. That's why it is easier to pirate.

I am building Freecount (https://github.com/ssimono/freecount) a little progressive web app to track expenses in a common pool (like a trip, a shared housing etc). It is meant to be entirely free and open source, without server to deploy, app to install nor account to create

Another reason would be to justify differences in salaries. When some people are getting paid 30K more than some of their colleagues, a difference in title makes it somehow acceptable, or at least moves the debates to "should X be a senior" instead of "should X be paid that amount".

This is not ideal and should not be necessary, as in a perfect world pay bands should come from factual skills, performance and responsibility.

But I still find it better than having no title distinction while still having completely opaque salary gaps.

Oh it looks like this is exactly what I am looking for, thanks a lot