I feel like a bit of a fraud because this was the PR that got me the "Mars 2020 Contributor" badge...
48 karma · joined March 18, 2014
I feel like a bit of a fraud because this was the PR that got me the "Mars 2020 Contributor" badge...
(Demo: https://asciinema.org/a/349330 )
Contains mostly guides on random things I learn over time and other bits of information I think should be publicly available.
Not very frequently updated, but RSS is available so it can be chucked in an RSS reader and forgotten about.
Ex:
logger.debug("A non-critical exception occurred", exc_info=True)One of the main gripes I do have with it is its reliance on the old-school %-based formatting for log messages:
logger.debug("Invalid object '%s'", obj)
As there are real advantages to providing a template and object args separately, this is a bit of a shame since it pushes people to use pre-formatted strings without any args instead.I fixed this for myself by writing bracelogger[0]. If this is a pain point for you too, you might find it useful.
Ex:
logger.debug("Invalid object of type {0.__class__.__name__}: {0}", obj)
[0]: https://github.com/pR0Ps/bracelogger[0]: https://manpages.debian.org/jessie/moreutils/chronic.1.en.ht...
Here is a demo of a small script I wrote that shows jq results as you type using FZF: https://asciinema.org/a/349330 (link to script is in the description)
It also includes the ability to easily "bookmark" expressions and return to them so you don't have to worry about losing up an expression that's almost working to experiment with another one.
As a jq novice, I've personally found it to be super useful.
I create these self-extracting packages all the time too. Getting the icons and such right on the package can be a bit of a pain so I made a quick script[0] to automate the process. You may find it useful too.
We also just embraced screen-peeking as everything was up on the same screen for everyone to see.
https://i.imgur.com/pnhyEjS.png
It was definitely a bit of a pain to set up each time. Something like a batch script that automates setting the emulators to a known-good config, configuring the controls, opening up the emulators, and starting the game would be possible and would make it a lot easier.
Even though it's been fixed since 2017 I can confirm that there's still lots of network-using software out there that isn't using the most recent Qt library. Installing any of it will destroy your ability to have lag-free video chats or do any other real-time streaming.
I've always been in the "wires wherever possible" camp and it's things like this that are keeping me there. Hopefully headphone jacks don't go totally extinct anytime soon...
[0] https://cmetcalfe.ca/blog/diagnosing-periodic-high-ping-time...
See https://cmetcalfe.ca/blog/forwarding-spam-with-gmail.html
Question for you since you presumably read their blog: Do you follow a bunch of blogs/news sources? If so, how do you do it without using feeds?
When I was setting up WireGuard on macOS Mojave it would connect but I wouldn't be able to load pages. Other devices didn't have any issues so the server config was fine. Turns out the autodetected MTU was too large and the packets were getting dropped. A dead giveaway that this is happening is that pages will (mostly) load over HTTP, but get stuck negotiating a secure connection over HTTPS. I'm guessing this is because of the larger packet sizes required to do the handshake.
Try setting to something really low like 100 to see if things start working and adjust from there.
Screenshot: https://i.imgur.com/F6w8Ixz.png (just took it now so I redacted some info)
It consists of 2 parts:
- a Python script to parse metadata from photos into json files and create thumbnails.
- A JS-based frontend that consumes the json files and thumbnails to provide a UI.
Features:
- Can be hosted completely statically making it ideal for low-power servers
- Serves up your photos in the same file structure as they are on the disk
- Works with many types of photos, including most raw files
- Parses and displays common EXIF data
- Works well on slower connections (minimal HTML+CSS+JS, small thumbnails, placeholders, preloads images as you view, etc)
[0]: https://www.reddit.com/r/NintendoSwitch/comments/87vmud/the_...
Same goes for the "Piracy and Copyright infringement".
There's no conspiracy here, just the normal incompetence. Calling the number listed on the page will probably allow you to petition to reclassify the site properly, making less likely to be blocked.
Of course, filtering in general sucks, but it's not like this is an ISP, it's a hotel.
However, compared to the amount of metadata that's already being leaked over SMS[1], adding the fact that you could[2] be using a specific SMS client that has the ability to encrypt messages doesn't seem too bad.
There was an option in a previous version of TextSecure to disable this tagging, but it was deemed unused and axed[3]. For the same reason, I'm loathe to add it back in, but having the option shoved under the "Advanced" menu may not be too bad.
[1] This is something that TextSecure does much better with. SMS messages (even encrypted) still leak metadata on who you're messaging and when.
[2] There's some element of deniability with whitespace tags (granted, not a lot). On the other hand, if you're registered with TextSecure (which can be checked simply by adding a user your contacts and opening the app), there's only one reason you would be there.
[3] See https://github.com/WhisperSystems/TextSecure/commit/40eca5e0...
We're using the same system we inherited from TextSecure for encrypted SMS: Trust keys implicitly on first use, while encouraging users to verify them out of band.
The verification is handled by providing a screen that has your identity and what you think the recipient's identity is. If the recipient's identity matches what your app says and vice-versa, then you know you're talking to the right person.
Ideally, the verification would be done in-person or via another secure means of communication. Currently you can verify identities by just reading them out, or via QR code.
The detection was actually inherited from TextSecure and works by "tagging" shorter messages with some detectable whitespace after the message contents. A bit of a hack, but it's a limitation of the transport.
Relevant commit: https://github.com/SMSSecure/SMSSecure/commit/93d94f2b7a9fd6...
If both users have SMSSecure, they can exchange keys and upgrade to an encrypted session.
Also, there's some amount of autodetection going on. SMSSecure will automatically prompt the user to start a secure session if it detects the recipient is also using SMSSecure.
But yes, if a user tries to start a secure session with someone who doesn't have SMSSecure installed, the recipient will just see a bunch of garbage (limitation of the transport).
To be clear, this project isn't endorsed in any way by Open Whisper Systems. We forked their codebase pre-v2.7.0 and are integrating upstream commits, but that's it.
The idea isn't to compete with TextSecure, it's to provide the encrypted SMS functionality TextSecure used to (with all it's compromises and drawbacks) for people that push-based messaging isn't an option for.