MagLit VS ultra-weather

On the privacy front, we're never going to compromise the user data, never going to sell it, never going to share it with anybody else. We'll be making writedown self-hostable as well.

On the security front, we're using firebase firestore as the database. So at rest, it's well encrypted.

We're thinking of introducing some sort of encryption via passwords (kinda how I already am doing it on https://maglit.me). E2EE would be quite difficult and would affect the usability.

maglit.me, can use custom links and is privacy respecting

jesus christ use https://maglit.me/ so your link will not be so fucking fat.

There are many services that offer such a functionality. Just search for "password protected link shortener". One example would be https://maglit.me/ by u/NayamAmarshe (I haven't tried it, I only read this post). However if you care for privacy (kind of the point of the whole post) and you have a web server you might want to selfhost the service (has a lot of other advantages as well, link all the easy to remember keywords are still available), which gives you even more options: like again MagLit or YOURLS with the Password Protection Plugin. (disclaimer: I am using a self hosted YOURLS instance myself, but have not used this plugin yet).

I tried sharing a couple of my web apps:

- HN the way I want to read it: https://hw.leftium.com/

- Source code: https://github.com/Leftium/hckrweb

- Weather forecast compared to last two days' weather: https://github.com/Leftium/ultra-weather#readme

One of the reasons I built https://uw.leftium.com/ was so I could see the previous two days' weather.

It uses the DarkSky API, but also supports other weather API's: https://github.com/Leftium/ultra-weather#readme

UltraWeather uses the openweather geocoding API[1]:

https://openweathermap.org/api/geocoding-api

Pretty generous free tier, and paid options seem pretty reasonable.

[1]: https://github.com/Leftium/ultra-weather#specify-a-location