692 karma · joined April 9, 2016
String signature = "POST" + "\n" + "/api/v1/..."
and String signature = "POST\n/api/v1/..."
don't result in identical variables, so I'm a bit puzzled why that would result in an error.However, there's a quoting error in the failing example where the double quotes in the JSON body aren't properly escaped:
String signature = "POST" + "\n" + "/api/v1/query" + "\n" + token + "\n" + timestamp + "\n" + "{"body":"content"}"
It may just be the example that's not correctly formatted, but the other (working) example does in fact escape the double quotes in the JSON. I guess, depending on how forgiving the used language is with quoting, that could also be the source of the error?It's very much like that article from Daniel Stenberg (curl developer): The I in LLM Stands for Intelligence: https://daniel.haxx.se/blog/2024/01/02/the-i-in-llm-stands-f...
Like, I'd have to remember both `prettypath` and `sed`, and given that there's hardly any chance I'll not need `sed` in other situations, I now need to remember two commands instead of one.
On top of that `prettypath` only does s/:/\\n/ on my path, not on other strings, making its use extremely narrow. But generally doing search and replace in a string is incredibly useful, so I'd personally rather just use `sed` directly and become more comfortable with it. (Or `perl`, but the point is the same.)
As I said, that's obviously just my opinion, if loads of custom scripts/commands works for you, all the more power to you!
Pretty convenient that the source was taken down before the blog was posted and it doesn't seem like we can get a hold of it.
Edit: MalwareBazaar doesn't seem to have a sample either.
However, I think OP might be using WSL and I'm not sure that's available in Sandbox.
So, sure, if you want to play it super safe, quote keys as well. But I'm personally fine with the trade-off in not quoting keys.
Yeah, that was my first thought as well. I personally don't mind YAML, but I've also made a habit out of quoting strings. And, I mean, you're quoting both keys and strings in JSON, so you're still saving approx. 2 double quotes per key/value pair in YAML if that's a metric that's important to you.
Is there any way to support the development — financially or otherwise?
Could also be that 0launcher has changed over the past four or five years.
Besides being a good, very simple, minimalistic launcher, it's also Open Source (https://github.com/tanujnotes/Olauncher), ad-free, and collects and shares no data.
I'm not sure why we have that obligation.
If it's supposed to do commit + push in one press, then I wonder how it handles commit messages?
Vimium mainly gives you keyboard navigation, but QuteBrowser removes the address, tab and bookmark bars and instead gives you keyboard access to everything via the very Vim-like status bar at the bottom. Incidentally this also frees up quite a bit of vertical screen real estate, which is a big deal to me. Browser settings, scripts, etc. are also all accessible via the keyboard — Vim style.
Edit: The lack of a solid Bitwarden integration in QuteBrowser is kind of hurting though.
First of all, the sound is fine. Nothing exceptional but certainly not bad. I'd say they compare pretty well to my Beyerdynamic DT 770 Pro (80 Ohm) or my old Sennheiser Urbanite XL. They also sit pretty well on my head for extended periods of time, which is nice, but will obviously vary from person to person. They don't have any fancy Teams-integration, which is a plus for me but a deal-breaker to others. They hold battery very well. I haven't tested it in depth but I've used them for maybe 3 full workdays without charging them, so maybe around 24 hours of active use and they still had some juice left.
But the firmware... What a disappointment. The headphones have 3 settings, ANC, ambient and "normal". I personally prefer "normal" but the headphones don't remember the setting across restarts, so every time I turn them on I have to sit through the boot sound (because system sounds can't be interrupted), wait for the audio feedback to finish saying "connected", and if a second device is connected, "second device connected", then click a physical button, wait for it to finish saying "ambient sounds", and finally click a third time to hear it say: "noise cancelling off", and _then_ I can start using them. It's OK the first 5-10 times but then it just gets really, really annoying.
I went to their forums about a year ago to suggest it as a feature but learned that Fairphone actually don't interact with the forums, it's just user-to-user interaction, so suggestions don't really make it further from there. That's fair, so I contacted their support about it instead. They suggested that I contact the store that my workplace bought the headphones from. (I didn't think that was really going to solve the issue, so I chose to just ignore that.) They've released 2 firmware updates since then, but no storing mode across reboots. They did however manage to glitch out the boot sound in one firmware update, so it played 2/3 of the audio only to interrupt itself and play the second half of the sound again. The last firmware update fixed that at least.
And before someone suggests that there might be no place to store aforementioned setting, they can store bluetooth pairings and EQ presets on the headphones. The noise cancellation preference could be stored in less than a byte. Unfortunately the firmware isn't OSS so I can't even fix it myself.
/rant
"Cooked rice turns out to be a potential source of food poisoning. Raw rice almost always carries dormant spores of the bacterium Bacillus cereus, which produces powerful gastrointestinal toxins. The spores can tolerate high temperatures, and some survive cooking. If cooked rice is left for a few hours at room temperature, the spores germinate, bacteria multiply and toxins accumulate. Ordinary cooked rice should therefore be served promptly, and leftovers refrigerated or frozen to prevent bacterial growth."
I've always taken that to mean that it's fine to reheat rice as long as it hasn't been standing around for too long before refrigerating the first time around.
Edit: Hmm... PayPal seems to throw error after error at me when I try to donate. I'll keep trying.
I could easily be wrong though, I haven't done web development for years.
I don't see why we can't celebrate someone for doing something without having to mention everyone else who's also done something. No one is diminishing their contributions but they're not the topic of the article. If you want to write an article about them, I'm sure someone would be happy to publish it.
That, however, doesn't diminish Dai Vernon's or Erdnase's contributions, but yeah, not a competition.
Obviously the usefulness of measures like this is likely pretty low if your dealing with tech-savvy adversaries, but if some random border guard or police officer forces you to log into your computer and — I don't know, I'm not very well-versed in these scenarios — show your Facebook messages or your password vault, you could use your duress password to clear cookies and other stuff to show that you don't have a Facebook account or a password manager ... or whatever, you get the general idea.
Or you could use it to not change anything but simply log in and additionally alert your work place that you're under duress and they can cut off your access to critical systems. Provided that you have some sort of internet access of course...