vitovito

These appear to be the relevant patents:

https://patents.google.com/patent/US6415439B1/en includes some aspects of the MIDI protocol in the tables; does this cover the LPC information the SWEETPEA authors couldn't figure out?

https://patents.google.com/patent/US6317714B1/en

https://patents.google.com/patent/US6281939B1/en

It doesn't look like anyone's published a reverse-engineering of the protocol.

Where does one get a 49.86mhz(??) maker-level transmitter these days?

Ishikawa had SOTA a decade ago with their page-flipping, high-speed video scanner: http://ishikawa-vision.org/vision/BFS/index-e.html

Also, this DIY Book Scanner forum thread: https://diybookscanner.org/forum/viewtopic.php?f=17&t=788

I've written up my experience conducting a design sprint for an internal, enterprise IAM team: http://vitor.io/designer-hangout-product-discovery-design-sp...

Our internal pitch for design sprints (using Jeff Patton's Product Discovery model) were basically getting to an informed go/no-go decision on a new feature in a week, and the teams that adopted that did find success in it.

Maintain the domain registration indefinitely on behalf of your friend. You could register it for ten years and renew it yearly so the risk is always ten years out, and hope that by the time they stop using it, whatever systems they authenticated with it are also defunct within ten years. You could also retain a company like MarkMonitor, which does domain management as part of trademark and other IP management.

But there's no way to control it after it lapses. It's an implicit risk for any system that relies on email for authentication.

I think the house analogy is a good one. You should buy the domain and use it, that's how they work, just like houses, but you can also be intentional about being clear that there were people there before you. Establishing redirects to archived versions of the URLs is one.

I recently sold a previously personal domain to a company that was going to use it for a new product. I added contractual provisions to address some of the issues that would come up, and I experimented with explicitly archiving a marker file to leave a record in web archives that the domain had changed hands, and a human being could consider treating the site as having different owners (and thus different archival permissions) before and after that point in time.

I wrote up my findings here: http://vitor.io/archival-markers and the proposed "/.well-known/archival-ownership-markers/ resource prefix" is described there along with examples.

The key word to search for is "canvassing" software.

I can't answer why they don't, but there have been a few companies in this space trying to make a business out of it.

Pieceable circa 2011 was acquired by Facebook: http://web.archive.org/web/20111006043944/http://www.pieceab...

Kickfolio circa 2012 (later app.io) raised $1M but shut down some time in late 2016 or 2017: http://web.archive.org/web/20120903014851/http://kickfolio.c...

AFAIK, both streamed the iOS Simulator to your browser.

Making a whole app available probably raises a lot of security and privacy issues; for a demo, you probably want something closer to a playable quote: https://tenmile.quote.games/

Just did! Has only bootloaders from 2014, though, and firmware changes with the Pi itself mean it won't work on the latest Raspberry Pi models, nor will replacing the RISCOS.IMG from a current version with the Pico version.

When I tried RISC OS' own instructions to have the equivalent experience with their latest OS versions, they seemed to be missing a step, too, as I'd still boot to a desktop on a Pi 4: https://www.riscosopen.org/wiki/documentation/show/Raspberry...

Write the latest full RISC OS (through Raspberry Pi Imager or elsewhere). Edit CMDLINE.TXT per their instructions, and after it boots, on your keyboard, press F12 to open a command line at the bottom of the screen, type in the commands from their instructions, and then also type:

    Unplug Desktop

Then press Ctrl-Break to reboot. You don't need to copy files to other SD cards or anything. It will boot immediately into BBC BASIC in Mode 7 (40x25, Teletext pixels, 16 colors).

In swapping the SD card between a Pi 1/2 and a Pi 4, I was getting occasional misfires, though, and it wouldn't boot into BASIC, getting hung up on the wrong networking driver, or complaining about a missing desktop. Ctrl-Break to reboot should fix it.

Matt Webb is the author, their contact information (GitHub repo, personal site with email) is at the bottom of the page.

Is https://aboutfeeds.com/ an answer to #2 and/or #5?

Why does the workout require motivation? You don't need motivation to eat or sleep. Surely you've experienced the negative consequences of a sedentary lifestyle: getting winded, needing help to move heavy objects, injuring yourself more frequently. If you have children, being unable to physically keep up with them. Health and strength are as important as feeding yourself and getting rest.

Strength training is functional: the thing you are building is strength within your own body. Programs often focus on just a handful of core exercises (squat, press, deadlift). They're the opposite of crossfit, and you can find gyms and trainers that will help you focus on your form in the way you want, without the shouting and peer pressure.

Rowing can be similar, and also a full-body workout, and lower impact on your joints if your form is correct.

It took me 6-9 months to not resent going to the gym three days a week. It's not fun, it's work, it's effort, it's an obligation for my health and wellbeing.

I've previously used Strapdown: http://strapdownjs.com/

From my bookmarks, there's also Markdeep: https://casual-effects.com/markdeep/

Not the OP, but in my experience, when clinicians ask for more data, they're actually asking for more lineage or provenance metadata.

We boiled it down for our teams like this:

Administrators are top-down: they want a high-level view and to be able to drill down from there.

Individual physicians are bottom-up: they want "their" data about "their" patients, and maybe, sometimes, to compare to the peers they personally trust.

As with any professional group, there's some minority percentage that treats their work like a craft and knows how to use data to improve their practices; but the majority want qualitative data and value interpersonal relationships. Giving a dashboard to the latter group at all is wasting time and effort of all parties.

If your dashboard can't attribute all of its data and all of the patients referenced to match the physician's definition of "theirs," you've lost. That's the "more data" and "drill down" physicians care about.

If your dashboard isn't timely and clinical -- which generally means presented in a clinical voice, at the point of care, or otherwise when they have an opportunity to make the change you want them to make -- it's not going to be actionable. That means surfacing some alternative action right before they see a patient which might benefit from that, which is not when they're on their computer. They might be one of those doctors that never is on their computer until the very end of the day. Looking at your dashboard at 11pm about the patients from earlier today (or more likely, earlier this past quarter of the year) is not helpful.

Looking at your dashboard is non-clinical work, and doctors want to do clinical work. If you're going to make them go do a new and non-clinical thing, it has to reduce some other non-clinical thing in a way that's meaningful to them. Otherwise, they're just as likely to do an end-run around your application entirely, like the doctors who only use index cards to write notes or who fail to enter their passwords every morning and lock themselves out, so they don't have to use the EMR.

Are you me? I also built out a body of research in a healthcare company about how to engage clinicians using data, that stopped us from making some mistakes until we got acquired. No doctor (or chief of staff, or chief medical officer, or anyone besides an actual data analyst) will slice and dice their data. Doctors won't even listen to a non-peer clinician discuss data with them, let alone their administrators.

In my timeline, I told the engineering team that all of their work was almost certainly for naught, that all the research said this product would completely fail, and we were basically just doing it for managerial and contractual obligations.

This gave engineering the freedom to use whatever technologies and conduct whatever technical experiments they wanted, since no-one would ever use the product, and it'd likely be shut down soon after launch for disuse.

A key hospital partner gave us a couple dozen docs to test it with. I interviewed them about how they measured their work and impact, and the data they used to improve their craft and outcomes. I asked them to review every measure on the dashboard, explain their understanding of it, and explain how their work or behavior would change based on that.

Almost to a person, the doctors said there was nothing of use to them there, as the research predicted. Some of these doctors were on the committee that specified the measures they would themselves be seeing.

The product was launched with great managerial acclaim, and promptly sunset 12 months later from disuse.

The Grid Book, by publication designer Jan V. White: https://archive.org/details/gridbookguidetop00whit

Copy rights are different from trademarks or patent rights. Related rights to copy rights are e.g. moral rights in France. CC0 and other public domain deeds (e.g. Unlicense) are about copy rights alone.

If you mean to also disclaim trademarks or patent rights, you will need additional waivers for each of those, as they're different aspects of rights and law.

I publish all of my original work into the public domain (using Creative Commons Zero), and have for years.

The reason, for me, is almost entirely pragmatic. Copyright and licensing are protections, but in today's world, receiving the benefit of that protection requires a budget, a lawyer, and a willingness to undertake legal proceedings which could take years to resolve.

If I am willing to invest in (1) registering my copyrights, which in the US is the only way to receive damages, (2) ongoing and perpetual searches to make sure no-one has violated my copyrights or licensing, (3) the costs to have one or more lawyers write letters, sue, and defend the suit in court against a likely large corporation who will spend millions to delay the case and bankrupt me, then I absolutely should put a license on my work and actively engage with my copyright.

If I'm not, regardless of whether I cannot afford to or do not desire to make a lawsuit my life's work, then I should opt out of the entire system. That is usually my choice.

( As a further note, Yale Law professor Stephen Carter argues that there's a fourth condition there: (4) if I'm willing to kill someone to enforce a legal verdict in my favor. See the quote in https://www.theatlantic.com/politics/archive/2016/06/enforci... )

For as long as I've been tracking (76 applications since 2018), my numbers for PM/design/research roles are roughly:

- 1/3 will either never acknowledge your application or ghost you mid-process

- Two weeks between human contact is about the average for a company with its shit marginally together

- It's taken as long as 238 days for a formal rejection, but the mean is more like two months

Do you need a git version? Or do you just need to be able to experience the development of a text?

If the latter, you can use Draftback (described: [1], download: [2]) to get an Etherpad-style time slider in the text.

If you needed to preserve that view, you could screen record the playback. You could also dissect the Chrome extension and turn its rendering output into something else, a text revision with each change, suitable for checking into version control? I'm not sure how Draftback handles rich formatting, images, tables, or the like; you'd have to figure that out, too. You'd also have to match the checkins to the time spent doing the writing, or you'd miss out on the cadence of the writing. And is there even a tool that lets you visually scrub through a document's changes in git with a time slider or equivalent?

[1]: http://features.jsomers.net/how-i-reverse-engineered-google-...

[2]: https://chrome.google.com/webstore/detail/draftback/nnajoiem...

Being able to the see the components is a great start, but one of the things we've been unable to easily do in our own trackers is dynamically remove particular stocks to see how much someone's portfolio growth is relying on e.g. TSLA. Any plans for that?

JPEG can be made almost as resilient as an uncompressed format by adding in restart markers.

Restart markers duplicate the JPEG headers within the file, at however many intervals you like, so the bitstream can be, well, restarted, limiting the effect of any corruption.

`jpegtran` can insert them losslessly.

Looks like it used to live at http://www.escapeyesterworld.com.

You can look through the Wayback Machine's archived URLs to find the video URLs here: https://web.archive.org/web/*/http://www.escapeyesterworld.c...

Like contactless payments, it uses NFC (the protocol), not NDEF (the data format) to write the image. You're not writing the image as an NDEF message, so NDEF-only systems (like early iOS support or WebNFC) won't be useful.

Open source code to write the image using libnfc and node.js 8.x: https://gitlab.com/bettse/wne_writer

The pragmatic answer is that, the USPS tried it 2-3 times in its history, but was continually hobbled by private industry lobbyists, until in 2006 when it was finally banned from ever trying anything again: https://www.bloomberg.com/features/2016-usps-email/

Practice. You're telling a story, it can be prepared, you don't have to relive it every time.

Understand why they're asking. It's easy to talk about your success, and to idealize how we got to an outcome, but in reality it's more like: 1) search for something on StackOverflow, 2) figure out you should be searching for different terms, 3) try some off-the-shelf software recommended in a buried comment, 4) fail to compile it from source, 5) try a buried answer in a related question; etc. Those are all "failures" in that you weren't born knowing the correct answer, and being able to describe how you got to an outcome fully is valuable.

Ask them the value they're getting so you can characterize the experience appropriately. We were hiring a senior designer to work with a particularly internally contentious product and development team. We were concerned they hadn't discussed any grit during the interview process, only happy paths. We call them up and say, tell us about a time you fought with someone and lost. They respond, "uh, am I going to have to actually fight people in this job?" No, your PM might be a real pain in the ass and we can't seem to get them replaced so you're going to have to stick up for yourself, and we'd like to hear about a time you did that and it still didn't work out for you, and what happened next. And, they did, and we hired them, and they worked out well.

My understanding is you're looking for landmarks in the audio and then matching/aligning on those.

Shenidam is open source software which does the whole process, site offline, GitHub still up: https://web.archive.org/web/20160309034204/http://shenidam.o... and https://github.com/stendardo/shenidam

A node stream module: https://github.com/adblockradio/stream-audio-fingerprint

Python: https://github.com/dpwe/audfprint

A blog post explaining fingerprinting: https://willdrevo.com/fingerprinting-and-audio-recognition-w...

Commercial software: https://www.redgiant.com/products/shooter-pluraleyes/

You could promote those accounts to @FlickrJubilee, which at one point was taking names and donations: https://twitter.com/flickrjubilee

Archive Team had a Warrior project to preserve at least freely licensed photos, and they have an EFnet IRC channel #flickrfckr where you might be able to provide accounts for further archiving: https://www.archiveteam.org/index.php?title=Flickr

This has been pretty widely discussed elsewhere, including Twitter, and in part was the reason SmugMug changed that policy at the last minute to include preservation of freely licensed photos, and deceased users' accounts: https://petapixel.com/2019/03/09/flickr-will-save-all-creati...

Likely the best way to "save" free accounts with more than 1000 photos that haven't yet been deleted is to use the new option to gift them a Pro membership, which apparently doesn't require the account's consent.

But communication on-the-fly, on-your-feet, in a high pressure environment, which is what a whiteboard test is, is not most communication.

Most communication gets thought about, drafted, revised, critiqued, socialized, ahead of distribution.

If your whiteboarding comes after hours or days of consideration and review, that sounds like a great way to vet good communicators. Otherwise, aren't you optimizing only for speed? If someone cracks a joke in the moment, they're a wit; but we only pay money to and call comedians those who worked on it for a while.