adyus

Well, Google's getting close; what about "hot shingles in your area"?

https://sunroof.withgoogle.com/

drone.io (https://www.drone.io/) has worked wonders for me.

USD is backed by the U.S. military force, via a slippery slope: you can only pay taxes in USD, and if the taxes you owe are large enough and you refuse to pay, the U.S. government will send increasingly larger forces to claim those taxes.

As long as the docker daemon starts on startup, there's a `restart: always` option in the docker-compose.yml config file that takes care of it. Using `depends_on: [list]` takes care of startup order cleanly.

I agree with you. Removing anything off-chain from the conversation, we're left with the equivalent of selling a million pixels on a web page (but at least there was some utility to that, in the form of advertising).

I'd argue that this limitation is artificial as well. With some painting forgeries, you're getting down to the molecular or brushstroke level of differentiation. It's all about the value that we humans assign to what's considered "an original", and I think that's what's happening with NFTs today. Unlike tangible art, however, I think NFT art is much more volatile and prone to the Beanie Babies effect if its popularity wanes.

In that scenario, trust shifts to somewhere the U.S. cannot easily regulate. In case of crypto, that can just be banned and rendered useless, as long as the rest of the world is USD-bound.

If a crypocurrency becomes popular in another country using another currency to on- and off-board, see my comment.

It would take a miracle for cryptocurrencies to suddenly replace fiat without being bound to any fiat currency. Essentially, all the world would need to switch trust at once.

The (U.S.) dollar is backed by the U.S. Army and always will be. Confidence decreases? The U.S. will likely start a war with the country whose currency tries to replace it (on "national security" reasons).

Fiat will always be backed by military force.

Like I said, it's shorthand for writing the whole CSS. How many lines of pure CSS would it take for `md:font-medium`?

Tailwind can do what you're describing via the @apply function.

Just write your CSS selector to target whatever you'd like, then use `@apply tailwind-classes md:other-tailwind-classes` inside the brackets.

This way, it's just a set of shorthand tags that replace the long-form CSS props, but it's still useful for quick design work.

"Nacho server" (not your server) also works.

I Ctrl-F'ed for Twist, made by the team at Todoist, but couldn't find it.

It has a way to go, but I found it the right mix of persistent, long-form discussion and decision making using Threads, and sync communication using Messages. It's the best of both worlds, if you can educate a team to use it properly.

Unless the parent was being sarcastic on purpose, this is exactly what the company is proposing to do, automate TL;DRs.

You might be thinking of utility classes as the finished product. They're incredibly useful for quickly prototyping and "jiggling" things until they look good.

Once that's done, the utility classes can be extracted to reusable CSS via the `@apply` directive.

A Hall sensor on each window (aka open/close sensor), plus temperature sensors in each room and one placed outside.

When the window is closed, but the outside temperature is lower that inside, it sends a notification to open the window. The opposite happens when the outside temperature exceeds the one inside, unless the window is already closed.

This is all written in Python via appdaemon since it's easier than defining the same automation via the UI (although that's also doable nowadays).

I use Aeotec Z-Wave Multisensors permanently connected to USB power (they can also run on battery). However, any PIR motion sensor would work, such as the cheap models from Xiaomi (but there's the extra cost of battery changes).

I use a Z-Wave 6-in-1 multisensor from Aeotec in each room, strategically placed in the corners so as to cover only motion in a single room. That takes care of motion sensing, temperature, humidity and luminosity (not used for automation, purely informative). The other two are UV and vibration sensors that are not as useful.

Setting a short motion detector rearm time lets me start a decay timer for the light that just turned on. If no motion is detected again, it starts lowering the intensity gradually over 10 minutes and finally turning the light off. I added a button in HA to override this and keep the light on when needed.

kevinsundar below is entirely correct, that's how I have mine set up as well. However, instead of network detection, there are multiple GPS-based device tracker methods for proximity.

AppDaemon would be great for that, as the callback methods it requires for listening to state changes or scheduled timer can be independently unit tested and debugged.

Any discussion of Home Assistant should start with the founder's vision, which I found very clear: https://www.home-assistant.io/blog/2016/01/19/perfect-home-a...

The purpose of Home Assistant is to first observe all data flowing through your house, by connecting all existing sensors, switches, gateways and anything else that has a digital pulse.

The second step is control, having centralized access through a web or mobile app to all moving parts of a home.

However, the power of HA comes from the third step: automation. The best interface is the one you can forget exists.

I've been running HA for over two years. Aside from being lazy about upgrading to newer versions and adjusting to breaking changes, it's been working great and has spoiled me and my wife. We now expect every house we visit to automatically unlock before we reach the door, for the lights to turn on (and gradually off) automatically as we move through rooms, and for our phones to notify us when the best time to open a window would be, to naturally cool during the summer. It's great to have cold light during the day and warm, lower level light as the evening progresses.

Together with the Python environment provided by appdaemon, there's almost no limits to what you can do, provided you instrument your house with sensors and switches as best as you can.

If you speak a little Python, you should look into appdaemon, it's a developer's (non-UI) way of doing the same.

This is essentially a souped-up https://portier.github.io/

I applaud the initiative, since it removes the couple steps it takes a user to reset their password via "Forgot password" flows. However, this type of auth should really be self-hosted or baked into the most popular frameworks, instead of provided by (yet) another third party you'd have to trust with your users' email address (at the very least).

It's actually easier. Cheating can be discouraged via real-time chat sessions, while async communication like emails or essay-style discussions can be scored via an NLP library like spaCy. If a machine can understand and parse the candidate's writing, chances are it's valid English.

All three metrics you mentioned can be evaluated using writing. In fact, writing makes up most of the communication in a remote environment.

Day 1 What have you learned from users? Nothing yet, haven't talked to any

There's your problem. You're building a pet/side project, not a startup.

Hey, that already exists (at nation-level): https://en.wikipedia.org/wiki/Special_drawing_rights

I believe it refers to assembling things digitally without thinking about how an actual human would work with the same things in the physical world.

Motivation is a highly personal thing, but perhaps I can help you with that hurdle.

Have you explored https://www.pubilling.io/ or the open-source http://killbill.io/?

I'm not sure what Square charges, but a regular POS from your business bank would be far, far less in percentage for in-person, card-present transactions. I've seen 1.5% figures here in Europe.

So far, Stripe seems to have lowered the fixed fee from 30¢ to 5¢ and dropped 0.2% off their payment gateway fees.

It appears there's a Javascript SDK listed as available.