Hey HN, I'd love it if you could give me feedback on my first little app. I did this on my own as a pet project. At some point it reached an acceptable state of stability and usability, therefore I launched it. It's a MVP for sure.
It's a pretty cool extension! Altho the way you handle new tweets (or replies for that matter) is too slow in loading. Is there no other way than to load in a remote webpage on ostrichapp.com to get the new message window?
At first, I was loading the new tweet form inline. But since the client's code need to be injected in every webpage, because that's all I can do with the Safari Extension API, then I couldn't put the form inline.
Here's why: I figured any malicious site owner could add some javascript code to submit the form with any text they want. Therefore any website could tweet something in your name. This is really bad, so I took this approach instead.
Absolutely agree. Much easier to tweet a page WITHIN Safari rather than copy the URL, move over to a Twitter app, then post it. Great feature, for sure.
12 comments
[ 5.6 ms ] story [ 40.8 ms ] threadHere's why: I figured any malicious site owner could add some javascript code to submit the form with any text they want. Therefore any website could tweet something in your name. This is really bad, so I took this approach instead.
(if that isn't possible - how come?)