I almost was hit by a Cruise car turning left at a busy intersection while I was in the crosswalk (with a walk signal). When I see a car attempting to turn left, I slow down or stop to make sure it sees me. Cruise car just kept going and got super close to hitting me. But there’s no way to complain or collect stats on it.
> And without fail, people will howl ITS NOT OPEN SOURCE.
Right, they mean that, as a user, you are not free to use the software for any purpose, nor are you free to change it in any way. Whether open source is morally/ethically better is separate from its definition.
It's fine for you to say you only want to support non-commercial use, but if you call it "Open Source" it dilutes the definition.
Why/how is your app better than setting native screen time limits in iOS? Doesn’t that accomplish the same thing (except tapping numbers rather than seeing a quote).
(All that said, glad you’re poking at this issue!)
a few ways! but the most succinct answer is that with clearspace, no learned behavior path can become a compulsive habit for quickly getting more scrolling.
every configuration of screen time limits we've tried has ended with us learning the quickest behavioral path to more scrolling (ie: quickly tapping "5 more minutes", entering passcode, etc).
1. we hit you with friction every time you enter an app you want to moderate your engagement with. with screen time limits, as long as you're under your budget, you'll get through no problem. in time this means you learn that early in the day is the best time to use social apps. we think this is a second order failure.
2. we let you stack your progress over time with your streak, which seems to be a far better behavioral motivator for staying in line with your goals.
3. we report usage for the apps you actually care about moderating. (I basically ignore my native screen time report, because "being up 25% this week" might mean I went on a long drive and was using maps to navigate, or that I doom-scrolled in bed until 3am.) we try to report data you actually care about (there's a ton we still need to do on this front, but we're getting better at it)
You mentioned to lukko above (lungy.app) that you might be interested in collabing, and then above you mention streaks... wanted to make sure you knew that with apps you can "call" other apps via shortcuts/urls and even get return data. At some point I'm hoping to work with a streaks app (rather than build it myself) etc etc.
The front page ideally would only have links to upvote, read the story, and read the comments for each story, at least on mobile. Having big targets for sausage fingers on small touch screens would be even better.
It's too easy to tap the wrong link and end up flagging, hiding, or searching for stories from that domain, as you point out.
Hi! We provide an on-prem version (as part of our enterprise tier); but better yet the SaaS solution itself is hybrid- meaning we provide a microservice for authorization for you (aka the PDP), and it answers all the queries locally from memory cache - which is great for security, but also latency (sub 10ms as a sidecar), and availability.
Updates are done through OPAL (https://opal.ac) - which has a a zero trust architecture (it sends instructions on how to get the data instead of the data itself) based on topics scoped with security tokens.
How is this possible? Cows must feed and they eat plants (inefficiently too)