You can’t just share the same that walkways that humans share. Utilities need their own “staircase” up and down the floors. Otherwise, the cables that are anywhere visible will look “ugly” to the residents.
Interesting YouTube video where people are arguing over the spelling of a specific vocalized word. Yanny or Laurel?
20180517/https://www.youtube.com/watch?v=KM38OFDKU20
Very interesting. False phonemes heard when inconsistent visual and auditory stimuli are heard, and the various physical and cultural conditions that increase or decrease susceptibility.
20180517/https://en.wikipedia.org/wiki/McGurk_effect
Although when I listen to the clip, it seems more like differences in pronunciation.
Very interesting. rtfd.io is an actual legitimate website.
Basically it is just setup as a redirect to readthedocs.org.
Home network notes.
Important! Two different types of in-wall cable: plenum cable, designed to be run through ventilation ducts, and riser cable. The first has more stringent fire-code standards, the second less so but still more stringent than ordinary stranded patch cable.
20180517/https://en.wikipedia.org/wiki/Plenum_cable
Also, plenum cable is required for schools and hospitals under all circumstances. So if you have a question of whether to buy both plenum cable and riser cable, just go with plenum cable if there is such a requirement.
20180517/DuckDuckGo does plenum cable need to be used for cables that
run beside a heat vent
20180517/https://www.ecmag.com/section/systems/plenum-vs-non-plenum
Again, I reiterate, because this is important!
As I’ve mentioned earlier, all technology is part of a stack that has a top and a bottom: there are base technologies that are built off of, and there is a derived product technology as a result. And unfortunately, the way technology works is that there is always going to be duplicated work in this story of technological progress.
But, as I’ve also mentioned, not all duplicated work is effectively waste… just that most duplicated work is mostly waste. So, when exactly is the problem of duplicated work worse or better?
I will provide my personal judgement here.
-
When two technologies perform the same task, but each expose an incompatible symbolic interface to achieve that task, the problem of duplicated work is one of the worst.
- Every derived technology needs to, in fact, “invent” a symbolic format, symbolic language, or symbolic interface upon which higher level technologies can build off of.
-
By constrast, when the symbolic interface exposed by duplicate technologies is identical or otherwise completely backwards/forwards compatible, the duplicated works are among the best.
-
When the base technologies are the same or very similar, and the derived technology is essentially the same, the problem of duplication is going to be one of the worse ones.
So, more about the size of my notes. I said I started writing these in about the year 2010. That is true, but when I started, I wasn’t writing very much very frequently. By the year 2012, when I got my own dedicated GNU/Linux laptop, by means of refurbishing a broken Windows laptop refused by its original owner, is when things started to speed up.
But, this also deserves interesting discussion in other dimensions. By virtue of spending more time in the GNU/Linux system, this is also the time when I turned more and more toward learning about other people’s existing work, and building upon existing libre software, by virtue of having access to the source code to study and modify. Ultimately, what happened is that I spent a lot more time documenting things already developed by other people and a lot less time developing my own software from scratch. In the past, I’ve spent considerable amounts of time writing lots of code, and considerable amounts of time learning about APIs, but not so much time writing about other people’s work.
- Footnote: Again, I reiterate, because this is important! Why didn’t I spend much time documenting? Because the documentation I was working with earlier on was already so well organized!
Yeah, I did write a lot more code during those times than I typically do nowadays, even though it ultimately turned out to be a lot of rework that other people already did once before. However, sometimes it is useful to reinvent software already written by other people, just so that you understand different ways that the older, simpler version of such software could have been written. Suffice it to say, the law of diminishing returns applies here: it is not “useful work” in the purest sense of the term, but it still does help for smaller improvements that require much more work input.
Important! Again, I reiterate, because this is important! This is the original Markdown documentation and reference, which is still pretty good for modern use.
20180516/https://daringfireball.net/projects/markdown/syntax
Now what about that Daring Fireball website? It has a blog of its own written in Markdown, correct? Indeed, this is the case.
20180516/https://daringfireball.net/
Very interesting news here. Twitter is removing support for third party clients. Looks like Twitter is on the fall.
20180516/https://daringfireball.net/2018/05/the_end_of_third_party_twitter_clients
Oh, very interesting. GitHub updated their terms and conditions to make them more user-friendly, hence they are more practically enforcable.
20180516/https://help.github.com/articles/github-terms-of-service/
Oh, I didn’t know there were special U.S. laws rendering complications for web service operators when people under the age of 13 are involved. What is that law, anyways? Oh, this. Yep, definitely written with a one-sided mindset. And for GitHub’s side, they don’t want anything to do with those more complicated legalese, especially getting in trouble for not following them. Indeed! If you read their terms and conditions, they don’t say that users under 13 are prohibited from using Internet services in general; they just say that they do not target their service to users under 13, and as a convenient way to escape potential legal liability, they forbid such users in their agreement, even though it is totally legally possible.
- Footnote: Again, I reiterate, because this is important! But, the really interesting thing about all such laws that pertain to people under 13 years of age. In only a few years after any such legal dispute, the dispute will be irrelevant because the person in question will no longer be a member of the prohibited group. And you know the way legal disputes are: one year is considered “fast.” The 18 years of age laws have a little bit more legal wiggle room for disputes before they become obsolete. Ultimately, we must all agree that none of these laws are really… are really all that enforceable, but are written upon the assumption that people will avoid disputes to begin with.
20180516/DuckDuckGo united states law minimum age 13 internet
20180516/https://www.ftc.gov/enforcement/rules/rulemaking-regulatory-reform-proceedings/childrens-online-privacy-protection-rule
20180516/https://www.ecfr.gov/cgi-bin/text-idx?SID=4939e77c77a1a1a08c1cbf905fc4b409&node=16%3A1.0.1.3.36&rgn=div5
In regard to so-called security systems called ZScaler (HTTPS interception) and DLP.
Sure, it’s a nuisance to have transient systems that do nothing 80% of the time, break common legitimate use cases 19.99% of the time, and catch inadvertent user errors for 0.01% of the time.
This is the text of the General Data Protection Regulation (GDPR).
20180516/http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679&from=EN
I do have to admit that I am somewhat annoyed by our modern day tech world. Yes, it is innovating much faster than before, but it is also much less organized than before, and there are no signs that the future innovations will ever become very well organized like the past progress has become. The community as a whole seems to just grow more and more fragmented, with specialized knowledge of their particular area but ultimately a smaller slice of the whole tech knowledge pie. Also, that’s the same reason why my notes are so big… I had to write them because there was no such organized structure already in the world. And, ultimately, they are still less organized than I would like, but that will hopefully be changing fast soon as I take some time to add in more categories and tags.
-
Footnote: The volume of these notes points to how disorganized the modern tech industry is at a global level. I never had to do this for the standard C library, I would just consult the official reference documentation.
- But the biggest thing, the fact that so many people have become accustomed to working in such a sloppy software environment. And purportedly Internet search engines are the driving force that keep the gears turning despite the mess.
-
Discontinuous communities, the fact that they do not regularly communicate. You can really see it when you look at the way their software is implemented. Even though they may be solving the exact same problems in the exact same way using the exact same base technologies, the fact that they do need to still make arbitrary symbolic decisions is where they start to diverge and become incompatible. And once they become incompatible, they can develop a sense of inertia when it comes down to the decision of restoring compatibility versus building off of their own systems.