I'm finally rewriting the Chrome extension to work with the new security restrictions. Chef's kiss to the Chrome team for adding the joy of message passing to Javascript, and giving developers three debug consoles to hunt in instead of one. I humbly accept this bounty.
-
-
-
Replying to @aboodman
Sorry, I'm not allowed to exchange messages with you in the Twitter context
1 reply 0 retweets 2 likes -
Replying to @Pinboard
It's funny because it was actually insanely difficult to make and so carefully thought out. But to you (rightfully) it's nothing more than a pita and speedbump. There's a lesson in there.
1 reply 0 retweets 2 likes -
I think it's "don't try"?
1 reply 0 retweets 3 likes -
Replying to @aboodman
It's like trying to admire the fine stitching and craftsmanship of the boot that's kicking me in the nuts. Hard to focus on the positives although it's undoubtedly quite an achievement.
1 reply 0 retweets 10 likes -
Is the design process for this documented anywhere, or is it another case of having to find and pour beer into the right people to hear the story?
1 reply 0 retweets 2 likes -
Replying to @Pinboard
Not sure the exact thing you're hitting (message passing isn't a recent change) but some old docs are here: https://www.chromium.org/developers/design-documents … (find in page "extensions" and crawl from there). Beer is gladly accepted too.
1 reply 0 retweets 0 likes
Thank you! I wrote an extension back in 2012 and was dragged back into it now, so I have missed seven years of whatever happened. I appreciate the pointer!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.