I'm concerned about the HTTP requests that fire off every time I navigate to a new page. E.g. navigating to my "Thursday 10th Jan 2019" note triggers [1]. It even includes a cookie in the request. Not completely private, it would seem, as you're very clearly collecting metadata about my app usage habits, even though it's not strictly required for the app to function properly.
[1]: POST https://trys-tiny-tracking.now.sh/ {"type":"hit","url":"/2019/01/10/"}
EDIT: Looking through the src [2], it appears the site will respect the user's "do not track" browser preference [3], but that's not supported in all browsers
[2] https://github.com/trys/JournalBook/blob/master/src/utils/be...
[3] https://developer.mozilla.org/en-US/docs/Web/API/Navigator/d...
Fair point, this is the beginnings of a basic hit counter that I'm working on. As there's no server (it's CDN hosted on Netlify), there's no way to see if anyone's even using the site. It's waaaaay less intrusive that GA, or other tracking tools. It's simply picking up page views - ignoring IP and any identifiable information (cookies obvs. included). It also respects do not tracking indicators in your browser. Tiny Tracking will be open sourced in time.
In my mind, this completely contradicts "privacy centric" and "offline first", which to me are very important goals. Even though the notes in the app are only ever stored on my computer, and even though it's metadata being sent, I would rather offline and privacy focused apps not use my network at all. That's what I aspire to anyway when I write apps for sephware.com, and I wish everyone would do the same.
But re: zero analytics, aren't you curious how many people use the app at a minimum?