Think of it like memory hierarchies. Bookmarks are long term storage, tabs are registers. Tab groups fall somewhere in the middle, easy to reengage with and easy to put out of focus.
18 karma · joined February 4, 2019
In the inescapable hell of n+1 competing standards.
If your code is stateful the typestate pattern is particularly easy to write in Rust - http://cliffle.com/blog/rust-typestate/
I've heard of this concept but a search for "mark-and-release per-frame allocation buffer" returned this thread. Is there something else I could search?
I've had a couple false starts on doing a full write up answering this question but the quick answer is that it's not actually time consuming and that doing the puzzle feels like the easiest way to get to the page.
A lot of procrastination blocking apps take an abstinence based approach which predictably leads to just disabling them. Another approach - the approach my extension takes - is attacking the instant gratification that you can get to through unconscious action.
The unlock puzzle takes maybe 5-15 seconds to complete, I find that time switch of mental state is enough to cause a moment of pause and consideration for whether I want to continue browsing.
As you mentioned a bypass is necessary and I added that in the extensions option page. I find that since the puzzles themselves aren't actually hard I usually feel like it's easier to do them then navigate away from the page and back.
I think the important thing to note is this isn't intended to stop you from procrastinating when you want to procrastinate. The intent is to help you recognize when you're procrastinating unconsciously.
The idea was largely inspired by this xkcd blag post - https://blog.xkcd.com/2011/02/18/distraction-affliction-corr.... One thing I took out it was the idea that doing this action is part of a contract with myself that I don't have to feel bad about browsing as long as I do this step. That's not encoded into the extension and I'm not sure how important it is for how successful it has been for me.
It's undocumented but it wouldn't be hard to add. Essentially you blacklist a domain in the 3 dot menu (toolbar icon on desktop). Blacklisted sites will show a word and key-value pairs of letters and numbers, you have to add up the values for each letter in the word to unlock the page. You can change the word length in the options page, also in options you can set the extension to sleep for 5, 15, and 30 minutes when you want to disable it without having to later re-enable it.
> Fennec Fox for mobile, what happened to that?
That's just the code name for Firefox for Android. Ime it's fairly pleasant to use since flick scrolling was improved, and browser plugins on mobile are the selling feature.
> FLASH TO JS CONVERTER
Definitely sad to see Shumway die, but I think in retrospect it will be clear it was a forward thinking decision. WASM will obviate a lot of the effort for what has clearly become a historical feature.
> Mozilla did realize their mistakes got back from their 9 year vacation (2009-2018)
The origin of modern Firefox could be dated back to the origin of Servo in 2012 since it layed all the groundwork. I think this is the clear turning point in Mozilla's refocus, maybe push it back to 2015 when Firefox OS was dropped.
There's also a new (I think?) mobile browser in progress. I'm not sure how it fits into the larger picture and information is a bit scarce, they just started releasing beta builds.