14 ms·
Chrome 81: Near Field Communications, Augmented Reality, and More
- stevenwliao 7y agoFound a Web NFC site to try it out: https://webnfc.app/ https://webnfc.app/
- codemysoul 7y agoAuthor here. Let me know if you have questions.
- magma17 7y agocan you write a tag multiple times with one interaction?
- codemysoul 7y agoDepends on what you mean with an interaction. Technically it would be possible to stack write operations, so you could just keep a tag to a close proximity of the adapter, and keep writing messages one after another. With the webnfc.app, you can only write a single NDEF message with single record of either URL or Text, during single interaction.
- magma17 7y agoI mean, if the nfc event is triggered, this code for (i=0, i<10, i++) writer.write(i) does it write ten times the tag? overwriting every number?
- codemysoul 7y agoThe NDEFWriter write()-method currently returns a promise which is resolved on a successful write operation and rejected on a failed write operation, so you would need to use async-await to be able to loop those writes like that. Here is a reference to the Web NFC API Write-operation: https://w3c.github.io/web-nfc/#writing-to-an-nfc-tag https://w3c.github.io/web-nfc/#writing-to-an-nfc-tag
- dazhbog 7y agoMeh, only NDEF NFC protocol is supported. A little bit too restrictive. There are so many devices out there that could be configured from an authorised website but many of them use a proprietary binary tag format. Hope they open it up a bit in the future. Just like they did with webUSB and webBT.
- moonbug 7y agoDon't be the "meh" guy.
- yalogin 7y agoA. It unrelated but all of Google’s blog posts are unreadable on my iPhone. The text doesn’t appear, I just see the title. Hope it’s just me and google did t actually real safari compatibility.
- Elidrake24 7y agoiPhone 11, 13.3.1, no issues here. I do also run AdGuard, though that would typically break sites like this.
- bogidon 7y agoInteresting MS<>Google partnership on the design front. Wish they had redesigned `<select multiple>` though. That's one component that really feels stuck a million years in the past
- fabianlindfors 7y ago<select multiple> is in desperate need of a redesign. I made multi.js (https://github.com/fabianlindfors/multi.js https://github.com/fabianlindfors/multi.js) to fix this but hopefully browsers will take the matter into their own hands.
- megaman821 7y agoNative multi-selection is the worst. The fact that you have to hold down a modifier key to make multiple selections is a usability nightmare. I have rarely seen a person who knows how to use the native browser widget. Even when you do know how to use it, it is just too easy to make a mistake. If there were 5 options already selected and you want to add a sixth, so you click it but you forgot to hold down the right key. Now the 5 previously selected options are gone with no way to get them back. In general I like using native widgets because mobile browsers do a lot of work to make native widgets usable on phones, but <select multiple> is so bad on the desktop that I always replace it.
- mister_hn 7y agoBut why are Browser gaining so much power, even to drive peripherals besides audio and video? That's fundamentally wrong and insecure
- Sephr 7y agoThe current OS permission models used by applications and drivers that interface with these peripherals are much less secure than those used by browsers.
- saagarjha 7y agoYeah, but you'd still need a JavaScript VM escape to access them from a webpage.
- bagacrap 7y agoI don't think you understand the comparison. Any native code that runs on your OS can do almost anything, like access your webcam. Code that runs in your browser can't do that unless you (the browser) grant the permission, or it finds a series of exploits. If you are suggesting browsers shouldn't offer access to webcams etc at all, that would not make the world more secure because the web would just die and we'd all be back to running native code.
- moooo99 7y agoI'd say the opposite is true. With more powerful browsers, you are making web applications more powerful and remove the need for a desktop app. Web apps, if built correctly, are probably more secure than desktop apps. Especially considering that you completely remove the need for user updates, since the website is updated by the developers. Plus, webbrowsers implement a proper permissions model unlike native apps, especially on Android, used to do.
- bjoli 7y agoSure, web browsers implement a proper permission model, but: the surface of a browser is enormous. Just the sheer magnitude of a modern browser gives me vertigo. Chrome has how many compilers? How much code to handle broken input? Whereas most kernels are easy to understand (even relatively modern ones like seL4), also many parts of a browser are at the frontier of "applied CS". If I were to build something relatively small today, I don't think I would feel safe if it had to run in a browser due to the enormous complexity of a browser. I just don't think it is possible to secure them fully. Writing everything myself at least gives me a false sense of security in the sense that I at least believe I understand what is running :)
- jve 7y agoOh, the time has come: > This version of Chrome removes TLS 1.0 and TLS 1.1. TLS (Transport Layer Security) is the protocol which secures HTTPS.
- Florin_Andrei 7y agoSo long, and thanks for all the blowfish.
- Krasnol 7y agoFirefox did the same with the release yesterday: https://www.mozilla.org/en-US/firefox/74.0/releasenotes/ https://www.mozilla.org/en-US/firefox/74.0/releasenotes/
- tandr 7y agoYeah, and the first thing I did this morning is to reenable it in order to access 5-year old cable modem. The "on-for-all" or off-for-all" feels kind of dangerous, it should be something I can enable for 192.168.. for example, and not for the whole world. As a matter of fact, for the local network it should be a default "on". IMHO, YMMV
- wayneftw 7y agoIs this the one that will disable extension manifest v2? That's the only update I'm watching out for because I'll have to switch to another browser at that point. I was going to start using Edge everywhere but now probably Brave after reading this - https://www.zdnet.com/article/brave-deemed-most-private-browser-in-terms-of-phoning-home/ https://www.zdnet.com/article/brave-deemed-most-private-brow...