101–110 of 183 posts
I wonder what throughput it can give when used as an animated sequence of codes? I experimented with animated QRs for data transfer last week and the real maximum I’ve achieved was around 9KB/s. https://divan.github.io/posts/animatedqr Using colored high-capacity encoding should yield much better results, given the decoder is as fast as QR one.
Is there a "human readable" bar code variation? I want something that's both scannable and typeable. One use case is those placards for artworks at museums and galleries. I want to print something that's both easy to scan and easy to jot down.
Like a UPC code? Those have the contents printed right underneath.
Imagine downloading a working application from a barcode (perhaps assuming you have the "reader" app which includes a set of software libraries to do some of the heavy lifting / batteries included) -- gameboy did it. It might be useful in a disaster, or an oppressive regime scenario, but at worst, it would be fun.
3D models? Retro game console with games distributed on paper?
My imagination is limited, but I have a feeling that barcodes are something waiting to meet some newly-possible potential with the advent of handheld scanners and very high capacity barcodes.
We tried VR and PDAs and cellphones and stuff in the late 80s/early 90s, but it wasnt until the 2010s they became something really useful; I wonder if barcodes will find some new life in the future, now that more capable and available hardware exists.
I wonder what throughput it can give when used as an animated sequence of codes? I experimented with animated QRs for data transfer last week and the real maximum I’ve achieved was around 9KB/s. https://divan.github.io/posts/animatedqr Using colored high-capacity encoding should yield much better results, given the decoder is as fast as QR one.
Cool. How does Apple's iPhone-to-Watch pairing animated graphic work? Maybe their technique has higher bandwidth.
So my guess is that Apple's approach is optimized for coolness, rather than transfer speed.
[1] http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=H...
[2] http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=H...
Earlier quoted context omitted.
This is "retarded" all over again. Slavery in humans is bad. Slavery in software applications it not.
At a family dinner I once jokingly described my gluten-free girlfriend as "glutarded," which was our inside joke way to refer to her dietary restrictions. I forgot that my aunt's husband, who has some congenital language issues that leave him with a speech impediment, had grown up being bullied and called 'retard,' until he gasped when he heard my words. I felt horrible, and have since been more conscious with my wor…
Good luck finding a country with people of any color that hasn't experienced some level of slavery.
I wonder if the 'Master'/'Slave' terminology is necessary here? Aside from being problematic, does it really describe the setup more than 'Primary'/'Secondary'?
Is it problematic outside of the US? That said, possibly not the most immediately illustrative choice of terms; master/slave usually implies who's in charge, not a spatial relationship.
Spatial relationship aside, there are plenty of less problematic ways to depict who is in charge.
Earlier quoted context omitted.
I think OP's point was that humans can't recognize those features. Edit: I should have said untrained humans .
I can recognize those features. Sure, you need to look for them, but why would anyone care to? Surely after encountering only a few RGB codes the average person will have no trouble inferring that a jumble of colored blocks against a white background is likely to be encoded data. Same "training process" as needed for QR codes - although in this case the quiet zone is not needed, so you _could_ use these in a delibera…
QR codes are able to be recognized as QR codes, which means you're able to think "I could definitely scan that", rather than thinking "that is some data there, that I could maybe read or maybe not."
It's the same as the difference between saying that data on the wire is "a TCP packet" vs saying it's "HTTP." Yes, either way, you know that you've got some packets—but if you want to parse them, you'd better be able to recognize the format of those packets.