We _could_ run something like https://github.com/sstraust/automagic-dark-mode , but I decided against it, because it makes for a confusing user experience. idk -- i wanted to support dark mode, but it's hard to make these tradeoffs correctly.
i have a guess at what's happening, but it would be a little bit of an unusual/edge case -- i made a backend change and it should maybe work now in this case?
if not i will crawl into the deep cave for a longer debugging session
> I found the algorithm nudged me toward emptier, clickbatier content.
I appreciate the effort as RSS is the best way to read a lot of sources but is login/signup really needed?
you can click any of the demo boxes on the home page to use it without signing up
if you want to save your preferences though, we _do_ need you to sign up, so that we can save who you follow, etc. to a database.
e.g. here is a direct link to the top headlines: https://sprinklz.io/demo/headlineNews
glad you're feeling this way too!
It should be: Demos: (no login required) Some may think it redundant. Not me.
Dark Reader on FF mobile can't redraw for some reason. Too bright white !
yes -- Sprinklz supports custom themes, and there's no good way to support the combination of custom themes + dark mode.
See: https://sprinklz.io/demo/editThemes for an example. (on nonmobile if you want to see the on-screen editor)
We _could_ run something like https://github.com/sstraust/automagic-dark-mode , but I decided against it, because it makes for a confusing user experience. idk -- i wanted to support dark mode, but it's hard to make these tradeoffs correctly.
I get a "failed to load feed with name home" on first load. Recurs on hard refresh
hm -- are you doing anything spicy with your browser?
i tried signup on chrome/firefox/safari + demos and i can't manage to repro.
im assuming this is after submitting signup?
This is without logging in, on: https://sprinklz.io/feed/home. Occurs in incognito too. Nothing blocked on the network so seems client side.
i have a guess at what's happening, but it would be a little bit of an unusual/edge case -- i made a backend change and it should maybe work now in this case?
if not i will crawl into the deep cave for a longer debugging session