940 karma · joined May 7, 2009
Current work:
- AI agent readiness testing: https://axtesting.com
- Prototypes, workshops, feasibility sprints, and technology transfer: https://tertile.one
Based in Austin, TX, USA, working with clients and open to work globally.
Current hobby projects include:
- NFC toy music boxes
- Digital audio players with tape scrubbing
- Modern digital stereo cameras
- Projectors and active link cables for handheld consoles
- Updates to my past work to improve its access and visibility
Personal site: http://vitor.io/
Plenty of commercial systems are bolted-together, commercial-off-the-shelf components or whole products. How many small shops have you swiped a credit card at, and their "register" was an iPad in a stand? Doing so lets you focus on the actual core competency of your business or product. If you're worrying about what some unknown customer might think about the appearance of your product at this stage, you're not focusing on the product itself.
I have ~200k hours of legacy audio I'd love to be able to do a fuzzy (phonetic?) search on, to pull content from and get real (human-edited) transcriptions of important stuff to resurface it, but there's not a lot of incentive to push it through a service for a quarter million dollars and then also pay to store and search it, since we're currently doing without it. Doing it at extremely low priority, delivering it over a long span of time, for an order of magnitude cheaper, with our IT standing up some stock fuzzy search engine, is a pretty easy sell, though.
Your web page points to different hashes over time through IPNS, which is additional work for a user, and relies on IPNS instead of being part of IPFS directly.
From a user perspective, Dat (and ZeroNet) maps to folders and filesystems much more coherently than IPFS does. I evaluated a few systems for a single use case in this Twitter thread: https://twitter.com/vitor_io/status/1019271473771569153
Remote: Yes
Willing to relocate: Would consider for the right role and city
Technologies: User experience (UX) design, user research, design technologist, prototyping, especially in emerging technologies (voice, 3D, AR, VR, sensors, IoT)
Résumé/CV: https://www.linkedin.com/in/vmiliano
Email: Listed at http://vitor.io
I got the impression, not that it was abandoned, but that bunnie and whomever else involved were hardware people, not software people. It had all the hallmarks of a hardware development kit without any serious software people on the core team. Software folks without experience working on underdocumented and undersupported hardware platforms had no place to go, no paths laid out, no real documentation for making the NeTV do things with just the built-in browser or kernel, like "what fonts are available out of the box" or "what is the equivalent WebKit/Chrome versions and how do I debug errors". The hardware folks expected the software folks to also be hardware folks, and they usually aren't.
I haven't seen an equivalent of a subcompact publisher (https://craigmod.com/journal/subcompact_publishing/) that provides reader analytics and supports authors as they write.
Also note that I don't think the hosted versions can be imported back into the Lytro Desktop software, if that's what you were hoping for; they're just stacks of JPEGs, JSON metadata, and the depth map data.
Rehosting an individual embed should be pretty straightforward, just replacing the CDN URLs with relative or absolute ones to wherever it's been rehosted (or to Wayback Machine URLs). I'll be writing up some details at some point, but don't wait on me.
Rehosting an entire user's "pictures.lytro.com" gallery was trickier than that, I don't think I was able to get it working locally.
Good luck.
They take a little while to load once you click on them; it's dozens and dozens of files.
The data for the embeds may still exist on Lytro's CDN, if you know the UUID for the image, and could be rescued and rehosted. After they shut their hosting service down last year, I crawled every embed the Internet Archive had, and downloaded the additional JSON and JPEG assets necessary to restore the embeds. https://www.archiveteam.org/index.php?title=Lytro
As far as I've been able to tell, their hosting service generated online viewers and embeds server-side, rather than their desktop software generating it and uploading it to pictures.lytro, Facebook, or 500px (the supporting services). It won't even let you do that kind of export without logging into api.lytro.com first. (Their Desktop 5 software is a .NET app if anyone wants to try poking at it.)
After their hosting service shut down last year, I crawled every embed the Internet Archive had, and downloaded the additional JSON and JPEG assets necessary to restore the embeds. https://www.archiveteam.org/index.php?title=Lytro
Those were eventually added, so now any embeds the Wayback had before the shutdown should work again, e.g. http://www.theverge.com/2014/7/30/5949913/lytro-illum-review v. https://web.archive.org/web/20170317183900/http://www.thever...
It's unclear whether all the Lytro file formats (including their later standard "XRAW") have any sort of documentation. The earlier formats (from their pre-Illum camera) do, e.g. https://github.com/nrpatel/lfptools but not the later formats, which include camera calibration data.
The viewers on GitHub, e.g. https://github.com/damienfir/lytrogl and https://github.com/behnam/php-lytro are only for their earlier formats.
If you're just calling s3 sync, it will fail in this use case, because s3 sync does not account for this.
You'd have to get a listing first, parse it, and then figure out interactively with the user what to do with the conflicting object names.
Or, more specifically, why it doesn't happen. A recent popular press article: https://www.bloomberg.com/news/features/2017-08-10/nobody-kn...
Underground? If the actual city can't get the data, how will you?
Inside walls? It's cheap and easy to make a hole and look, to make a lot of holes and look, tear down a whole wall and look. Manual labor is cheap.
Building the data up would be great if you had all the manual labor necessary to do it, but based on the Bloomberg article you'd never legally get access to the most vital spaces in order to compile it fresh for yourself (since the data already exists elsewhere, it's just that most people can't get it).
And then it's just as likely the cities wouldn't let you sell it to anyone or use it in anyway for security reasons, just like the utility companies are telling the city.
e.g. I can have "testobj" as an object, and also "testobj/child" as an object.
When downloaded to a regular filesystem, that breaks and you lose one object or the other object depending on which was downloaded first, because a regular filesystem can't do that.
It does have an API, and can work via bookmarklets, or by linking to pages by prepending https://via.hypothes.is/
Any requirements are going to be constraints, and may not be reflective of reality, good practices, market needs, user expectations, etc. In your example, discovery and purchase are often not performed in the same transaction/visit/mental process. Different modalities will result in different realistic time constraints. A UX person brought in to come up with "a variety of design concepts" is going to pitch discovery (vacation planning, pinterest-style aspirational ideation, reading travel stories, etc.) as independent from purchase (booking last minute, booking for the future, booking for a specific destination, booking for a specific cost, etc.). If time (efficiency, shorter is better) is a metric they're going to pitch time (time to bounce, longer is better) instead.
Any constraints are going to limit your possibilities, and might result in a local maximum. If you're okay with that, fine, just say it up front, so everyone is on the same page.
UX job titles are pretty varied, because UX roles tend to fill the space left by whatever expertise the product team is missing, whether research, or user contact, or interaction design, or visual design, etc. Again, I think you'd be better served by looking for types of experience.
Designer, UX designer, product designer, UX strategist, all might work as titles. Someone with research experience is probably necessary, but someone that is a dedicated researcher probably won't also be able to do the design work, and someone that specializes in visual design probably won't be able to do the research.
Does that help?
A lot of UX candidates are going to self-select out from this description, because you're bringing them in too late in the process. You're assuming that the requirements that someone (who?) has come up with are remotely correct, and an experienced UX person knows that's nearly never the case. (Perhaps you have a well-validated stack of customer and market research completed! But I'm going to assume that, like most product teams, you don't.)
Industry studies have found that features and product ideas developed in isolation are wrong, 1/3 to 1/2 or more of the time, where "wrong" is defined as "doesn't move the needle in the way it was expected to."
An experienced UX person is going to want to come in before requirements, to help collect the requirements through understanding users and use cases, and to do the "variety of design concepts" at that stage, often even with active participation from dev, PM, and other stakeholders. (You'll see this called "design studio" or other types of participatory, facilitated design.)
Metrics and measurements are also best developed at that stage, and actively tested to make sure the concepts will affect them in the way everyone expects.
You may be having trouble because "taking" requirements is often something only done by production designers: people who make the final graphics for implementation.
You might have the best success by visiting your local design meetups and looking for a freelancer or consultant with at least several years of experience doing design research, user research, and facilitation, the more experience the better. Hire them to vet and interview candidates; they'll want to understand how your team works and what your expectations for the role are.
Listen to them if they suggest your expectations are misaligned with regards to an effective design process.
Or its brand new sibling, Joy: http://ncase.me/joy/
Both by Nicky Case, who has made many explorable explanations: http://ncase.me
e.g. two independent streams, identifying the same 30-second commercial, but the audio streams are offset from each other by half a sample length?
(Note that a download of just page content and assets isn't enough; WARC stores headers, etc., also.)
I wrote about the problems open source projects often face getting design (and other non-technical) help they can use: http://opendesign.foundation/articles/import-designers/
I tested them in Chrome on a MacBook Pro and they seem to work, but your mileage based on browser/OS/keyboard may vary.