Finally found official name enwp.org/False_dilemma for when people see N options when in fact there are at least N+1, of which the unconsidered options may be superior and considering only N options creates boxed-in thinking.
Examples: ATOM vs RSS (unconsidered: HTML), Tíu Dropar multiple tipjars, where competing tipjars blot out the option of not tipping.
Amazed to see that “send[ing] your password file to the server” is one of the examples in the curl manpage. wat. curl.haxx.se/docs/manpage.html#-F
Checked into Hakkavelin, HR
The other detail added to #taproot: #indieweb phoning via SIP and a “Call Me” button. On desktop devices you’ll see it on my homepage in the Elsewhere section. Clicking it on a WebRTC-enabled browser will start an audio call with me if I’m logged into a SIP client.
Next: using a Tropo app as a middleman for providing voicemail transcription and local numbers, improving/providing mobile UI.
After deliberating a little about how to “do” a composite homepage feed, whether or not I should forget about having “notes”, “music” and “articles” and just merge them all, coupled with the fact that I already use notes for replies, I have reached a simple conclusion, of which this post is the first demonstration.
/notes/ and what used to be “Notes” is now my de-facto dump for short-medium length chronological posts of all types. This covers notes, replies, checkins, short articles (basically named notes with more structure) and so on. Posts with a name live at /notes/DDD-name, those without names live at /notes/DDDSSS.
/articles/ retains all content which lived there in the past. Going forward it might become more of a wiki, or a place for very long things like Data Export.
/music/ will retain all it’s content, and be where I post standard musical notation tunes. Audio recordings of those tunes will be posted as audio posts with a link to the relevant tune.
Hopefully these changes, along with improved templating (post-type-specific DOM templates here I come) will make finding, posting and reading posts on #taproot a much more pleasant experience.
Working through some example circuit simulations I finally gained an intuitive understanding of the voltage divider equation — it’s just a ratio, but I had never figured this out before.
Given this circuit, where the voltage source is rated at 1V:
The voltage at A is equal to
1V·(R2 / R1 + R2), which is
1·(1/1+1) = 1·(1/2) = 0.5.
R1 + R2 represents the total resistance of the path, and as such the total voltage drop. Dividing R2 by the total produces a fraction representing the voltage drop over R2. Multiplying the input voltage by this fraction leaves us with the voltage dropped over just the R2 portion of the circuit, which must be VA because there are no other branches in the circuit.
Put another way, the equation finds the ratio of resistance (and so voltage drop)
R2:R1 and then feeds the input voltage through this. Here’s a more abstract visual representation of what’s going on:
Received some spam telling me my website needs a responsive layout. I wonder if @beep gets these emails.
“Fail Fast” is the trendy alliterative buzzword version of “have small feedback loops”, just less accurate and more prone to undesirable misinterpretations.
@thatEmil that should work fine — one thing to bear in mind is that by default they both treat redirects differently. IIRC, cURL doesn’t follow redirects by default whereas
I helped write a thing which crunches multiple millions of numbers, do I get to call myself a Big Data Scientist now?
SIP/WebRTC call-via-personal-site #tabdump:
Having a go at making Sumendi’s leche frita (fried milk). Just put the mix in the fridge, pretty sure the consistency is perfect, but I’ll find out for sure tomorrow!