I jumped on this at first as well. But to be honest if their target demographic is industrial production of coffee like beverages (like those Star Bucks soda can ”coffees”), well then it might not be so bad. I was thinking that a lot of flavour compounds of espresso breaks down quite rapidly while the drink cools, so the method of cooling all drinks to equal temperatures could be enough to skew the results regardless, but again for commercial coffee based soft drinks this is already the case. Headline is a bit misleading though.
According to the article they see the main use for industrial scale production of coffee/espresso based drinks, in that regard it does make sense. For home use not so much even if there could be some niche market for cold espresso drinks at home, using less ice would allow for less dilution and faster than prepping and then refrigerate the coffee. I sometimes put concentrated ice coffee into my whey/oat shakes, but this is indeed very niche use even for me.
Isn’t the problem that it’s supposed to not execute commands without strict approval but the shell stdout redirection in combination with process substitution is bypassing this.
You probably know this but it’s possible to buy a controller card for the panel on Ali Express and retro-fit into the case and use as a monitor if you are ready to retire the computer itself.
I’m contemplating doing this myself at some point but my maxed out 2019 iMac upgraded to 128GB ram and extra SSD is still plenty fast for me, actually feels subjectively quicker than my M2 Pro MacBook Pro with significantly less ram feel. I was a bit surprised as I had read all the hype of the responsiveness of the Apple M-machines.
Interesting, does anyone have a list of known providers vulnerability to this in the past? I'm thinking big providers like G-Suite, Office 365, Zoho, Fastmail, etc.
I can only talk from personal experience I did not trust most online payments around the turn of the millennium, but I did order quite a few things online. I usually payed either by collect on delivery or by invoice like regular good old fashioned mail-order, or by the early 00s VISA had something called e-card or similar, where you could generate a temporary one time use CC via a Java applet, this card was only valid for a day and could only be charged by a pre-determined amount, making the risk very low.
From what I can see this doesn't contain any kind of permission model, or authentication. At least what I could see in the documentation. I would say that RLS is one of the big killer features for postgrest which makes it so great for rapid prototyping something that's actually useful when exposed to the open internet.
I have a side project where this would fit perfectly. I’ve for a database in Postgres and my plan have been to sync the data into a local SQLite for a react-native app which needs to work offline and with flaky connections, to then later sync it back into PG. I have never gotten around to actually build the sync and it looks like this could solve that problem.
Does this play nice with RLS? I’m running everything on Postgrest at the moment.
Would you mind sharing this? I’ve only used expo for experimental non-production apps so far but it works be great to be able to do this if ever needed. Reading this thread makes me a bit more hesitant about using expo.