Thomas Steiner (@tomayac)

Now at @tomayac@toot.cafe

The below is an off-site archive of all tweets posted by @tomayac ever

June 29th, 2020

Sign-in form best practices, by ⁦@sw12⁩. Favorites: Be sure to make your password rules transparent and add a “show password” feature.💡 https://t.co/Noik5tdcGl

via Twitter for iPhone

RT @ChromiumDev: 🧪 Start experimenting with a new way to access browser and device data with User-Agent Client Hints. Available in Chrome 8…

via Echofon

@mhartington Love how many of the UI best practices of https://t.co/LpoNYtqD5v this implements. Great work. 💏

via Echofon

@wesbos @SaraSoueidan The marketing is great and they’ve definitely created a hype. Will I pay $99 for it to start fresh, tell everyone about my new email, and set up tons of backup emails again? Probably no. It’s a cool tech demo, though. For another

via Echofon

@html5test @voxpelli @firt They emphasized *in part* in the blog post, so yeah, fingerprinting was an argument in not implementing, but not the only one.

via Echofon in reply to html5test

@rowan_m I could also page your manager and mention that some of their reportees reports spare cycles. But you wouldn’t want me to do that, would you? /me pets cat.

via Twitter for iPhone in reply to rowan_m

If you want to test-drive this yourself, here’s the new branch: https://t.co/gGkKaiwGSJ.

via Twitter Web App

Sneak preview of the 💷‍♀️ Service Worker Detector extension (https://t.co/0L1fYfz5tZ) working in Safari Technology Preview 109.

(Thanks, @xeenon, for the handholding in getting this up and running). https://t.co/eg3sLkldTq

via Twitter Web App

@campuscodi @ZDNet The article lacks the source. This is the missing link for where you write “Apple said”: https://t.co/mBwQwiGFTG.

via Twitter Web App

@xeenon 🎉 Thank you so much for the help! Greatly appreciated! It all worked fine nopic.twitter.com/rqgFvQb2NC2NC

via Twitter Web App in reply to xeenon

@xeenon It’s probably the same thing with the missing references. I need to recreate the project. Be right back.

via Twitter for iPhone in reply to xeenon

@xeenon Ah, I see. That’s the kind of thing I meant. Xcode n00b here, sorry. Let me try to fix my project then.

via Twitter for iPhone in reply to xeenon

@xeenon Another small thing I ran into: inspecting a popup window only works if you set Web Inspector to open in a new separate window. It shows a white screen when run docked.

via Twitter for iPhone in reply to xeenon

@xeenon This is from my `popup.html` file, note the highlighted parts. pic.twitter.com/Q0HKPGhlEQ

via Twitter Web App in reply to xeenon

@xeenon Awesome, this was it. It seems there’re some issues with resolving relative paths. If I load everything from `/` it works. pic.twitter.com/RGCTpX1ebj

via Twitter Web App in reply to xeenon

@xeenon Woohoo, managed to build an extension by creating a fresh extension via the wizard and then replacing the Resources.
Now I get `[Error] Failed to load resource: The operation couldn’t be completed. (Cocoa error -1000.)` in my popup.js. How do I

via Twitter Web App in reply to xeenon

@xeenon I’ll give it a try as soon as I can. Unfortunately can’t install a beta build myself on my corp. MacBook.

via Twitter for iPhone in reply to xeenon

@xeenon My suggestion would be to have the documentation be cross-read by someone who never touched Xcode and any of the App Store publication process.

via Twitter for iPhone in reply to tomayac

@xeenon Thanks for the clarification. As many developers, I won’t start from scratch, but try to convert an existing extension. But good to know starting fresh is supported now on Catalina.
FWIW, I hope not to run into native issues like with the old Ed

via Twitter for iPhone

🗣 PSA: If you want to play with Safari Web extensions (https://t.co/YpRKOOae2N), you need(!) to be on macOS Big Sur. I tried installing Xcode 12 beta on Catalina, switched to it, installed STP 109, and it still wouldn’t work. Confirmed by @xeenon: http

via Twitter Web App

@nomsternom @webkit @ChromiumDev Yes, prompting isn’t the universal answer. I still think a mix of granting _some_ permissions on install and ad-hoc _grouped_ prompting for others could work, all while “forgetting” granted permissions after a certai

via Twitter for iPhone in reply to nomsternom

“They [@npmjs] realized it after the fact [of firing five engineers] that they let all the black people go”.—@nomadtechie
I don’t have details, follow Amal instead. ⤵️ https://t.co/pWkaLmRWJO

via Echofon

@WebKit’s first line of defense against fingerprinting is to not implement web features which increase fingerprintability and offer no safe way to protect the user. Here are some examples of features we have decided to not implement […]:”—https://t

via Twitter Web App