1 karma · joined March 4, 2021
About 1000 mirrors distributed around the world by independent institutions using donated storage and bandwidth. Some distros may have "corporate-funded" primary mirrors on providers like AWS, but independent mirrors of those still pop up. The majority of the mirrors are universities and ISPs.
> What about the source code?
Most distros have "source mirrors", as most package managers will build a "source package" which includes the source code used to build the package, in addition to vendor patches and build instructions. If they don't provide a source mirror, you go to wherever the dev kept their source, which used to default to either SourceForge or a personal website, and is now mostly GitHub.
By default most distros have a list of mirrors that they try, and they also allow you to specify a specific list of mirrors if the defaults don't work. If your country shuts off internet access to the rest of the world, and there's no mirror in your country, someone can stand up a mirror at a local business and you can use that. And you can install Linux distros from a DVD, CD, floppy disk, USB stick, and local LAN. Even if you only have one copy of the install media for one release of one distro, you can make a mirror out of it.
You can easily live without tech giants! Stop using a smart phone, use a Linux PC/Laptop, pay for your few online services like e-mail, stop using the internet for shopping and everything else. You know, the way the entire world worked 15 years ago.
> Yes, there are alternatives for products and services offered by the tech giants, but they are harder to find and to use.
If life is somewhat difficult without giant tech corporations, this is inherently unacceptable? No - this is called living in the real world. You do very often have to choose between an immoral yet easy life, and a moral yet difficult life. This has been our constant choice for literally millennia. Every society has had to grapple with it. Entire religions are based on it. It is the completely unavoidable part of life that everyone is forced to participate in.
> If I were still blocking the tech giants today, I wouldn’t have been able to watch this week’s antitrust hearing online. C-SPAN streamed it live via YouTube, which Google owns.
So get a TV! I don't know if you know this, but C-SPAN is a TV channel! You can watch it without the internet! You can even make comments on it without the internet by calling a live show and speaking your mind! Amazing! (But, probably don't do this, as the average caller seems to have about the same political insight as the average YouTube commenter)
This whole premise - that life is impossible without tech giants - concedes that life is impossible without the internet. I assure you that it is not. It's up to you to decide whether that convenience and lack of expense is preferable to the alternative, which is doing things "old school".
# cat > dropme.sh <<'EOFILE'
#!/bin/sh
set -eu
read -r SLEEP
tmp=`mktemp` ; tmp6=`mktemp`
iptables-save > $tmp
ip6tables-save > $tmp6
for t in iptables ip6tables ; do
for c in INPUT OUTPUT FORWARD ; do $t -P $c DROP ; done
$t -t nat -F ; $t -t mangle -F ; $t -F ; $t -X
done
sleep "$SLEEP"
iptables-restore < $tmp
ip6tables-restore < $tmp6
rm -f $tmp $tmp6
EOFILE
# chmod 755 dropme.sh
# ncat -k -l -c ./dropme.sh $(ifconfig eth0 | grep 'inet ' | awk '{print $2}') 12345 &
# echo "60" | ncat -v $(ifconfig eth0 | grep 'inet ' | awk '{print $2}') 12345
If you're lucky the existing connections won't even die, but the box will be offline for 60 seconds.You will of course need some way to scale this later, but as long as an artifact of your build pipeline is auto-generated IAM policy jsons, an org-wide security team can analyze them with automated tools and remediate as needed.
In which case you probably have enough free time to build a tool that just moves files around at runtime. Organize your repo however you want, then run your tool as a wrapper for any other command, and it'll move all files into the places other tools expect them. Now you've solved the problem, which was that humans like aesthetically pleasing things that serve no useful purpose.
Personally, I would start writing the abstraction as soon as I plan to have more than two apps.
I mean, this is the case any time your app talks directly to a database
But our headlight market and rules are pretty ridiculous. Most "fancy" non-HID bulbs are a ripoff and actually make visibility worse, and it's also illegal to convert a halogen setup to HID. Combine this with the fact that some designs are just crap no matter what the bulb type, and we have a general market failure to understand the real performance of headlights. People think they can generalize headlight types, but it doesn't bear out in practice. https://www.consumerreports.org/headlights/are-hid-and-led-h...
At no point in the American story does it say that wealth is to be distributed fairly. The past century has shown that as popular revolts upended the old ideas of aristocracy and monarchy, the US elite became extremely fearful of the idea of a more equal society. Communism was the worst specter of this potential loss of personal wealth for the elites, but its modern forms are also increased taxation, universal health care, increased public education/transporation/housing, etc. The more you distribute wealth to the rabble, the less wealth you can have as an individual, and Americanism is all about personal wealth (personal freedom comes largely from personal wealth; you can't even be the king of a puddle if you don't own the land it sits on).
It's similar to ancient Rome. The citizens can live quite comfortably as long as they have soldiers, slaves, and foreign riches. The big corporations of today are a modern-day Roman army: roving the world to capture and bring home cheap goods. The generals, senators, and merchants get the majority of the loot, and the citizens get fresh bread and garum, fruit, and the occasional exotic spice.
And much like the circuses of Empire, as long as the rabble are kept in bread and games, they'll put up with anything. No health care, no education, 3 jobs? Keep them in bread and games and they'll be satisfied. Netflix provides the circus, Wal-Mart provides the bread. Why would the rabble want them broken up when they're getting exactly what they want?
So this notion of fighting the status quo is really anti-American. You can't get far with the argument without butting heads against the fact that people would have to give up their cheap t-shirts, and that some would always have to work hard and live poor their whole lives. There's no way around it: somebody has to pay for our wealth, surplus, and convenience. If it's not us, it'll have to be someone else.
For example, CloudFront has features that let me create redirects for different content to go to different origins and prefixes, but Cloudflare does not have this option. You can write a .js edge worker to do it, but I'd rather not trust the integrity of my site to some crappy javascript that I threw together, and I'd rather not have to maintain my custom code indefinitely. (Actually Cloudflare's support technicians will offer to write the custom code, but it's still not something I would like to have sitting out there outside of a VCS and SDLC, with bit rot, tech debt and other nasties lurking in the future)
I remember when I imagined big companies might use their considerable resources to put together something like that. Then I found out it's just a handful of random engineers cobbling together crap and hiding it behind a fancy domain name.
It is probable that Office365's entire spam filtering system is a very large and ugly spreadsheet that gets passed around between a few teams using a ticketing system.
Change Management authorize sactions which could be problematic by vetting them through a process. The end result of the process is more confidence in the change: we know who's making it, when, where, why, what the impact will be, what we'll do if it goes wrong, etc. If the change looks stupid, dangerous, or uncertain, it gets rejected. If it looks good, it gets approved. The appropriate access is doled out temporarily to make the change. In this way, Larry the Janitor can deploy changes to your prod db, and you can be just as certain (maybe more so?) about the outcome than if your 10x developer were doing it.
Just one example of this is Terraform applies. By loading your changes into a .plan file and requiring approval of the .plan, you know for certain what actions are going to be taken and approve only those. (That doesn't stop Terraform from totally hosing your system due to all the ways it can't predict the outcome of its actions, but at least you know what the intention was)
I can tell you that lots of huge companies have this, but not consistently. Some teams move fast while some move glacially. Greenfield work can move the fastest, unless you get stuck waiting on someone to build environments.
Definitely don't stay there too long if you're unhappy. Worst case you try something new and it stinks, in which case you try again.
This is the biggest one.
After dropping out of high school, I never attended another school. The amount of socialization and long-lasting human connections that I missed out on is incalculable. Not to mention exposure to different subject matter. Macintosh had great fonts because Jobs took a calligraphy course on a whim. You might discover a hidden passion for entomological forensics. You might join a friend for a gap year trip, meet an amazing person, get married, move to Spain, get divorced 3 years later, become an accountant. Or experience the rush of unity and purpose from joining your classmates at a protest march. Or attend your dorm mate's band in some dinky basement and fall in love with beatboxing to electro swing. Screw education; go to college to wade hip deep into new experiences.
$40K to be totally immersed in innumerabile possibilities that will effect the next 80 years of your life? Compared to ~$15K for an economy car, or ~$250K for a house? Sounds worth it to me.
...that said, if you have economic hardships, self-study is completely feasible, and you can have a great career with no degree. It will still take you years to really get going, but it can work.
I get why people like to use it, but people also like slowing down to stare at car crashes on the highway. Maybe it's not a good thing.
## About
This comment explains what I know about writing docs to make them easier to understand. A succinct paragraph at the top should state what the rest of the document will cover. Don't create a document with random "stuff" in it and not explain what that "stuff" is at the beginning.
## Header Sections
Break up your document into discrete sections. They can be categories, a series of steps, etc. These headers break up the page into logical chunks of information. The header title pre-loads your brain to receive the following information, and makes it easier to skim. These header sections become a Table of Contents later.
## Grouping Information
A leading sentence groups a set of correlated bullet points:
- bullet points are useful visual indicators
- they break up important points
- they are very easy to absorb individually
Call out the major steps needed to perform an action. Step 1. Figure out the major parts of your instructions
Step 2. Break up instruction into discrete steps
- Provide sub-grouping for complex steps
Step 3. If additional steps are required but not included here, call out
that they are necessary and where to find further information.
## Adding EmphasisUsing specific emphasis can help to underscore __unique information__ and make it easier to find specific information ON THE PAGE. It also helps break up concepts visually, making it Easier To Read.
Emphasis makes skimming easier. Skimmability makes it more likely people will absorb the information you want them to.
## Be descriptive
Using extra, otherwise unnecessary words can "de-compress" a concept so that it takes less brain power to understand what the words mean. It may not be beautiful prose, but it will be easier to understand to more people.
Don't be afraid to break a paragraph up to make it easier to read. One idea spread over many paragraphs is a lot easier to understand than trying to pack it all into one.
## Don't make assumptions
Probably more than one person will be reading your document. We all have different life experiences and will interpret it slightly differently. Ask yourself if all your readers know everything you know. Probably not, or they wouldn't be reading your doc!
Before you dig into something complicated, think about what information is necessary to understand it. List the pre-requisite knowledge needed to grok the next information. Provide background information for concepts you haven't covered yet, and refer to other documents when possible.
## Use Graphics
Complex concepts can be understood easier when presented visually. If it would take you two pages to explain something that a simple diagram or flow chart can express, start with the visual. Use the text to explain details that the diagram doesn't show.
# Edit, edit, edit
Drafts are important. Constantly revise your document as you write it. Review it and see if re-writing or re-organizing sections makes it easier to read. Read it from the beginning and see whether your edits have stopped making sense, and edit again.
Documents get better when you revisit them later and solicit feedback. A fresh perspective is always good.
Follow that up with this SAML and OAuth comparison: https://www.ubisecure.com/uncategorized/difference-between-s...
Then see how OpenID Connect fits in: https://www.okta.com/identity-101/whats-the-difference-betwe... https://www.gluu.org/blog/oauth-vs-saml-vs-openid-connect/
And this page shows examples of a web app using OAuth2: https://connect2id.com/learn/oauth-2
Not even then. If you're an enterprise using EKS, you still have to work around the pain points, missing features, incompatibilities, and do a metric shit-ton of custom integration. And that's before even touching CI/CD, and ignoring how you build the infrastructure.
It's like a Formula 1 engine. Really complicated, you still have to assemble the rest of the vehicle, and you need a team of engineers to understand what it's doing when you drive it.
I think the author is right. gRPC is bullshit that you only use if you're dedicating your whole organization to one protocol. They actually re-added that wacky backwards-REST API-gateway because people really needed a REST API. On the other hand, Consul not only has a REST API since the beginning, but it incorporates more useful (some would say necessary) features so you don't have to write them from scratch. So you can go with Consul and get more compatibility and features, or go with Etcd for the opposite.
But at the same time, a "lightweight database written around Raft consensus" is like saying "clogs for runners". Most people shouldn't use it, and those that do won't be happy with the consequences later.
It's much, much easier to just download a binary and compare its cryptographic hash with the origin's before running it. That's how all Linux distributions ship apps, and Windows has a slightly more modern version of that.
I would like to use it again, but I'm a afraid I'd miss out on the latest developments that happen only in Linux-land (I'm still pissed that containers are such a Linux-centric piece of tech when they in no way need to be).