34 Matching Annotations
  1. Aug 2020
    1. I went against the grain, applying other tools that people have written over the years to directly perform the job at hand which do not involve entering a program for awk or a shell to run, with answers like https://unix.stackexchange.com/a/574309/5132 and https://unix.stackexchange.com/a/578242/5132 . Others have done similar. https://unix.stackexchange.com/a/584274/5132 and https://unix.stackexchange.com/a/569600/5132 are (for examples) answers that show alternative tools to answers employing shell script and (yet again) awk programs, namely John A. Kunze's jot and rs (reshape), which have been around since 4.2BSD for goodness' sake!
  2. Jul 2020
  3. Jun 2020
    1. Using OpenBTS, which we will be including in FreedomBox soon, and with cheap additional hardware, a FreedomBox can talk directly to GSM handsets, to provide alternatives to commercial mobile services.
  4. May 2020
    1. Not merge the values of the keys.

      This is one of the biggest limatations of <<: *anchor: it overwrites values of keys. It's too heavy-handed and therefore of limited use. You can only use it if you don't mind keys getting overwritten (such as if you are going to overwrite the keys below the <<:.).

    2. GitLab will perform a reverse deep merge based on the keys
    3. It’s an alternative to using YAML anchors and is a little more flexible and readable
    1. examples, listing both the conventional systems and their counterpart systems: Conventional schooling Home schooling Encyclopedia Britannica Wikipedia Microsoft Office Open Office Taxicabs Uber Hotel chains Airbnb Big-box stores Ebay National currency Cryptocurrency
  5. Apr 2020
    1. Take a moment to consider the alternative. No, not the IT department's fantasy world, that never-gonna-happen scenario where you create a strong, unique password for every account, memorize each one, and refresh them every few months. We both know it's not like that. The reality is that in your attempts to handle all those passwords yourself, you will commit the cardinal sin of reusing some. That is actually far more risky than using a password manager. If a single site that uses this password falls, every account that uses it is compromised.
    1. there's no reasonable way to communicate effectively with the less technically minded without acquiescing to the nontechnical misuse of the term "hacker"
    2. The more easily relabeled of the two uses of the term "hacker" is the malicious security cracker: it is not only the more recent phenomenon to acquire that label, but also the one whose meaning is most easily evoked by an alternative term. This is why, when you read an article of mine that talks about malicious security crackers, I use the term "malicious security cracker"
    1. Not everybody uses rubygems as their package management system. If this sounds odd to you, read https://gist.github.com/54177.
  6. Mar 2020
    1. 27$/year

      They spell it "27$/year" instead of "$27/year". I love it that they bucked the useless convention of putting $ sign first and did it the way that makes more sense. We've all had that thought, why do we say it "27 dollars" but write it, "dollars 27". It just doesn't make sense.

    1. I usually write in Google's online word processor Google Docs, even when noting the company's shortcomings. This article is different: it was drafted in a similar but more private service called Graphite Docs.
    1. If these asset owners regarded the “robots” as having the same status as guide dogs, blind people or default human citizens, they would undoubtedly stop imposing CAPTCHA tests and just offer APIs with reasonable limits applied.
    1. Q. Why does Rubinius not support frozen and tainted? A. Rubinius has better features; frozen and tainted are considered harmful. To elaborate... Both frozen and tainted depend on strewing checks throughout the source code. As a classic weak-link system, only one of those checks needs to be misplaced for the guarantees offered by either to fail. Since the number of checks is high, and as new code is written new checks need to be considered, the features inherently constitute unbounded complexity and unbounded risk.
    1. You could try AoE (ATA over Ethernet, very fast since it's Layer 2 protocol). SSHfs is yet another option (fast setup and encrypted by default). Or iSCSI (wich is tricky to setup).
    1. This might not be the most user-friendly solution. But it’s certainly creative and something different from your typical captcha systems. Pennyauth aims to verify your users by asking them to pay $0.01 per login. Payments are processed using QUID — and users can submit payment in as little time as it takes for them to grab their credit card.
    1. If you ever need to work with external translators, it’s a bit of a pain sending both your YML files and a bunch of views like index.en.html.erb. For one thing, you need some code to find all those files and send them, and put them back after receiving the translations. For another, your translator must respect the markup and code of the template, and know not to translate them. And if you want to use tools like WebTranslateIt, it’s easier to stick to YML.

      Good point. Better to store translations in your I18n backend in the same place as your subject translations, etc. (which by default is in YAML file).

  7. Dec 2019
    1. ReST

      "ReST" instead of "REST". I like how this way matches the case of the actual phrase that it's standing in for "Representational State Transfer", so you can better tell which letters are the beginning of words (all but "e").

  8. Nov 2019
    1. REST and GraphQL are wonderful tools to create an API that is meant to be consumed by third parties. Facebook's API, for example, is consumed by ~200k third parties. It is no surprise that Facebook is using (and invented) GraphQL; a GraphQL API enables third parties to extensively access Facebook's social graph enabling them to build all kinds of applications. For an API with that many consumers, GraphQL is the fitting tool. But, to create an internal API (an API developed and consumed by code written by the same organization), RPC offers a simpler and more powerful alternative. Large companies, such as Netflix, Google and Facebook, are starting to replace REST/GraphQL with RPC for their internal APIs. Most notably with gRPC which is getting popular in the industry.
  9. Sep 2019