edibleEnergy

needs <map> tags

dang, that is slick! (Apple M1 Macbook Air)

I listened to a very good 'In Our Time' podcast episode about Paul Dirac recently: https://www.bbc.co.uk/programmes/m000fw0p

Dang that's some list of options :D http://git.savannah.gnu.org/cgit/parallel.git/tree/src/paral...

Heya, I really like it :) Like the top comment currently though I have a hard time with the font. Everything else seems great!

Title of the post is not right, the author issued a (technically important) correction[1]:

> Brief correction: Cookies seem to get removed and re-created immediately. At least the cookie content and creation date seems to change. Nonetheless: After hitting the "remove all" button you still don't end up with an empty cookie jar.

[1]: https://twitter.com/ctavan/status/1044543955457773573

I've used YAML for years, and yeah, there's a lot of warts, but I love it for small(ish) manually edited configuration files. I generally keep it simple and it works.

The GDPR explicitly does not set out to specify implementation details because of the reasons here: https://gdpr-info.eu/recitals/no-15/ (Technology neutrality)

The latter. I don't have specific examples in mind, just that if you do not trust a company's data collection policies, the collection capabilities of an installed program are much greater than when viewed through a web browser. See [1] for an example from a few of years ago.

[1]: https://gizmodo.com/facebooks-messenger-app-logs-way-more-da...

Hi John, just an FYI: if you have Facebook Messenger installed on your phone, you are probably giving Facebook a lot more data than you think.

Somewhat tangential to this particular issue, but this is a good lesson for developers in why you should be dry and explicit in your writing.

Sure `alert("FFFUUU WHY U NO WORK");` keeps you entertained for 5 minutes while you debug a problem but when that accidentally gets to prod...

Sure, https://perldoc.perl.org/perlpolicy.html#BACKWARD-COMPATIBIL... that’s the policy for the language itself, but as it mentions there it’s considered generally a “community” virtue. I wasn’t programming back in 02 so I’m sure it was extremely different (and the source I’ve read from modules from that era is pretty frightening. Any major framework or generally used module will try to maintain backwards compatibility at least as far as documented behavior. I’ve never come across the kind of stuff I see all the time with node and go and python; package maintainers changing parameters and such because they weren’t happy with the original API.

What this article arrives at is basically the perl/CPAN model. Don’t break backwards compatibility unless you absolutely have to; as in cases of security or when the original functionality never worked in the first place.

Thanks for writing Ack petdance! Nowadays I typically use 'git grep' but I still use ack a good amount.

It'd be scanned years later if the USB drive I've backed it up on for regular infrequent use goes kaput on me ;)

The replacing every year or so sounds like the most robust way to do it with current best practices but that requires a lot of maintenance.

https://github.com/4bitfocus/asc-key-to-qr-code looks like it is trying to do that, though the issues on the repo suggest it might not work 100%, which is kind of a deal-breaker.

I was just (re-thinking) about this at work.. Just bought a Yubikey and was basically going to start from scratch with my PGP setup.

I really don't like the idea of storing anything really critical on a usb drive or an airgapped system.

I don't have an airgapped computer just laying around that I can store secrets on (and keep alive), and I don't trust a usb drive to last.

I really wish there was something like a clean way to store an encrypted printout that could be scanned years later if neccesary, ie a method of storage that I actually have faith would reliably survive for a decade or more.

The lack of a property manager also struck me as crazy and I've never been a landlord. Plenty of rentals have gotten trashed and city fines accrued long before airbnb existed. Doesn't sound like this stuff happened overnight.

I blogged about a fun one a while ago[1], pornhub using WebSockets to dodge adblockers.

[1]: http://blog.bugreplay.com/2016/11/pornhub-bypasses-ad-blocke...

Screen binding to ctrl-a and tmux users binding to ctrl-a so it feels more like screen is a bad idea imho. Ctrl-a (move to start of line) is one of the most convenient key combos on the command line. I bind my tmux key to ctrl-s, because I have never needed to freeze my screen.

I'm excited for the whitespace stripping heredoc operator, it's always a bummer having to put all heredocs all the way left.

This is the only place I've found them parsed and documented: http://peter.sh/experiments/chromium-command-line-switches/

Related ProPublica data visualization: http://projects.propublica.org/louisiana/

Like any feature, there's a lot of weird edge casey parts of SRI that can be abused.

We blogged about Adblock detectors over here[1] a couple of months ago for BugReplay[2]. A major Adblock detector FAdBlock was using subresource integrity to detect whether it's payload was being blocked, ie when adblocker was blocking it from being loaded.

[1]: https://blog.bugreplay.com/2016/11/fkadblock-how-publishers-... [2]: https://www.bugreplay.com

There's really no legitimate reason why twitter allows follows via their API[1]. I'm not sure if they see some benefit from allowing spam-follow bots to run wild or what they could possibly be thinking.

[1]: https://dev.twitter.com/rest/reference/post/friendships/crea...

I think the skill difference comes down to learning to write code vs learning to run code. Testing, manual or automated, involves executing your software, whereas often while coding you've only ran the code enough times to make sure it does what you expect of it most of the time.

Plug: we are in private beta with Feedback[1], the customer support version of BugReplay[2]. We integrate with Zendesk aside from our standard custom JavaScript integration.

In short, it's a product for Web development teams to collect perfect no-hassle bug reports from their users with all the details (video, network traffic, js logs) required to analyze and reproduce a problem.

[1]: https://www.bugreplay.com/feedback-by-bugreplay

[2]: https://www.bugreplay.com

Very cool demo. We did a demonstration of PornHub using WebSockets to bypass ad blockers[1] a few months ago., though that's more WebSocket-fallback development ;)

http://blog.bugreplay.com/post/152579164219/pornhubdodgesadb...

My first major project with Go was BugReplay[1], and I had pretty much the same experience as the author. As someone with a lot of perl and python experience the idea of how restricted the language is stylistically initially seemed like a stumbling block but quickly turned into a huge asset.

Now when I go back to python or perl (or javascript) I'm super conscious of the choices I make regarding type checking and parameter checking.

[1]: https://www.bugreplay.com