1,736 karma · joined June 1, 2013
I wouldn't be surprised if it was still in use now.
(Which does seem to show off the lack of lag and responsiveness)
Pretty neat the way it went from crazy hyperspace to a gentle, peaceful floating in the air!
[0] https://cpc.farnell.com/tekview/powertxtuk/gsm-power-socket-...
One thing I noticed, when I did the rectangle demo, I’d click on the “123” to input a number, but my phone showed the full keyboard, would be nice if it defaulted to numbers for that. (Obvs it’s not designed for a phone but I assume the same on a tablet?)
Just skimming the docs, can you add a job directly via the DB? So a native trigger could add a job in? Or does it have to go via a client?
Lots of options that are useful, and pretty good UI for setting things up
But yes, those are common scenarios, and most services that offer calling a webhook have retries baked in for such things. It is the responsibility of the consumer to verify if they have already received a message or not.
You should not be consuming a webhook 'live' and attempting to work on it the moment you receive it - that way lies dragons!
I have dedicated endpoints for services to send to, and they are verified and consumed as quickly as possible and put into a queue to be processed after. That way I can at least see what was sent, and if we missed something.
I use it daily for Github/ssh in general - and the 2 slots are used for part of passwords for a couple of other things.
I have a couple that are used daily, one in a safety deposit box (which is the "master" key), and a stack of new ones on my desk in case anything breaks. (I used that Cloudflare offer to get a hefty discount on them).
I also have a paperkey copy that lives elsewhere.
It’s quite cool just how far you can get with postgres
style="border-radius: 5px; border: 1px solid #2563eb; background-color: #3b82f6"
Personal choice obviously, but I work with frameworks and components if I'm doing frontend stuff, so having things as a single name for something that is consistent across everywhere I use it makes it easier for me.
It's not for everyone, and that's cool.
Being able to think "Hmmm, I want a rounded button, with a border and a blue background" and just typing class="rounded border border-blue-600 bg-blue-500" and it's done.
With lots of UI being components now, it doesn't really matter that it is verbose - I actually find that helpful. And even if you want to have a class that you use all over the place, just use @apply and create a custom class that you can use anywhere.
One place it can be hard to use, is if you have a specific design system - then yea at that point you either work with Tailwind and modify the config to match, or you just go with standard CSS - but at that point it probably makes sense.
I'll give you the image uploads/embeds - it really can be pot luck if it works or not
I’d say the amateur is the one who mastered the hammer and thinks everything is a nail.
Edit: rather, not realised yet that everything is not a nail