I think there's a lot of opportunity in this space with AI. It'd be interesting if you could take some metadata into account when organizing notes. For example, you might be able to guess when someone is home when they're accessing the site from a frequent IP address. This example is top of mind for me, as I just completed a move this weekend. I wish I had been better organized taking notes as I set up different home systems in the past, as it's now been a few years and I wish I had notes I could go look back on. Being able to filter my apple notes app by geolocation would be awesome.
I love the idea of not having to worry about tags to keep notes organized. Nice work!
Thanks for looking! I'm actually surprised Apple hasn't done this yet. The organizing and search stuff they do with photos, metadata, and image recognition is really great. So I'm sure they will.
As a pwa, it'd be a bit annoying since it'll have to ask you every time to geolocate. At least, I think it's the same as mic access.
DNS Server 2 = ISP DNS Service, OpenDNS, your router whatever
when pi-hole blocks the ad's DNS query, macOS will treat that as a DNS failure and use DNS Server 2 as a fallback. Resulting in the ad being shown.
Doing (A) was my first attempt and at least using a Ubiquiti router, if Pi-hole blocked a DNS query it would always fallback to the secondary DNS server. In my environment, the only way I was able to get pi-hole to work consistently was to set the pi-hole server as the only DNS server in the DHCP server.
> when pi-hole blocks the ad's DNS query, macOS will treat that as a DNS failure and use DNS Server 2 as a fallback. Resulting in the ad being shown.
My experience with OSX and Pi-Hole doesn't match your experience. There's a difference between appearing to be in a failure mode (i.e. timing out) and returning blocked (null/0.0.0.0) results.
I set this up a few years ago and now that time has passed I'm not confident enough to claim what exactly led me to that conclusion. I never got around to setting up a second pi-hole server which is what led me to click on the article above. 3 years in and I've never had a blip in service so I just haven't prioritized it.
I did go and test this now, and agree with you. On macOS I set my primary DNS to pi-hole and secondary to 8.8.8.8. running dig on api.segment.io (blocked on pi-hole by default), it resolved to 0.0.0.0 via pi-hole and did not try 8.8.8.8 on any attempt. So my earlier comment is incorrect above and setting a secondary DNS server as a back-up may work.
This is a great write up! I’m curious, did any enterprise requirements influence this decision? Specifically supporting SCIM for synchronizing users with something like okta?
Author here, and yep! We eventually want to offer those kinds of enterprise features (SCIM, syncing group membership from Okta/other IdPs), so I kept that in mind throughout the process.
While I haven't gone too deep on that yet, I was thinking we'd take inspiration from how GitHub maps IdP groups to native GitHub teams. So first step here would be adding user groups/teams natively in the product.
I love the idea of not having to worry about tags to keep notes organized. Nice work!