Programming

I work with governmental organisations and heavy industry. spotty internet, data privacy, changing laws, cleanroom areas, IT audits, travel to places with less savoury governments, telemetry that shouldn't be stored but is due to some flag someone forgot, takeover of the server, ulterior motives, you name it. needing a network connection means it has to be assumed compromised, and short of letting my IT dept host its own version, you can't convince me otherwise. I need to be able to 1) sync data only when on a verified safe network, and 2) trust the server that data goes to and from.

when it comes to what something could be used for... are you doing market research, or basic research? building a tool usually means you have a need for that tool. If you're trying to market something, do a proper test with a control group. just going "i made a thing, i don't know what it's good for" isn't going to pull in crowds, especially if there is a barrier such as account creation to actually use the thing.

Edit:

also, your page is missing basic accessibility features. all the links are s, not s, so they're not properly picked up.