I worked for ByteDance in Singapore. People would show up for work between 10 and 11am, lunch would start around 11:45am or 12, then people would nap until 2pm at their desk. A good, focused engineer could produce the same output as these engineers while only working in the morning
Yep - I put that rule at the bottom so that everything I want elsewhere is sorted by some preceding rule. That's how unfuck works too, though.
My ruleset looks like this now:
To: (tix|orders)@domain | From: orders@* | Subject contains (pedido|order|sipariş|confirma) -> something I bought, to Orders
To: tix@domain -> to Tickets
To: travel@domain | Subject contains (tickets|billete) -> to Travel
(some specific mailing lists by sender) -> to Reads - those are the newsletters I want to read
From: *@(domains of banks I have) -> to Banks - obviously
From: *@linkedin.com -> to Linkedin; it's noisy but sometimes useful
Header list-unsubscribe exists -> to Ads
That's about it. I don't remember the last time something I didn't want reached my inbox, however I go to the ads and do a mass unsubscription every couple of months.
The easiest way I can think of is for you to join the Discord server.
Top right corner of the website (I'm aware that's not the best icon for it - addressed it to the team).
Shouldn't take long until Linux is up there, tho. I know the team started managing the build process.
Jfyi, I'm doing exactly this (and more) in a platform library; it covers the issues I've encountered during the last 8+ years I've been working with Go highload apps. During this time developing/improving the platform and rolling was a hobby of mine in every company :)
It (will) cover the stuff like "sync the logs"/"wait for ingresses to catch up with the liveness handler"/etc.
The docs are sparse and some things aren't covered yet; however I'm planning to do the first release once I'm back from a holiday.
In the end, this will be a meta-platform (carefully crafted building blocks), and a reference platform library, covering a typical k8s/otel/grpc+http infrastructure.
I'll check this out, thanks for sharing. I think all of us golang infra/platform people probably have had to write our own similar libraries. Thanks for sharing yours!
https://github.com/m-bain/whisperX looks promising - I'm hacking away on an always-on transcriber for my notes for later search&recall. It has support for diarization (the speaker detection you're looking for).
But overall it's pretty simple to do after you wrangle the Python dependencies - all you need is a sink for the text files (for example, create a new file for every Teams meeting, but that's another story...)
Any good solutions for capturing the audio streams and piping them where they're needed? (I.e both microphone and speakers. I was wondering if I needed to mess with pulseaudio and/or jack (I mean pipewire under the hood, but I think those APIs sit on top and might be clearer))
Never mind, played around a little, and pulseaudio's cli API makes it easy enough to sling some loopback/virtual devices around that you can then read from easily enough.
It sounds great, but they could also block the settings' switches in the pull-down drawer first...
As far as I understand, this whole Find My/Remote Lock stuff will stop working when the thief pulls the bar down and activates the Airplane mode. Then all the data is one vulnerability away from being accessed.
This is the case on Google Pixel 8 Pro and it's been there for ages; I assume it's the same for other vendors.
Having just changed out the battery on my trusty Note 20 Ultra yesterday, this made me smile as I imagined a thief evenly applying heat to the back edges of the phone, carefully prying the phone open with suction cups and a series of plastic picks, gently dislodging six fragile micro-connectors, removing 11 different nano-sized screws, removing the wireless charging antenna, peeling back layers of ribbon connectors, removing the speaker module, dripping solvent into the battery compartment and then waiting ten minutes for it to soften the battery glue so they can start prying the battery out.
Maybe somewhere during that painstakingly onerous process, they'll pause and ponder their life choices. I know I certainly did! :-).
>As far as I understand, this whole Find My/Remote Lock stuff will stop working when the thief pulls the bar down and activates the Airplane mode. Then all the data is one vulnerability away from being accessed.
Finding that "one vulnerability" is going to be pretty hard. The device is still going to be locked, you're very limited in what your exploit has access to. The common EoP used for rooting/jailbreaks are going to be out, because you won't be able to run arbitrary code on the phone. True, there are occasionally exploits in the bootchain itself (eg. checkra1n for iOS), but you could be waiting years/decades for it. By then the phone would be useless, and any juicy credentials already rotated. Best case scenario, you get some nudes.
I checked on my OnePlus 7 and indeed it's possible by default. There is a setting to disable access to the notification (/setting) drawer from the lock screen at least in Oxygen OS though.
Right. I just recently switched to iOS and was pleased to turn that on. It took a minute to remember why only sometimes I was able to access the settings pulldown until I finally realized I had to wait for face unlock to finish - I felt pretty silly when I remembered.
I'm surprised this isn't a feature on android yet.
This is also easily defeated by throwing the device into a foil bag until you are in a room with a faraday cage, or just a remote location without cellular service.
