boffinAudio

.. promptly forget that you did this, or where you put the file containing the custom shell function, etc.

Ctrl-R serves a mnemonic purpose as well.. it helps you document your workflow and processes at the shell, and not hidden in some file somewhere.

Where does it live? In a .bashrc I have to maintain? The point is, not having to create an alias or function, because the tool lives in history.

None of these are that complicated that they deserve a dedicated shell script and chmod'ing, or presence in a cloneable repo, etc.

I so rarely see my (oft-repeated) favourite BASH script hack - commenting ones command lines:

    $ mv -n ~/Desktop/*.pdf ~/Documents/PDF_Archive/  #pdfsync

This command, which sweeps all the PDF files off my Desktop into a PDF Archive, is easily recalled with the key-combo Ctrl-R "pdfsync" - this is very convenient because it doesn't require me to add a custom shell script anywhere, in any particular path, and can also be used to refer to combinations of commands, for example:

    $ for i in some_collection_of_git_repos/ ; do ; pushd . ; cd $i ; git fetch --all ; popd ; done #refreshgits

Ctrl-R "refreshgits", and voila: all of the repos I'm interested in get a full automatic refresh ..

Command commenting is my favourite trick to teach ops newbies, too .. right after they learn about just how important "history > some_history.txt #historylog" is as a command, as well ..

Hey, that ghost peering over your shoulder has a really gnarly smile.

You can add the popcorntime plugin to stremio and get the best of both worlds.

No, it runs on everything.

There is no evidence that stremio uses subliminal methods.

Stremio OS is a good open-ended solution to the problem of non-active torrent users. In the existing desktop client, the user only participates while watching a particular stream - but with Stremio OS, the capability for torrent participation is a lot more viable.

Watch for an update to Stremio in the near future with a toggle for 'participate in torrent sharing while not watching' ..

No it isn't, it leaks data to Apple whether you opt in or not.

Tell me you've never been to the Kimberley desert without telling me you're a regular tourist ..

>Nobody in my circles seemed to think the polygraph was anything but a tool.

Just like the e-meter.

>buearacracy

Yeah, that's a cult.

So the intentions are part of the dowsing process, and the science has not caught up with that yet.

>Everyone who believes in it agrees it works, but not how it works? That's a classic sign of witchcraft.

No, its a sign of incomplete scientific investigations. Or are you going to tell me everyone knows how SRRI's work, to take the most overt example of incomplete sciencey/witchcraft?

(We don't know how they work, just that they do work, so hey .. ship the pills, witches ..)

Oh, this is so great - thanks for sharing, I'm going to dive deep into this crazy, weird, Postscript rabbit hole ..

(Been reading POC||GTFO for years, but now I finally think its time to write something..)

This is surely either derived from the Alchemist Owl's POC||GTFO musings, or destined to be included in them at some point in the very near future.

https://www.alchemistowl.org/pocorgtfo/

I'll never get my head around the fact that a language that started life as a way to accurately draw things on a printer and on a screen, is capable of being used for full-fledged applications such as this - although I suppose it makes sense, its still just too weird to me.

What's next? A full-blown desktop OS in Postscript, which is also the User Manual?

I sure freakin' hope so .. ;)

Its easy to "prove" dowsing doesn't work - all you have to do is not find water.

Wikipedia is not a source of truth - only collective associative reality.

Done precisely that with random Monte Carlo digs on a site, didn't find water.

Switched to dowsing, found water within minutes.

That its a cult.

A generation of Americans have no idea what the commons is.

How is it available if libuv?

I wrote an app (MIKME) which does this - the apps purpose is to allow remote recording with a self-powered bluetooth microphone, so you can have "point-source" audio for your video projects - leave the microphone with the subject, but move the camera around..

It wasn't that difficult to get audio/video in sync .. I just used AVFoundation, which has plenty of functions for dealing with the sync issue. The biggest problem was getting the recordings off the microphones filesystem to the iOS device - we had to invent a new protocol for this ("lost and found protocol"), because Apple sure don't make it easy for devices to share data .. but once the files are copied, the sync is the easy part.

I still have one that I use as a raspberry Pi workstation, and yeah .. you have to maintain those cables.

Still, a great device to have around a pile of rPi's.

Although, I do prefer to just use my external LCD monitor .. far less likely to destroy the cables.

Always, always, always start your new embedded project in a Virtual Machine. NEVER MIX TOOLS ON THE SAME SYSTEM.

This has been the #1 cause of quality issues for my (commercial) projects.

If you start a project with a new chipset, with a new vendor - build a new VM, install the vendors tools (and only the vendors tools) in that VM, and do your builds from there.

Do your hacking on your own (non-VM) machine, sure. That's perfectly fine.

But ALWAYS use the VM to do your releases. And, for the love of FNORD, KEEP YOUR VM IN SYNC WITH YOUR DEV WORKSTATION.

Disclaimer: currently going through the immense pains of dealing with a firmware build that absolutely has to be fixed while the original dev is on vacation - nobody can get into their workstation, the VM prepared for the task is 6 months out of date, and the customer is wondering why they should pay for the whole team to do something that one very special programmer is the only one on the planet can do .. grr ..

Whats wrong with tkinter? You're negative experience can't possibly be the standard by which 15+ years of productive use of it is to be discarded .. perhaps you haven't learned how to make beautiful UI's with it, but some of us have ..

You can easily go from Figma -> tkInter code -> app, too.

Thanks, fixed.

I just write GUI's in tkinter (python), build a single .exe with nuitka, and interface with generalized application functionality either as a .dll or python module ..

tkinter may not be the sexiest way to do things, but its definitely productive in terms of the code-compile-distribute methodology, and it is very easy to wire up to a generalized 'daemon'-style abstraction, where the app logic is implemented as a daemon, sent application commands over a well-greased socket.

With this architecture, I no longer care that its Windows underneath - this is just another platform target - and can easily use either MacOS or Linux as the development environment, needing only to test on Windows, ultimately.

Anything beyond the sphere offered by tkinter is just less appealing. If I have to start treating a platform target in any kind of 'special' way, I just lose interest in that target, as a whole - however, from a UI perspective, Windows tkinter support hasn't been that bad, and generally keeps up fine.

(Disclaimer: if I really need performance, I also use the JUCE framework for my needs - even though its an audio-centric framework, you can build GUI apps with it just as well, and its also a cross-platform way to do things in pure C++ ..)

I'm a huge fan of the Opener Blackfly, which has been physically designed for VTOL-like performance while providing a very simple flight mode during the transition from level to VTOL:

https://evtol.news/opener-blackfly/

The angle of attack of the lifting surfaces is intentionally offset so that, when the Opener reaches certain speed limits, aerodynamics take over and the plane switches modes automatically, without requiring much pilot input.

I can't wait to see these things buzzing around the skies - imho, this is the closest to 'the flying cars promise, fulfilled' so far ..

Whenever I need to do network things in Lua, I refer to the turbo.lua framework, which I've used in the past on other projects and I just find it so useful:

https://turbo.readthedocs.io/en/latest/

Whether its a set of file descriptors, a network socket, or some higher level session abstraction, I can usually find the 'best' way to deal with it by inspecting the turbo.lua sources - or, if feasible, I just use turbo.lua for the application on the table. It has been a seriously valuable tool in the 'get some networking/signals/fd_set thing working as quickly as possible" department.

Not that I'm suggesting the author switch to it, just that there is already a battle-tested and well-proven Lua-based framework for these things, and its worth investigating how it manages these abstractions. The distinction between local and IP sockets is well managed, also ..

I have a Model 100 that I regularly use for writing purposes ... its kind of cute to have it wired up to a raspberryPi for whenever some server work needs to be done, too ..

Would surely be nice to see a re-invented M100 out there. ClockworkPi came close, but it was disappointingly diminutive ..