devadvance

Interestingly, there's a company in the U.S. working to address this (Levels Health). I saw an article in The Verge about the product [0].

This has been done elsewhere, such as in Europe. For example, Supersapiens offers a similar service [1]. However, as you may note when you visit their page in the U.S., it's not offered in the U.S. This appears to be due to the fact that the sensor used, the Abbot Libre Sense [2], is not available in the U.S.

* [0] https://www.theverge.com/22794594/levels-health-glucose-fitn...

* [1] https://www.supersapiens.com

* [2] https://www.libresense.abbott/en/home.html

Strongly agree with this. I'd add that shared vehicles of any kind make multimodal transportation far more feasible.

For example, I can walk to a bike dock, take a bike a few miles, then dock it. I can then bus/rideshare home as a result of weather, timing, luggage, etc.

It's certainly possible to do this with owned vehicles to some extent, but with far less flexibility.

Google Stadia | https://stadia.dev/about/ | Multiple locations (U.S., Canada, Germany) | Multiple Roles | Full-time | ONSITE

Stadia is Google's cloud-based platform that lets you instantly play your favorite video games on the devices you already own. No more waiting for game downloads, updates, or installs. With Stadia, you have the freedom to decide how to play, what to play, and where to play across laptops, desktops, phones, tablets, and TVs.

We design, build, launch, and land the fundamentals that make it possible to include video game streaming in first- and third-party applications.

We're looking for folks for a variety of roles, such as:

• Engineering Manager, Client Software Development Kit, Stadia - https://careers.google.com/jobs/results/92087616158999238

• Engineering Manager, Stadia Developer Tools - https://careers.google.com/jobs/results/86504840366039750

• Software Engineer III, Full Stack, Stadia Graphics Infrastructure - https://careers.google.com/jobs/results/73804741072560838

• Staff Software Engineer, Front-End, Stadia - https://careers.google.com/jobs/results/93196403976610502

• Product Manager, Stadia - https://careers.google.com/jobs/results/111760946944189126

• Product Manager, Content, Google Stadia - https://careers.google.com/jobs/results/143567615688614598

• Technical Integration Manager, Experience Studio - https://careers.google.com/jobs/results/87639454174323398

• Strategic Partner Manager, Stadia - https://careers.google.com/jobs/results/134300370240185030

And many more roles that you can find and apply to here: https://careers.google.com/jobs/results/?q=stadia

You can also learn more about some of our engineering work on our tech blog: https://stadia.dev/blog/

Disclaimer: I have read the Economist article but not the book it appears to synopsizing/marketing.

It doesn't seem like trying to simplify challenges in large cities to a single dimension like housing is a path to success. Basic needs and social services beyond housing go a long way in supporting people, which (sadly) can't be provided by just addressing a housing shortage/affordability gap.

It's worth taking a look at the SF Point in Time and Housing Inventory Counts data [1] to provide context on this conversation.

[1] https://hsh.sfgov.org/about/research-and-reports/pit-hic/

Google Stadia | https://stadia.dev/about/ | Mountain View, CA, USA | Multiple Roles | Full-time | ONSITE

Stadia is Google's cloud-based platform that lets you instantly play your favorite video games on the devices you already own. No more waiting for game downloads, updates, or installs. With Stadia, you have the freedom to decide how to play, what to play, and where to play across laptops, desktops, phones, tablets, and TVs. We're working to expand the availability and convenience of how people play the industry’s best games.

We are also making our infrastructure and tools available to developers and publishers who want to build their own interactive streaming platforms, and deliver their games directly to their customers. We aim to grow the industry across gaming and other interactive streaming applications.

Gamers demand high quality, performant, gaming experiences, which requires us to solve complex engineering challenges every day. This role involves delivering functionality that is used by both external users and external app developers; on servers as well as clients. These present unique challenges.

We design, build, launch, and land the fundamentals that make it possible to include video game streaming in first- and third-party applications.

I'm looking for folks to join our Client SDK team:

• Engineering Manager, Client Software Development Kit: https://careers.google.com/jobs/results/92087616158999238-en...

• Senior Software Engineer, Client Software Development Kit: https://careers.google.com/jobs/results/117505447633527494-s...

• Other Stadia roles: https://careers.google.com/jobs/results/?q=stadia

You can also learn more about some of our engineering work on our tech blog: https://stadia.dev/blog/

Happy to share!

WebP [1] is based upon VP8 encoding. VP8 is one of the codecs for which WebM is frequently a container. Ultimately, it's similar but achieves different objectives.

[1] https://en.wikipedia.org/wiki/WebP#Technology

I don't know if there's a pre-existing site that will do it, but you could do this with FFmpeg and therefore FFmpeg.wasm. A brief search [1] indicates that it would likely be about the combination of the right filters. Ostensibly, you could put those filter options into the FFmpeg.wasm demo app [2] (scroll down) and get your video out.

[1] https://stackoverflow.com/questions/54547061/ffmpeg-animatio...

[2]https://ffmpegwasm.netlify.app

A couple issues with this link:

1) The post is a three-paragraph news announcement rather than anything of substance. There really isn't anything material to discuss specific to this link.

2) This page was originally posted in either 2019 or 2020. In this 2020 snapshot [1], it says February 2019.

From other sources, it seems like somewhere between a stablecoin and just using a different data store for corporate finance.

[1] https://web.archive.org/web/20201013063509/https://www.jpmor...

If longer menus are needed, it might be necessary to manually set `overflow: scroll` and hide the scrollbar.

I saw several posts about using `<details>` in this way, but none that fully implemented what I was looking for. So I implemented a site navbar that uses `<details>` in two ways: for dropdowns, and for a sidebar.

A working reference implementation can be found here [1]. Additionally, I ended up using a version of this on my personal site [2]. This works on stable versions of Chrome, Edge, Firefox, and Safari.

One thing to be careful of when using `<details>` in interesting ways: accessibility. At a minimum, I encourage folks to make sure that screen readers work as expected.

[1] https://codepen.io/devadvance/pen/bGBvvWv

[2] https://github.com/devadvance/devadvance.github.io/blob/mast...

Fantastic post that builds up knowledge along the way. A fun case where this type of knowledge was relevant: when creating emoji short links with a couple characters (symbols), I made sure to snag both URLs: one with the emoji (codepoint + `U+FE0F`) and one with just the symbol codepoint.

Another thing worth calling out: you can get involved in emoji creation and Unicode in general. You can do this directly, or by working with groups like Emojination [0].

[0] http://www.emojination.org/

This could be helpful to some folks. I appreciate the clear distinction between "salaried" and "exempt", as that's something I've seen many folks misunderstand.

It's worth noting that, if you're in the United States, minimum salary for exemption also varies by state [0]. For example, as of 2021 in California, for many professions it is now 58k USD.

[0] https://sbshrs.adpinfo.com/blog/exempt-employees-minimum-sal...

If you're referencing the GIF of the terminal: it's a small docker image[0] I use to have a consistent demo environment. In this case, I'm running it within iterm on macOS.

[0] https://github.com/devadvance/terminalcheatsheet/blob/stagin...

The hover previews is an awesome example. Thanks for sharing!

I like collections of commands. However, the challenges that seem unsolved are (1) keeping the example in sync with the CLI options, and (2) making it easy to dig into parts of examples. The former is a classic documentation problem, of course.

Are you using FFmpeg or directly using libavcodec (or similar)?

Author here. This is the same journey I went through and I 100% agree! It can be intimidating at first, but FFmpeg is a a worthwhile utility to begin learning.

I've also added some shell functions[0] to my dotfiles to make it a bit easier to use when switching between several different machines.

[0] https://gist.github.com/devadvance/03d3c8f57b3e0254fb989e946...

Previously discussed here: https://news.ycombinator.com/item?id=15340729

As an engineer, I appreciate the depth of this post. However, I'd also appreciate a more approachable version that I could share with a broader audience. E.g., without understanding anything about hashing, SGX, etc., how can we best explain the advantages of this approach over the "upload your contacts list" request that you encounter in other chat apps?

Ah, I didn't realize that! Looking at this [0] issue thread, it seems like the minimum version with AVIF support is v7.0.25. The suggestion to use Docker in that thread might be useful for you as well, if you are interested in a couple quick tests and are already set up for containers.

[0] https://github.com/ImageMagick/ImageMagick/issues/1432#issue...

I used ImageMagick [0] just now to create a couple test images.

  magick testimage.png testimage.avif
  magick testimage.png -quality 60 testimage60.avif

[0] https://imagemagick.org/script/magick.php

Great work on this! I especially appreciate the use of the limited-input device flow, after seeing many device projects that use flows intended for servers :)

> Support & configuration for time zones

Are you referring to this? [0] Might be out of scope, but from experience, there are some date/time conversions that will require the TZ name (e.g., "Europe/London") to avoid needing to know whether to use the offset value or DST offset value. Could be worth including the canonical names [1] in a future revision.

Again, awesome work, and it's pushing me to try an E-Ink project of my own!

[0] https://github.com/tikurahul/Inkplate-6-micropython/blob/mas...

[1] https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

The native mobile app does not use a web view.

The native app uses Flutter [0].

Disclosure: I work on Stadia, and am speaking only for myself.

[0] https://9to5google.com/2019/11/08/google-stadia-app-play-sto...

I agree that the support for uncommon resolutions is less than ideal. That said, I've gotten it to work. Caveat: sample size of one.

On a 2019 MacBook Pro 16" with the dedicated GPU, I've had success connecting a 5120x1440 Samsung CRG9 via DisplayPort. I had to use this adapter [0] and this cable [1] to do so, but it does work. It also works on a 2018 MacBook Pro 13", but due to the lack of a dedicated GPU (i.e., Intel graphics only), the output is a bit fuzzy as it's not a natively supported resolution. Still, it's good enough for productivity work, though not for video/photo editing or gaming.

[0] https://www.amazon.com/gp/aw/d/B07F17ZHJY

[1] https://www.amazon.com/gp/aw/d/B079736Z53

When building for the web, I use a combination of Lighthouse (Chrome Dev Tools audit) and the axe extension to do a first pass at validating the accessibility of the site/app/etc. Of course, there's an art to this as well.

For example, there's a significant number of individuals with cognitive disabilities [0], so using a combination of axe to ensure heading structure is logical and accurate, plus spending the time to ensure concise and accessible content, is an approach that I take often.

a11y is more than WCAG contrast ratios :)

In principle, I like it. A lingering question, however: how would this work from a search engine indexing standpoint?

Hi folks! This idea came to life after a friend asked for a guide to get started using the terminal on their MacBook. Though there are sites/pages that are workable, none quite matched the goals of approachability, accessibility, great UX, and performance that I was aiming for.

Terminal Cheat Sheet is the result of the collaboration between me and my friend [1] to try to meet those goals.

It maximizes approachability through straightforward content and localizing, accessibility through best practices like WCAG [2], and performance through the use of static content. It's also meant to complement, not replace, options like man pages or detailed user guides.

We started with the most essential commands and a few guides for now, and we're really looking for constructive feedback. Would this help folks get up and running on the terminal for the first time? What additional guides would help with that? Are you interested in helping us translate to other languages?

If you have any questions or ideas, please comment, reach out, or add an issue to the repo. PRs welcomed [3].

- - - - -

[1] For more of his work, check out https://medium.com/@dontcallmebigguy and https://github.com/dontcallmebigguy

[2] https://www.w3.org/WAI/standards-guidelines/wcag/

[3] https://github.com/devadvance/terminalcheatsheet

Two kinds of data may be interesting:

1) where fiber may be run but not offered for residential service. E.g., future offerings.

2) where business fiber is offered. This would cover the dedicated internet (DIA) option.

Wish I had known about this months ago! Any more info you can share on data, plans, etc.?

Maybe a quick cache in front of Plaid for now? Even in-mem might be a decent short term solution.

Cool idea, though I couldn't get it to load yet. Will look after the deluge of interest goes away!

I'm curious: do you see any risk of folks indirectly tracking you via your transactions?