Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Today it's awk(1)

Uncategorized
1 1 0

Gli ultimi otto messaggi ricevuti dalla Federazione
  • Il cuore batte spesso in solitaria.
    Ma va bene così, fa parte di quello strano, assurdo gioco che è la vita. Una maestra severa.

    read more

  • Ben Werdmuller wrote a new perspective on RSS. It's great, just what we need. RSS is of the web, and is the simplest most obvious way to get all the twitter-like systems connected.

    https://werd.io/why-rss-matters/

    read more

  • Making Glasses That Detect Smartglasses

    [NullPxl]’s Ban-Rays concept is a wearable that detects when one is in the presence of camera-bearing smartglasses, such as Meta’s line of Ray-Bans. A project in progress, it’s currently focused on how to reliably perform detection without resorting to using a camera itself. Right now, it plays a well-known audio cue whenever it gets a hit.
    Once software is nailed down, the device aims to be small enough to fit into glasses.
    Currently, [NullPxl] is exploring two main methods of detection. The first takes advantage of the fact that image sensors in cameras act as tiny reflectors for IR. That means camera-toting smartglasses have an identifying feature, which can be sensed and measured. You can see a sample such reflection in the header image, up above.

    As mentioned, Ban-Rays eschews the idea of using a camera to perform this. [NullPxl] understandably feels that putting a camera on glasses in order to detect glasses with cameras doesn’t hold much water, conceptually.

    The alternate approach is to project IR in a variety of wavelengths while sensing reflections with a photodiode. Initial tests show that scanning a pair of Meta smartglasses in this way does indeed look different from regular eyeglasses, but probably not enough to be conclusive on its own at the moment. That brings us to the second method being used: wireless activity.

    Characterizing a device by its wireless activity turned out to be trickier than expected. At first, [NullPxl] aimed to simply watch for BLE (Bluetooth Low-Energy) advertisements coming from smartglasses, but these only seem to happen during pairing and power-up, and sometimes when the glasses are removed from the storage case. Clearly a bit more is going to be needed, but since these devices rely heavily on wireless communications there might yet be some way to actively query or otherwise characterize their activity.

    This kind of project is something that is getting some interest. Here’s another smartglasses detector that seems to depend entirely on sniffing OUIs (Organizationally Unique Identifiers); an approach [NullPxl] suspects isn’t scalable due to address randomization in BLE. Clearly, a reliable approach is still in the works.

    The increasing numbers of smartglasses raises questions about the impact of normalizing tech companies turning people into always-on recording devices. Of course, the average person is already being subtly recorded by a staggering number of hidden cameras. But at least it’s fairly obvious when an individual is recording you with a personal device like their phone. That may not be the case for much longer.

    hackaday.com/2025/12/09/making…

    read more

  • @Zambunny ti abbraccio virtualmente, per quel che vale ❤❤❤

    read more

  • read more

  • In tutto l'ordine degli ingegneri non ne trovano uno che sappia far funzionare la PEC.

    read more

  • We report: all of the wind of these past few weeks has stripped the trees bare here. The ground is all mulch and rotting wood, and we are bound to get a foot stuck in there at some point tonight. With no leaves on the branches, and barely a breeze, the night is eerily quiet.

    read more

  • @SecurityWriter the first season took everything good about 80s horror and fantasy and teen movies, and the fifth season seems to be taking everything bad, including 30 year olds playing high schoolers. (This last bit I could forgive if the 30 year olds and the scripts were good, but they aren't, so...)

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    0 Views
    Today's #FreeSoftwareAdvent is all about XMPP.Snikket (https://snikket.org/) is an easy-to-install, and easy-to-administer, XMPP server. It is designed for families and other small groups. The apps for Android and iOS (based on Conversations, I think) are great.Dino (https://dino.im/) is my desktop XMPP client of choice.Profanity (https://profanity-im.github.io/) is a terminal / console XMPP client, which is incredibly convenient.Why not have a fun festive project of setting up an XMPP-based chat server for you and your family and friends?#XMPP #FOSS #SelfHosting
  • 0 Votes
    1 Posts
    0 Views
    Today's follow-up #FreeSoftwareAdvent entry is vi/vim.Which I use depends on the situation. Classic vi/nvi tends to be lighter weight and start faster, while vim offers extra features that I find particularly useful). I usually just type `vi` which gets me `vi` on OpenBSD, `nvi` on FreeBSD, and `vim` (or `vim-tiny`) on most flavors of Linux. If I specifically want vim features, I'll invoke it as such directly.I could go on for ages about favorite features, but a select few:• the ability to keep my hands on the home row and not use a mouse is helpful for preventing RSI symptoms• it's a language¹ of editing, involving counts, verbs/commands, and objects/motions, so I can express my editing *intent* and then use the period command to re-issue that same editing *intent*• the :global or :substitute commands can make massive-yet-precise edits across huge files• the :*do commands extend that power across multiple files, allowing me to precisely edit millions of lines across thousands of files with targeted precision• it's ubiquitous—even as some Linux distros have started removing ed(1) from the base installs , relegating it to packages, I can always type `vi` on any Unix-like/POSIX system and be editing with a powerful editor. And with builds for Windows and my phone, I can use it everywhere. No need to install anything• they work just fine over a SSH connection without a GUI, and use minimal resources so they work even on that old hardware from the 90s.⸻¹ https://gist.github.com/nifl/1178878
  • 0 Votes
    1 Posts
    0 Views
    Though a bit niche, my #FreeSoftwareAdvent today is ed(1). As the goofball behind @ed1conf, I certainly play it up, but I certainly use it more than the average Unix/BSD/Linux user.A while ago I wrote up list of reasons¹ why one might use ed, and some are more obscure/improbable reasons (though I've encountered all of them in that post), there are a couple of those that drive me back to ed regularly:• I can still see the output of previous commands on the screen while I edit, where a full-screen editor would obscure that output that I need to incorporate in my edit• it's just darn fast for a quick edit, changing a variable name or adding/removing an entry in a list, etc. No startup costs for a honkin' huge $VISUAL with dozens of plugins and language-server processes and GUI rendering• very usable on low-bandwith/high-latency connections like I sometimes get when I remote into machines (less of a problem now, but I still experience sessions where I'll SSH in, invoke ed, make the change, write & quit, and exit the shell, in a couple seconds, while the screen repaints things oh-so-slowly• and most importantly, there's quality geek-cred for using it in front of others 😆⸻¹ https://blog.thechases.com/posts/cli/why-ed1/
  • 0 Votes
    1 Posts
    0 Views
    Today's #FreeSoftwareAdvent entry: ledger(1) & hledger(1)I primarily use ledger use for my #plaintextaccounting purposes¹ but try to mostly keep my data-files in a form that hledger can process them too.Getting started involved a crash-course in accounting terms, but the use of positive/negative numbers (rather than "debits" and "credits" which always bugged me; though both have ways of specifying that output should be in credit/debit format) eased the transition.While it started a little tedious, a few helper-scripts and shell-functions simplified adding new common entries and gave me lazy access to common reports.I still struggle a little bit with closing the books (I though I'd figured it out, and documented it², but had some hiccups so I'll need to revisit my documentation in January)But it's been incredibly helpful to see and track our household net worth, spot trends, keep tabs on gift-card balances that would otherwise get forgotten, track invoices sent to clients, and it simplifies balancing the checkbook monthly.⸻¹ http://plaintextaccounting.org/² https://blog.thechases.com/posts/closing-out-the-books-in-ledger/