Steak Wiki - User contributions [en]

Radio

2026-05-26T02:40:12Z

ViciousCarnivore: /* List */

[[File:Antenna size per band from sigid wiki.png|Antenna size per band from sigid wiki.png]]
(from sigidwiki)

===List===
* https://www.eevblog.com/forum/beginners/question-about-an-example-in-the-book-rf-circuit-design-by-chris-bowick/msg5738275/?topicseen#msg5738275 beginners rf circuit design book which is recommended in the thread, though there are some errors in the books circuits (not uncommon, practical electronics for inventors also has errors, I have found).
* https://www.eevblog.com/forum/rf-microwave/questions-about-antennas-and-sleeve-baluns/msg5780307 - Some detailed antenna notes. I didn't read it all yet, but putting it here for reference.
* https://magsmx.com/index.html - Some tools for Microwave RF. Phase shifters, Switches, Drivers and Antennas. Some reading material.
* https://www.everythingrf.com/rf-calculators - RF Calculators

[[Category:online notes]]

Vintage Sweets Oranges

2026-05-25T13:35:22Z

ViciousCarnivore: /* History */

Purchased at WF the first week of 06/2025.


[[File:IMG 20250608 072438823.jpg|300px|thumb|right|]]
[[File:IMG 20250608 072527888.jpg|300px|thumb|right|]]

==Packaging==
Sold in single Qty.

==Price==
$1.99/lbs. It was about $1 per Orange. Maybe a little more since these are a little large.

==Fruit==
===Flavour===
Fair. Tastes like the orange freeze pops I used to eat as a kid/teenager. Also gives me a slight headache like those do as well. They are OK. Could be better, but not something you would throw away. 7/10.

===Colour===
These are an orange-yellow colour.
===Peelability===
These are easily peelable.
===Seeds/Seedless===
Seedless.
===Size===
It is a large size.

==History==
Purchased another one at Whole Foods. 01/2026. This time is was a very good vintage sweets orange. So the taste of these can differ. I found it best to cut into small pieces as it's a bit too sweet to eat a whole 1/6th of an orange at a time.

3: Another Vintage Sweets, late season 05/2026. This one was a full / rich flavour and very good. Generally, the vintage sweets have been good. The first one tasted like a freeze pop, and was nostalgic for when i was a teenager eating generic grocery store freeze pops/popsicles. But the flavour profile is not consistent. None of the other ones have been like that.

4. I purchased about 4 of these from WF, in 05/2026. One was good, one was bad. The other two vanished from my fridge. In this case, buying multiple was the right call, as some will be bad, but not all.

[[Category:Oranges]]

Computing Fails

2026-05-19T11:19:43Z

ViciousCarnivore: /* Confirmed Fails */

Mistakes made by flawed humans.

==Confirmed Fails==
* IPv6. Decades after it's introduction, still no one wants to use it. At some point, you have to admit, that IPv6 was a fail. And engineers should make a replacement.

* Windows after XP. XP was a great operating system. And Windows was never quite the same since Vista.

* ARM on cellphones. Millions (billions?) of devices that are unusable after 5 years. Landfill.

* CrowdStrike - Boy, this really "Striked, the IT Crowd / Made the IT Crowd Strike"... Get it? [https://en.wikipedia.org/wiki/2024_CrowdStrike-related_IT_outages] If there's one thing they could've changed, it might be to do 'staggered rollouts' instead of all machines at once.

* SaaS. This is similar to managed services. Evil. No customer wants SaaS, but they don't always have a choice. Compare a mechanic to the insurance companies. One does active work for things that break. The other one takes in a paycheck whether things break or not.

==Potential Fails==

* systemd. While it works, it is practically no better than the previous solutions, and is a mess of LOCs.

* wayland. This may end up making a whole lot of work for people, or it may fix what was wrong with X. See dedoimedo's thoughts on this. I don't know enough to comment. https://www.dedoimedo.com/computers/xlibre.html https://www.dedoimedo.com/computers/wayland-2024.html

==Too Much==
Programs that are full of junk or otherwise misleading. With wget, we have too much info. This example isn't specific to wget, but is a common sight. Less is more.
===usable wget===
<pre>
$ wget -h
wget: unrecognized option: h
BusyBox v1.31.1 () multi-call binary.

Usage: wget [-c|--continue] [--spider] [-q|--quiet]
[-O|--output-document FILE]
[-o|--output-file FILE] [--header 'header: value'] [-Y|--proxy on/off]
[-P DIR] [-S|--server-response] [-U|--user-agent AGENT] [-T SEC] URL...

Retrieve files via HTTP or FTP

--spider Only check URL existence: $? is 0 if exists
-c Continue retrieval of aborted transfer
-q Quiet
-P DIR Save to DIR (default .)
-S Show server response
-T SEC Network read timeout is SEC seconds
-O FILE Save to FILE ('-' for stdout)
-o FILE Log messages to FILE
-U STR Use STR for User-Agent header
-Y on/off Use proxy
</pre>

===unusable wget===
<pre>
$ wget -h
GNU Wget 1.20.1, a non-interactive network retriever.
Usage: wget [OPTION]... [URL]...

Mandatory arguments to long options are mandatory for short options too.

Startup:
-V, --version display the version of Wget and exit
-h, --help print this help
-b, --background go to background after startup
-e, --execute=COMMAND execute a `.wgetrc'-style command

Logging and input file:
-o, --output-file=FILE log messages to FILE
-a, --append-output=FILE append messages to FILE
-d, --debug print lots of debugging information
-q, --quiet quiet (no output)
-v, --verbose be verbose (this is the default)
-nv, --no-verbose turn off verboseness, without being quiet
--report-speed=TYPE output bandwidth as TYPE. TYPE can be bits
-i, --input-file=FILE download URLs found in local or external FILE
-F, --force-html treat input file as HTML
-B, --base=URL resolves HTML input-file links (-i -F)
relative to URL
--config=FILE specify config file to use
--no-config do not read any config file
--rejected-log=FILE log reasons for URL rejection to FILE

Download:
-t, --tries=NUMBER set number of retries to NUMBER (0 unlimits)
--retry-connrefused retry even if connection is refused
--retry-on-http-error=ERRORS comma-separated list of HTTP errors to retry
-O, --output-document=FILE write documents to FILE
-nc, --no-clobber skip downloads that would download to
existing files (overwriting them)
--no-netrc don't try to obtain credentials from .netrc
-c, --continue resume getting a partially-downloaded file
--start-pos=OFFSET start downloading from zero-based position OFFSET
--progress=TYPE select progress gauge type
--show-progress display the progress bar in any verbosity mode
-N, --timestamping don't re-retrieve files unless newer than
local
--no-if-modified-since don't use conditional if-modified-since get
requests in timestamping mode
--no-use-server-timestamps don't set the local file's timestamp by
the one on the server
-S, --server-response print server response
--spider don't download anything
-T, --timeout=SECONDS set all timeout values to SECONDS
--dns-timeout=SECS set the DNS lookup timeout to SECS
--connect-timeout=SECS set the connect timeout to SECS
--read-timeout=SECS set the read timeout to SECS
-w, --wait=SECONDS wait SECONDS between retrievals
--waitretry=SECONDS wait 1..SECONDS between retries of a retrieval
--random-wait wait from 0.5*WAIT...1.5*WAIT secs between retrievals
--no-proxy explicitly turn off proxy
-Q, --quota=NUMBER set retrieval quota to NUMBER
--bind-address=ADDRESS bind to ADDRESS (hostname or IP) on local host
--limit-rate=RATE limit download rate to RATE
--no-dns-cache disable caching DNS lookups
--restrict-file-names=OS restrict chars in file names to ones OS allows
--ignore-case ignore case when matching files/directories
-4, --inet4-only connect only to IPv4 addresses
-6, --inet6-only connect only to IPv6 addresses
--prefer-family=FAMILY connect first to addresses of specified family,
one of IPv6, IPv4, or none
--user=USER set both ftp and http user to USER
--password=PASS set both ftp and http password to PASS
--ask-password prompt for passwords
--use-askpass=COMMAND specify credential handler for requesting
username and password. If no COMMAND is
specified the WGET_ASKPASS or the SSH_ASKPASS
environment variable is used.
--no-iri turn off IRI support
--local-encoding=ENC use ENC as the local encoding for IRIs
--remote-encoding=ENC use ENC as the default remote encoding
--unlink remove file before clobber
--xattr turn on storage of metadata in extended file attributes
Directories:
-nd, --no-directories don't create directories
-x, --force-directories force creation of directories
-nH, --no-host-directories don't create host directories
--protocol-directories use protocol name in directories
-P, --directory-prefix=PREFIX save files to PREFIX/..
--cut-dirs=NUMBER ignore NUMBER remote directory components

HTTP options:
--http-user=USER set http user to USER
--http-password=PASS set http password to PASS
--no-cache disallow server-cached data
--default-page=NAME change the default page name (normally
this is 'index.html'.)
-E, --adjust-extension save HTML/CSS documents with proper extensions
--ignore-length ignore 'Content-Length' header field
--header=STRING insert STRING among the headers
--compression=TYPE choose compression, one of auto, gzip and none. (default: none)
--max-redirect maximum redirections allowed per page
--proxy-user=USER set USER as proxy username
--proxy-password=PASS set PASS as proxy password
--referer=URL include 'Referer: URL' header in HTTP request
--save-headers save the HTTP headers to file
-U, --user-agent=AGENT identify as AGENT instead of Wget/VERSION
--no-http-keep-alive disable HTTP keep-alive (persistent connections)
--no-cookies don't use cookies
--load-cookies=FILE load cookies from FILE before session
--save-cookies=FILE save cookies to FILE after session
--keep-session-cookies load and save session (non-permanent) cookies
--post-data=STRING use the POST method; send STRING as the data
--post-file=FILE use the POST method; send contents of FILE
--method=HTTPMethod use method "HTTPMethod" in the request
--body-data=STRING send STRING as data. --method MUST be set
--body-file=FILE send contents of FILE. --method MUST be set
--content-disposition honor the Content-Disposition header when
choosing local file names (EXPERIMENTAL)
--content-on-error output the received content on server errors
--auth-no-challenge send Basic HTTP authentication information
without first waiting for the server's
challenge

HTTPS (SSL/TLS) options:
--secure-protocol=PR choose secure protocol, one of auto, SSLv2,
SSLv3, TLSv1, TLSv1_1, TLSv1_2 and PFS
--https-only only follow secure HTTPS links
--no-check-certificate don't validate the server's certificate
--certificate=FILE client certificate file
--certificate-type=TYPE client certificate type, PEM or DER
--private-key=FILE private key file
--private-key-type=TYPE private key type, PEM or DER
--ca-certificate=FILE file with the bundle of CAs
--ca-directory=DIR directory where hash list of CAs is stored
--crl-file=FILE file with bundle of CRLs
--pinnedpubkey=FILE/HASHES Public key (PEM/DER) file, or any number
of base64 encoded sha256 hashes preceded by
'sha256//' and separated by ';', to verify
peer against

--ciphers=STR Set the priority string (GnuTLS) or cipher list string (OpenSSL) directly.
Use with care. This option overrides --secure-protocol.
The format and syntax of this string depend on the specific SSL/TLS engine.
HSTS options:
--no-hsts disable HSTS
--hsts-file path of HSTS database (will override default)
FTP options:
--ftp-user=USER set ftp user to USER
--ftp-password=PASS set ftp password to PASS
--no-remove-listing don't remove '.listing' files
--no-glob turn off FTP file name globbing
--no-passive-ftp disable the "passive" transfer mode
--preserve-permissions preserve remote file permissions
--retr-symlinks when recursing, get linked-to files (not dir)

FTPS options:
--ftps-implicit use implicit FTPS (default port is 990)
--ftps-resume-ssl resume the SSL/TLS session started in the control connection when
opening a data connection
--ftps-clear-data-connection cipher the control channel only; all the data will be in plaintext
--ftps-fallback-to-ftp fall back to FTP if FTPS is not supported in the target server
WARC options:
--warc-file=FILENAME save request/response data to a .warc.gz file
--warc-header=STRING insert STRING into the warcinfo record
--warc-max-size=NUMBER set maximum size of WARC files to NUMBER
--warc-cdx write CDX index files
--warc-dedup=FILENAME do not store records listed in this CDX file
--no-warc-compression do not compress WARC files with GZIP
--no-warc-digests do not calculate SHA1 digests
--no-warc-keep-log do not store the log file in a WARC record
--warc-tempdir=DIRECTORY location for temporary files created by the
WARC writer
Recursive download:
-r, --recursive specify recursive download
-l, --level=NUMBER maximum recursion depth (inf or 0 for infinite)
--delete-after delete files locally after downloading them
-k, --convert-links make links in downloaded HTML or CSS point to
local files
--convert-file-only convert the file part of the URLs only (usually known as the basename)
--backups=N before writing file X, rotate up to N backup files
-K, --backup-converted before converting file X, back up as X.orig
-m, --mirror shortcut for -N -r -l inf --no-remove-listing
-p, --page-requisites get all images, etc. needed to display HTML page
--strict-comments turn on strict (SGML) handling of HTML comments
Recursive accept/reject:
-A, --accept=LIST comma-separated list of accepted extensions
-R, --reject=LIST comma-separated list of rejected extensions
--accept-regex=REGEX regex matching accepted URLs
--reject-regex=REGEX regex matching rejected URLs
--regex-type=TYPE regex type (posix|pcre)
-D, --domains=LIST comma-separated list of accepted domains
--exclude-domains=LIST comma-separated list of rejected domains
--follow-ftp follow FTP links from HTML documents
--follow-tags=LIST comma-separated list of followed HTML tags
--ignore-tags=LIST comma-separated list of ignored HTML tags
-H, --span-hosts go to foreign hosts when recursive
-L, --relative follow relative links only
-I, --include-directories=LIST list of allowed directories
--trust-server-names use the name specified by the redirection
URL's last component
-X, --exclude-directories=LIST list of excluded directories
-np, --no-parent don't ascend to the parent directory

Email bug reports, questions, discussions to <bug-wget@gnu.org>
and/or open issues at https://savannah.gnu.org/bugs/?func=additem&group=wget.

</pre>
===Conclusion===
No human being can digest all the information in the latter. It's
a mess. Perhaps another flag can be used for the verbose help information, but
for average daily usage, busybox wins here.

EDIT: it looks like I am not the only one who thinks this way as someone has created:
https://github.com/tldr-pages/tldr

==Javascript and White Space bloat==
Discourse. I hate it so much. It's as if someone who had never used a forum before thought about designing forums. They then looked at all the reasonable spacing and coherent navigation offered by php forums from the 2000's, and said: "No, I must have more white space, and a font size that is 3 times as big. I must also make it slower, by adding superfluous javascript libraries.". Thus, discourse was created: To deter people from actually using forums effectively.

Forums have been nerfed apparently in favor of social media. In fact, most websites have been nerfed in favor of monolithic 'feeds'.

==IPv6 Is Badly Designed==
IPv6. It was supposed to take over IPv4 over 20 years ago (yes, people were talking about IPv6 in the year 2000). In 2020, it still hasn't. Why? Because it's crap, and everyone knows it. However, the amount of corporate money invested into it, means that it may eventually get forced onto the masses. It's not even easy to find criticisms of the technology these days. It's all being astroturfed by shills. It's like a bad sequel. It's worse than the original. But you can't avoid it.

Ref: https://web.archive.org/web/20070707080506/http://tech.hellyeah.com/display_doc.phtml?id=28

<pre>
To begin with, IPv6 will use a 128 bit address space, as compared to
IPv4's 32 bits. This 128 bit address is the biggest reason for IPv6. It
is supposed to give us plenty of IP addresses to last us well into the
future. However, 128 bits is overkill. Sixty-four should be more than
enough.

Let's put it in terms that are easier to comprehend. We'll assume that
there are 15 billion people on the planet. (currently, there are only
6.1 billion, and the largest estimates for the next fifty years project
12 billion). With 128 bits per IP address, each person could have
2.26e28 IP addresses to themselves. If we reduce it to 64 bits, each
person would still have 1.2 billion addresses.

What about the people who want to put IP addresses on every light pole,
mailbox, stop light and street sign? Well, there are about 148 million
square kilometers of land on the Earth (not including ocean). With 128
bits, we have almost 2.3e20 addresses per square centimeter. If we
reduce that to 64 bits, each square centimeter would still have about
12.5 IP addresses -- more than enough.

...(Sections Omitted)

Part of IPv4's immense success was due to its
simplicity and rigid structure. It does the job it was meant to do
quickly and effectively. IPv6 adds all sorts of bells and whistles that
are unneccesary and even detrimental. With all the wasted space and
privacy issues, I'd rather have the IETF go back to the drawing board
and come back with IPv7

</pre>
Less is more. The answer isn't "add more people". The answer isn't "add more ip addresses". Things can't expand exponentially forever. There has to be limits in place. It has to be practically usable.

If you look at it right, neither ipv4 nor ipv6 is designed correctly. ipv4 is too simple, and ipv6 is too complicated. They are both fails.

It's been said, but if they had made ipv4 5 octets from the start, ip addresses would not have run out for decades. Maybe not ever.

Also consider that mac addresses are easier to read than IPv6, and much higher than 4 billion combinations (16 ^12, according to: https://stackoverflow.com/questions/44873804/will-mac-address-ever-run-out-of-combinations) It's 48 bits. This brings up the question: What is the best way to represent ip addresses (ipv4, ipv6, mac address, or other), and what is the appropriate number of bits to designate to it.

==Hidden Files==
alias ls='ls -a'
Hidden files are evil. All ls should be ls -a. They will bite you as often as pcb makers get bitten by incorrect footprints. Its bad design. It will never go away. There's no thinking that you should've been smarter. Lies. Its the human factor. It will always, always bite you someday.
Hidden files are fundamentally flawed. They will always cause trouble.

In Windows (10/11), there are 2, TWO levels of hidden files. I kid you not.

==Duplication of Work==
There are dozens of companies and individuals doing source code management tools. Meta-coding. The duplication of work can't ever have been this bad, and the duplication here isn't even an actual tool: it's a tool for a tool. Go ahead and search for source code / git hosting. Prepare yourself, there are way too many options. It's to the point of hyperbole.

Western cultures need to take a lesson from china. One of china's strengths, is not necessarily cutting corners, but in not doing more than is needed to complete a task. It's about efficiency. And it is possibly a sin to indulge in things that aren't necessary. Time and Life is short. Time management is critical.

==Intel ME==
See libreboot.org.

==Inconsistent flag usage for common commands: chown / scp and the recursive flag==
Look at scp and chown. Then look at the recursive flag.
scp -r
chown -R
They are both recursive. I know I've stumbled across this probably over a hundred times
in the last decade using Linux.

There should be an unwritten standard where lower case is used for the most common
operations. kind of like how there is an unwritten standard for commands to give
help when you type command -h or --help. But there is none. Cases are all over the
place. it's a mess. simple things. How many millions of moments have been lost to people
typing the wrong -r or -R. It adds up over billions of man hours. It's a fail.

Someone really screwed up here.

One solution, would be for flags to be case insensitive. Is there any reasonable use case
where you'd want to be able to use both -r and -R for different things in the same program?
It's just confusing.

==ARM==
"That sure is a lot of non-reusable trash you are creating there (cellphones)."

==OAuth==

[[File:Dilbert.gif|300px|thumb|right|Computers get worse]]
"We need to make it more difficult for users to get their data" - gmail and office365 email monopoly collusion

==Windows 11 Incompatibility==
This link is priceless. I took a screenshot since the internet archive 'somehow failed' to save the page. Basically, a logical and sane person asks why his top of the line workstation doesn't work with Windows 11. Imagine paying 5 grand for a (typically GPU CAD) workstation only to have to buy another one in 7 years. He is told to use 'rufus', by 'unofficial' support.
https://answers.microsoft.com/en-us/windows/forum/all/why-does-windows-11-still-not-support-my-cpu-chips/e2bd3cab-43ca-4f1c-821b-0825ca597666
[[File:Priceless.png|300px|thumb|right|How to Create Landfill Waste]]

==Quickbooks==
Quickbooks is an interesting story of what can go wrong with software. A number of things have gone wrong over time, though when it was first introduced, it was indeed a valuable program to have.
* Online activation required (which breaks old editions)
* Move to SaaS model/online (antagonistic to the customers. uses a slower web browser interface)
* Potential forced move to cloud servers
* Never ending software (it's entirely possible to make an accounting software that is a finished product and then people can move onto solving other problems, but developers seem to be interested in making a lifetime occupation out of a 5-10 year project).

It's fascinating and horrific just how bad the accounting software situation is. Evil stuff.

Computing Fails

2026-05-19T11:17:01Z

ViciousCarnivore: /* Windows 11 Incompatibility */

Mistakes made by flawed humans.

==Confirmed Fails==
* IPv6. Decades after it's introduction, still no one wants to use it. At some point, you have to admit, that IPv6 was a fail. And engineers should make a replacement.

* Windows after XP. XP was a great operating system. And Windows was never quite the same since Vista.

* ARM on cellphones. Millions (billions?) of devices that are unusable after 5 years. Landfill.

* CrowdStrike - Boy, this really "Striked, the IT Crowd / Made the IT Crowd Strike"... Get it? [https://en.wikipedia.org/wiki/2024_CrowdStrike-related_IT_outages] If there's one thing they could've changed, it might be to do 'staggered rollouts' instead of all machines at once.

==Potential Fails==

* systemd. While it works, it is practically no better than the previous solutions, and is a mess of LOCs.

* wayland. This may end up making a whole lot of work for people, or it may fix what was wrong with X. See dedoimedo's thoughts on this. I don't know enough to comment. https://www.dedoimedo.com/computers/xlibre.html https://www.dedoimedo.com/computers/wayland-2024.html

==Too Much==
Programs that are full of junk or otherwise misleading. With wget, we have too much info. This example isn't specific to wget, but is a common sight. Less is more.
===usable wget===
<pre>
$ wget -h
wget: unrecognized option: h
BusyBox v1.31.1 () multi-call binary.

Usage: wget [-c|--continue] [--spider] [-q|--quiet]
[-O|--output-document FILE]
[-o|--output-file FILE] [--header 'header: value'] [-Y|--proxy on/off]
[-P DIR] [-S|--server-response] [-U|--user-agent AGENT] [-T SEC] URL...

Retrieve files via HTTP or FTP

--spider Only check URL existence: $? is 0 if exists
-c Continue retrieval of aborted transfer
-q Quiet
-P DIR Save to DIR (default .)
-S Show server response
-T SEC Network read timeout is SEC seconds
-O FILE Save to FILE ('-' for stdout)
-o FILE Log messages to FILE
-U STR Use STR for User-Agent header
-Y on/off Use proxy
</pre>

===unusable wget===
<pre>
$ wget -h
GNU Wget 1.20.1, a non-interactive network retriever.
Usage: wget [OPTION]... [URL]...

Mandatory arguments to long options are mandatory for short options too.

Startup:
-V, --version display the version of Wget and exit
-h, --help print this help
-b, --background go to background after startup
-e, --execute=COMMAND execute a `.wgetrc'-style command

Logging and input file:
-o, --output-file=FILE log messages to FILE
-a, --append-output=FILE append messages to FILE
-d, --debug print lots of debugging information
-q, --quiet quiet (no output)
-v, --verbose be verbose (this is the default)
-nv, --no-verbose turn off verboseness, without being quiet
--report-speed=TYPE output bandwidth as TYPE. TYPE can be bits
-i, --input-file=FILE download URLs found in local or external FILE
-F, --force-html treat input file as HTML
-B, --base=URL resolves HTML input-file links (-i -F)
relative to URL
--config=FILE specify config file to use
--no-config do not read any config file
--rejected-log=FILE log reasons for URL rejection to FILE

Download:
-t, --tries=NUMBER set number of retries to NUMBER (0 unlimits)
--retry-connrefused retry even if connection is refused
--retry-on-http-error=ERRORS comma-separated list of HTTP errors to retry
-O, --output-document=FILE write documents to FILE
-nc, --no-clobber skip downloads that would download to
existing files (overwriting them)
--no-netrc don't try to obtain credentials from .netrc
-c, --continue resume getting a partially-downloaded file
--start-pos=OFFSET start downloading from zero-based position OFFSET
--progress=TYPE select progress gauge type
--show-progress display the progress bar in any verbosity mode
-N, --timestamping don't re-retrieve files unless newer than
local
--no-if-modified-since don't use conditional if-modified-since get
requests in timestamping mode
--no-use-server-timestamps don't set the local file's timestamp by
the one on the server
-S, --server-response print server response
--spider don't download anything
-T, --timeout=SECONDS set all timeout values to SECONDS
--dns-timeout=SECS set the DNS lookup timeout to SECS
--connect-timeout=SECS set the connect timeout to SECS
--read-timeout=SECS set the read timeout to SECS
-w, --wait=SECONDS wait SECONDS between retrievals
--waitretry=SECONDS wait 1..SECONDS between retries of a retrieval
--random-wait wait from 0.5*WAIT...1.5*WAIT secs between retrievals
--no-proxy explicitly turn off proxy
-Q, --quota=NUMBER set retrieval quota to NUMBER
--bind-address=ADDRESS bind to ADDRESS (hostname or IP) on local host
--limit-rate=RATE limit download rate to RATE
--no-dns-cache disable caching DNS lookups
--restrict-file-names=OS restrict chars in file names to ones OS allows
--ignore-case ignore case when matching files/directories
-4, --inet4-only connect only to IPv4 addresses
-6, --inet6-only connect only to IPv6 addresses
--prefer-family=FAMILY connect first to addresses of specified family,
one of IPv6, IPv4, or none
--user=USER set both ftp and http user to USER
--password=PASS set both ftp and http password to PASS
--ask-password prompt for passwords
--use-askpass=COMMAND specify credential handler for requesting
username and password. If no COMMAND is
specified the WGET_ASKPASS or the SSH_ASKPASS
environment variable is used.
--no-iri turn off IRI support
--local-encoding=ENC use ENC as the local encoding for IRIs
--remote-encoding=ENC use ENC as the default remote encoding
--unlink remove file before clobber
--xattr turn on storage of metadata in extended file attributes
Directories:
-nd, --no-directories don't create directories
-x, --force-directories force creation of directories
-nH, --no-host-directories don't create host directories
--protocol-directories use protocol name in directories
-P, --directory-prefix=PREFIX save files to PREFIX/..
--cut-dirs=NUMBER ignore NUMBER remote directory components

HTTP options:
--http-user=USER set http user to USER
--http-password=PASS set http password to PASS
--no-cache disallow server-cached data
--default-page=NAME change the default page name (normally
this is 'index.html'.)
-E, --adjust-extension save HTML/CSS documents with proper extensions
--ignore-length ignore 'Content-Length' header field
--header=STRING insert STRING among the headers
--compression=TYPE choose compression, one of auto, gzip and none. (default: none)
--max-redirect maximum redirections allowed per page
--proxy-user=USER set USER as proxy username
--proxy-password=PASS set PASS as proxy password
--referer=URL include 'Referer: URL' header in HTTP request
--save-headers save the HTTP headers to file
-U, --user-agent=AGENT identify as AGENT instead of Wget/VERSION
--no-http-keep-alive disable HTTP keep-alive (persistent connections)
--no-cookies don't use cookies
--load-cookies=FILE load cookies from FILE before session
--save-cookies=FILE save cookies to FILE after session
--keep-session-cookies load and save session (non-permanent) cookies
--post-data=STRING use the POST method; send STRING as the data
--post-file=FILE use the POST method; send contents of FILE
--method=HTTPMethod use method "HTTPMethod" in the request
--body-data=STRING send STRING as data. --method MUST be set
--body-file=FILE send contents of FILE. --method MUST be set
--content-disposition honor the Content-Disposition header when
choosing local file names (EXPERIMENTAL)
--content-on-error output the received content on server errors
--auth-no-challenge send Basic HTTP authentication information
without first waiting for the server's
challenge

HTTPS (SSL/TLS) options:
--secure-protocol=PR choose secure protocol, one of auto, SSLv2,
SSLv3, TLSv1, TLSv1_1, TLSv1_2 and PFS
--https-only only follow secure HTTPS links
--no-check-certificate don't validate the server's certificate
--certificate=FILE client certificate file
--certificate-type=TYPE client certificate type, PEM or DER
--private-key=FILE private key file
--private-key-type=TYPE private key type, PEM or DER
--ca-certificate=FILE file with the bundle of CAs
--ca-directory=DIR directory where hash list of CAs is stored
--crl-file=FILE file with bundle of CRLs
--pinnedpubkey=FILE/HASHES Public key (PEM/DER) file, or any number
of base64 encoded sha256 hashes preceded by
'sha256//' and separated by ';', to verify
peer against

--ciphers=STR Set the priority string (GnuTLS) or cipher list string (OpenSSL) directly.
Use with care. This option overrides --secure-protocol.
The format and syntax of this string depend on the specific SSL/TLS engine.
HSTS options:
--no-hsts disable HSTS
--hsts-file path of HSTS database (will override default)
FTP options:
--ftp-user=USER set ftp user to USER
--ftp-password=PASS set ftp password to PASS
--no-remove-listing don't remove '.listing' files
--no-glob turn off FTP file name globbing
--no-passive-ftp disable the "passive" transfer mode
--preserve-permissions preserve remote file permissions
--retr-symlinks when recursing, get linked-to files (not dir)

FTPS options:
--ftps-implicit use implicit FTPS (default port is 990)
--ftps-resume-ssl resume the SSL/TLS session started in the control connection when
opening a data connection
--ftps-clear-data-connection cipher the control channel only; all the data will be in plaintext
--ftps-fallback-to-ftp fall back to FTP if FTPS is not supported in the target server
WARC options:
--warc-file=FILENAME save request/response data to a .warc.gz file
--warc-header=STRING insert STRING into the warcinfo record
--warc-max-size=NUMBER set maximum size of WARC files to NUMBER
--warc-cdx write CDX index files
--warc-dedup=FILENAME do not store records listed in this CDX file
--no-warc-compression do not compress WARC files with GZIP
--no-warc-digests do not calculate SHA1 digests
--no-warc-keep-log do not store the log file in a WARC record
--warc-tempdir=DIRECTORY location for temporary files created by the
WARC writer
Recursive download:
-r, --recursive specify recursive download
-l, --level=NUMBER maximum recursion depth (inf or 0 for infinite)
--delete-after delete files locally after downloading them
-k, --convert-links make links in downloaded HTML or CSS point to
local files
--convert-file-only convert the file part of the URLs only (usually known as the basename)
--backups=N before writing file X, rotate up to N backup files
-K, --backup-converted before converting file X, back up as X.orig
-m, --mirror shortcut for -N -r -l inf --no-remove-listing
-p, --page-requisites get all images, etc. needed to display HTML page
--strict-comments turn on strict (SGML) handling of HTML comments
Recursive accept/reject:
-A, --accept=LIST comma-separated list of accepted extensions
-R, --reject=LIST comma-separated list of rejected extensions
--accept-regex=REGEX regex matching accepted URLs
--reject-regex=REGEX regex matching rejected URLs
--regex-type=TYPE regex type (posix|pcre)
-D, --domains=LIST comma-separated list of accepted domains
--exclude-domains=LIST comma-separated list of rejected domains
--follow-ftp follow FTP links from HTML documents
--follow-tags=LIST comma-separated list of followed HTML tags
--ignore-tags=LIST comma-separated list of ignored HTML tags
-H, --span-hosts go to foreign hosts when recursive
-L, --relative follow relative links only
-I, --include-directories=LIST list of allowed directories
--trust-server-names use the name specified by the redirection
URL's last component
-X, --exclude-directories=LIST list of excluded directories
-np, --no-parent don't ascend to the parent directory

Email bug reports, questions, discussions to <bug-wget@gnu.org>
and/or open issues at https://savannah.gnu.org/bugs/?func=additem&group=wget.

</pre>
===Conclusion===
No human being can digest all the information in the latter. It's
a mess. Perhaps another flag can be used for the verbose help information, but
for average daily usage, busybox wins here.

EDIT: it looks like I am not the only one who thinks this way as someone has created:
https://github.com/tldr-pages/tldr

==Javascript and White Space bloat==
Discourse. I hate it so much. It's as if someone who had never used a forum before thought about designing forums. They then looked at all the reasonable spacing and coherent navigation offered by php forums from the 2000's, and said: "No, I must have more white space, and a font size that is 3 times as big. I must also make it slower, by adding superfluous javascript libraries.". Thus, discourse was created: To deter people from actually using forums effectively.

Forums have been nerfed apparently in favor of social media. In fact, most websites have been nerfed in favor of monolithic 'feeds'.

==IPv6 Is Badly Designed==
IPv6. It was supposed to take over IPv4 over 20 years ago (yes, people were talking about IPv6 in the year 2000). In 2020, it still hasn't. Why? Because it's crap, and everyone knows it. However, the amount of corporate money invested into it, means that it may eventually get forced onto the masses. It's not even easy to find criticisms of the technology these days. It's all being astroturfed by shills. It's like a bad sequel. It's worse than the original. But you can't avoid it.

Ref: https://web.archive.org/web/20070707080506/http://tech.hellyeah.com/display_doc.phtml?id=28

<pre>
To begin with, IPv6 will use a 128 bit address space, as compared to
IPv4's 32 bits. This 128 bit address is the biggest reason for IPv6. It
is supposed to give us plenty of IP addresses to last us well into the
future. However, 128 bits is overkill. Sixty-four should be more than
enough.

Let's put it in terms that are easier to comprehend. We'll assume that
there are 15 billion people on the planet. (currently, there are only
6.1 billion, and the largest estimates for the next fifty years project
12 billion). With 128 bits per IP address, each person could have
2.26e28 IP addresses to themselves. If we reduce it to 64 bits, each
person would still have 1.2 billion addresses.

What about the people who want to put IP addresses on every light pole,
mailbox, stop light and street sign? Well, there are about 148 million
square kilometers of land on the Earth (not including ocean). With 128
bits, we have almost 2.3e20 addresses per square centimeter. If we
reduce that to 64 bits, each square centimeter would still have about
12.5 IP addresses -- more than enough.

...(Sections Omitted)

Part of IPv4's immense success was due to its
simplicity and rigid structure. It does the job it was meant to do
quickly and effectively. IPv6 adds all sorts of bells and whistles that
are unneccesary and even detrimental. With all the wasted space and
privacy issues, I'd rather have the IETF go back to the drawing board
and come back with IPv7

</pre>
Less is more. The answer isn't "add more people". The answer isn't "add more ip addresses". Things can't expand exponentially forever. There has to be limits in place. It has to be practically usable.

If you look at it right, neither ipv4 nor ipv6 is designed correctly. ipv4 is too simple, and ipv6 is too complicated. They are both fails.

It's been said, but if they had made ipv4 5 octets from the start, ip addresses would not have run out for decades. Maybe not ever.

Also consider that mac addresses are easier to read than IPv6, and much higher than 4 billion combinations (16 ^12, according to: https://stackoverflow.com/questions/44873804/will-mac-address-ever-run-out-of-combinations) It's 48 bits. This brings up the question: What is the best way to represent ip addresses (ipv4, ipv6, mac address, or other), and what is the appropriate number of bits to designate to it.

==Hidden Files==
alias ls='ls -a'
Hidden files are evil. All ls should be ls -a. They will bite you as often as pcb makers get bitten by incorrect footprints. Its bad design. It will never go away. There's no thinking that you should've been smarter. Lies. Its the human factor. It will always, always bite you someday.
Hidden files are fundamentally flawed. They will always cause trouble.

In Windows (10/11), there are 2, TWO levels of hidden files. I kid you not.

==Duplication of Work==
There are dozens of companies and individuals doing source code management tools. Meta-coding. The duplication of work can't ever have been this bad, and the duplication here isn't even an actual tool: it's a tool for a tool. Go ahead and search for source code / git hosting. Prepare yourself, there are way too many options. It's to the point of hyperbole.

Western cultures need to take a lesson from china. One of china's strengths, is not necessarily cutting corners, but in not doing more than is needed to complete a task. It's about efficiency. And it is possibly a sin to indulge in things that aren't necessary. Time and Life is short. Time management is critical.

==Intel ME==
See libreboot.org.

==Inconsistent flag usage for common commands: chown / scp and the recursive flag==
Look at scp and chown. Then look at the recursive flag.
scp -r
chown -R
They are both recursive. I know I've stumbled across this probably over a hundred times
in the last decade using Linux.

There should be an unwritten standard where lower case is used for the most common
operations. kind of like how there is an unwritten standard for commands to give
help when you type command -h or --help. But there is none. Cases are all over the
place. it's a mess. simple things. How many millions of moments have been lost to people
typing the wrong -r or -R. It adds up over billions of man hours. It's a fail.

Someone really screwed up here.

One solution, would be for flags to be case insensitive. Is there any reasonable use case
where you'd want to be able to use both -r and -R for different things in the same program?
It's just confusing.

==ARM==
"That sure is a lot of non-reusable trash you are creating there (cellphones)."

==OAuth==

[[File:Dilbert.gif|300px|thumb|right|Computers get worse]]
"We need to make it more difficult for users to get their data" - gmail and office365 email monopoly collusion

==Windows 11 Incompatibility==
This link is priceless. I took a screenshot since the internet archive 'somehow failed' to save the page. Basically, a logical and sane person asks why his top of the line workstation doesn't work with Windows 11. Imagine paying 5 grand for a (typically GPU CAD) workstation only to have to buy another one in 7 years. He is told to use 'rufus', by 'unofficial' support.
https://answers.microsoft.com/en-us/windows/forum/all/why-does-windows-11-still-not-support-my-cpu-chips/e2bd3cab-43ca-4f1c-821b-0825ca597666
[[File:Priceless.png|300px|thumb|right|How to Create Landfill Waste]]

==Quickbooks==
Quickbooks is an interesting story of what can go wrong with software. A number of things have gone wrong over time, though when it was first introduced, it was indeed a valuable program to have.
* Online activation required (which breaks old editions)
* Move to SaaS model/online (antagonistic to the customers. uses a slower web browser interface)
* Potential forced move to cloud servers
* Never ending software (it's entirely possible to make an accounting software that is a finished product and then people can move onto solving other problems, but developers seem to be interested in making a lifetime occupation out of a 5-10 year project).

It's fascinating and horrific just how bad the accounting software situation is. Evil stuff.

Paramount Cara Cara Orange

2026-05-19T06:26:26Z

ViciousCarnivore:

A Paramount Cara Cara with a label that doesn't look like the paramount orange. Can't say I'm a fan of that. It was a good orange, though. Purchased 05/2026 from S&S.


[[File:Paramount cara cara.jpg|300px|thumb|right|]]

==Packaging==
Sold in single qty. I generally don't buy oranges in bags. Many of the bags are not labeled as to what farm they are.

==Price==
n/a I think it was 1.99/lbs.

==Fruit==
===Flavour===
This was a good orange.

===Colour===
This was a orange yellow colour. The fruit being a cara cara, looks slightly like a grapefruit. A little red.

===Peelability===
Somewhat easy to peel. Though it was starting to be difficult to peel (i.e. break off in pieces)
===Seeds/Seedless===
These are seedless.
===Size===
these are medium to medium small size.

==History==

[[Category:Oranges]]

Paramount Cara Cara Orange

2026-05-19T06:26:13Z

ViciousCarnivore:

A Paramount Cara Cara with a label that doesn't look like the paramount orange. Can't say I'm a fan of that. It was a good orange, though. Purchased 05/2026 from S&S.


[[File:Paramount cara cara.jpg|150px|thumb|right|]]

==Packaging==
Sold in single qty. I generally don't buy oranges in bags. Many of the bags are not labeled as to what farm they are.

==Price==
n/a I think it was 1.99/lbs.

==Fruit==
===Flavour===
This was a good orange.

===Colour===
This was a orange yellow colour. The fruit being a cara cara, looks slightly like a grapefruit. A little red.

===Peelability===
Somewhat easy to peel. Though it was starting to be difficult to peel (i.e. break off in pieces)
===Seeds/Seedless===
These are seedless.
===Size===
these are medium to medium small size.

==History==

[[Category:Oranges]]

File:Paramount cara cara.jpg

2026-05-19T06:25:47Z

ViciousCarnivore:

Paramount Cara Cara Orange

2026-05-19T06:24:20Z

ViciousCarnivore: /* Colour */

A Paramount Cara Cara with a label that doesn't look like the paramount orange. Can't say I'm a fan of that. It was a good orange, though. Purchased 05/2026 from S&S.


[[|300px|thumb|right|]]
[[|300px|thumb|right|]]

==Packaging==
Sold in single qty. I generally don't buy oranges in bags. Many of the bags are not labeled as to what farm they are.

==Price==
n/a I think it was 1.99/lbs.

==Fruit==
===Flavour===
This was a good orange.

===Colour===
This was a orange yellow colour. The fruit being a cara cara, looks slightly like a grapefruit. A little red.

===Peelability===
Somewhat easy to peel. Though it was starting to be difficult to peel (i.e. break off in pieces)
===Seeds/Seedless===
These are seedless.
===Size===
these are medium to medium small size.

==History==

[[Category:Oranges]]

Paramount Cara Cara Orange

2026-05-19T06:23:18Z

ViciousCarnivore: Created page with "  A Paramount Cara Cara with a label that does..."

A Paramount Cara Cara with a label that doesn't look like the paramount orange. Can't say I'm a fan of that. It was a good orange, though. Purchased 05/2026 from S&S.


[[|300px|thumb|right|]]
[[|300px|thumb|right|]]

==Packaging==
Sold in single qty. I generally don't buy oranges in bags. Many of the bags are not labeled as to what farm they are.

==Price==
n/a I think it was 1.99/lbs.

==Fruit==
===Flavour===
This was a good orange.

===Colour===
This was a orange yellow colour.
===Peelability===
Somewhat easy to peel. Though it was starting to be difficult to peel (i.e. break off in pieces)
===Seeds/Seedless===
These are seedless.
===Size===
these are medium to medium small size.

==History==

[[Category:Oranges]]

Oranges

2026-05-19T06:20:31Z

ViciousCarnivore: /* List */

Here is the orange blog or orange log.

I'll try to keep track of good and bad oranges.
Most oranges are bad, unfortunately.

It appears these companies are findable via a web search online, unless the Oranges are sold as generic.

todo: organize these by type (navel, cara cara, valencia, etc)

[[File:Cyberblockmetalorange.png|300px|||]]

==List==

* [[Booth_Ranches_Oranges]]
* [[Homegrown Organic Farms Oranges]]
* [[Kings_River_Oranges]]
* [[MB_StoreBrand_California_Oranges]]
* [[Paramount_Oranges]]
* [[Paramount Cara Cara Orange]]
* [[Peels Cara Cara Navel]]
* [[RVO Oranges]]
* [[Sequoia Oranges]]
* [[Sunkist CaraCara Oranges]]
* [[Sunkist Moro Oranges]]
* [[Sunkist Oranges]]
* [[Sunkist LateSeason Oranges]]
* [[SunPacific Oranges]]
* [[SunPacific Organic Oranges]]
* [[Suntreat Oranges]]
* [[Vintage Sweets Oranges]]

* [[Orange_Template]]

[[Category:Oranges]]

Oranges

2026-05-19T06:20:19Z

ViciousCarnivore: /* List */

Here is the orange blog or orange log.

I'll try to keep track of good and bad oranges.
Most oranges are bad, unfortunately.

It appears these companies are findable via a web search online, unless the Oranges are sold as generic.

todo: organize these by type (navel, cara cara, valencia, etc)

[[File:Cyberblockmetalorange.png|300px|||]]

==List==

* [[Booth_Ranches_Oranges]]
* [[Homegrown Organic Farms Oranges]]
* [[Kings_River_Oranges]]
* [[MB_StoreBrand_California_Oranges]]
* [[Paramount_Oranges]]
* [[Paramount_Cara_Cara_Orange]]
* [[Peels Cara Cara Navel]]
* [[RVO Oranges]]
* [[Sequoia Oranges]]
* [[Sunkist CaraCara Oranges]]
* [[Sunkist Moro Oranges]]
* [[Sunkist Oranges]]
* [[Sunkist LateSeason Oranges]]
* [[SunPacific Oranges]]
* [[SunPacific Organic Oranges]]
* [[Suntreat Oranges]]
* [[Vintage Sweets Oranges]]

* [[Orange_Template]]

[[Category:Oranges]]

Vintage Sweets Oranges

2026-05-19T06:12:51Z

ViciousCarnivore: /* History */

Kings River Oranges

2026-05-19T06:10:41Z

ViciousCarnivore:

Purchased at MB around 2025/05

This orange was very good. Named King's River, and it is of high grade.

2: I purchased some more of these from S&S in 2025/11 and they were not very good. They were acidic and I had to eat them warm, otherwise the acid + refridgeration was so bad, it hurt my mouth. So these are not consistent, apparently. The new ones were a very thin skin/rind, which doesn't line up with this photo. I should've taken photos. Lesson learned.

3: Purchased 03/2026 from Wgm. This one was a little off, but it was alright. Worth eating, this time.

4: Purchased 03/2026 from Sh. This one is OK.

5. Purchased two 04/2026. Not good. Made me hate oranges. I don't know what they put in this one.

6. Another one from 03 or 04. Been in the fridge for a few weeks. Also just average. The king's river oranges have generally not been that good. Though, the first one I got was very good.

[[File:IMG 20250530 210739103.jpg|300px|thumb|right|]]
[[File:IMG 20250531 233920508.jpg|300px|thumb|right|]]

There appear to be multiple labels from this brand. One label is a white background, the other is a black background (similar to suntreat, sunkist, and vintage sweets. There is also a pink label, though that is for a cara cara.

==Packaging==
Sold in Single Qty.

==Price==
$1 each.

==Fruit==
===Flavour===
Very good. Like an apology from the universe. 8.8/10.

===Colour===
Yellow-orange
===Peelability===
Easily peelable.
===Seeds/Seedless===
This orange is seedless.

===Size===
Large Orange. Medium size rind.

==History==
I went back in a couple of days later, and there were not many King's river left. Only the Booths Ranch. I did manage to buy 3 more. And they are still good, though I did get the runts of the lot.

[[Category:Oranges]]

PCBs

2026-05-17T09:06:58Z

ViciousCarnivore: /* Thermal Design */

PCBs. esPCB, ésePCB, 1632
==Tips/Techniques==
===List===
* https://www.eevblog.com/forum/projects/ive-never-seen-a-circuit-board-made-like-this/ - a way of using solder on epoxy board for traces. Allows for iterative development but has an up front investment. Would be interesting to see this done without the cnc, but with just a hot solder pen for modifications. That might be the answer to avoiding breadboards, which I don't like, and protoboards are better but not perfect, I should try this. There was also a follow up video, named "Howie did it - 3D printing a printed circuit board".
* https://pcdandf.com/pcdesign/index.php/current-issue/293-board-talk/18918-minimum-finished-hole-size-and-how-it-impacts-manufacturability -
<pre> "Not long ago, a customer sent us an 8-layer rigid PCB design for quotation. On the surface, nothing unusual – until we noticed the minimum finished hole size (FHS) was 4 mils. That number might not sound alarming, but in PCB manufacturing, 4 mils is a red flag. Here’s why.

The issue arises when fabricators drill a plated through-hole (PTH) and deposit copper during plating. The remaining diameter after this process becomes the finished hole size. A 4-mil FHS with a tolerance of ±4 mils technically ranges from 0 to 8 mils. That kind of spread becomes nearly impossible to maintain in volume production.

To make a PTH, fabricators start with a larger drill size and plate copper along the walls. The smaller the drill, the shorter its flute length – and the fewer panels manufacturers can drill in a stack. Large-scale factories typically drill 10–20 panels at a time for efficiency, but a tiny drill bit can’t survive that workload, which drives up cost and limits throughput. In practice, the smallest common drill diameters used in offshore volume production sit around 8 mils (0.2 mm). After plating (about 1 mil per side for IPC Class 3), that leaves a finished hole closer to 6 mils.

Designing for 4 mils simply doesn’t align with what’s achievable at scale. Could we force it? Yes, by over-plating, doubling the copper thickness and dramatically slowing the line. But that’s a recipe for higher costs, longer lead times and questionable yield.

Bottom line: A 4-mil finished hole is feasible only in small prototype runs, not in cost-sensitive, high-volume production.

When considering 4-mil finished holes in a PCB design, pause. Building prototypes in a specialized facility is possible, but impractical for volume production. Instead, explore HDI strategies with laser-drilled microvias to achieve density without sacrificing manufacturability or cost."</pre>
====Rivets====
* http://fab.cba.mit.edu/classes/863.16/doc/tutorials/PCB_Rivets/ - Guide on PCB rivets, 2 size recommendations, and how to flatten one side with a punch and hammer after installing. There are many rivet guns for sale, but it's good to see that the fundamental idea of rivets needs only a hammer and a punch.
* https://www.eevblog.com/forum/repair/rivetseyelets-for-pcb-repair/ - Places to source rivets/eyelets
* https://www.eevblog.com/forum/projects/ive-never-seen-a-circuit-board-made-like-this/25/ - Page 2 of this thread, someone suggests that eyelets are prone to breaking traces due to differences between PCB and metal expansion. You may be better off using stranded wire.
* https://maker-hub.georgefox.edu/w/index.php?title=Through_Hole_Press&mobileaction=toggle_view_desktop - You can use a press to close the rivets. (This makerspace also has some other interesting equipment, such as a Voltera V-One, along with other shops. It's a useful resource to review as the wiki pages of equipment are thoroughly documented with usage and safety instructions).

====Thermal Design====
* https://www.ti.com/lit/an/snva419c/snva419c.pdf - Copper thickness and power dissipation.
* https://www.eevblog.com/forum/manufacture/need-help-desciphering-layout-specs/ - reference for TI data sheet.
* https://lpt-inc.com/about-us/gallery/ - High power ceramic circuit board. The ceramic would insulate of course.
See also [[Software#Simulations]]

====Using Image Processing to detect PCB Errors====
[[Software#Ansys]]
====Layout Design Tools====
[[Software#Layout_Design_Tools]]

[[Category:online notes]]

PCBs

2026-05-17T09:03:55Z

ViciousCarnivore: /* Thermal Design */

PCBs. esPCB, ésePCB, 1632
==Tips/Techniques==
===List===
* https://www.eevblog.com/forum/projects/ive-never-seen-a-circuit-board-made-like-this/ - a way of using solder on epoxy board for traces. Allows for iterative development but has an up front investment. Would be interesting to see this done without the cnc, but with just a hot solder pen for modifications. That might be the answer to avoiding breadboards, which I don't like, and protoboards are better but not perfect, I should try this. There was also a follow up video, named "Howie did it - 3D printing a printed circuit board".
* https://pcdandf.com/pcdesign/index.php/current-issue/293-board-talk/18918-minimum-finished-hole-size-and-how-it-impacts-manufacturability -
<pre> "Not long ago, a customer sent us an 8-layer rigid PCB design for quotation. On the surface, nothing unusual – until we noticed the minimum finished hole size (FHS) was 4 mils. That number might not sound alarming, but in PCB manufacturing, 4 mils is a red flag. Here’s why.

The issue arises when fabricators drill a plated through-hole (PTH) and deposit copper during plating. The remaining diameter after this process becomes the finished hole size. A 4-mil FHS with a tolerance of ±4 mils technically ranges from 0 to 8 mils. That kind of spread becomes nearly impossible to maintain in volume production.

To make a PTH, fabricators start with a larger drill size and plate copper along the walls. The smaller the drill, the shorter its flute length – and the fewer panels manufacturers can drill in a stack. Large-scale factories typically drill 10–20 panels at a time for efficiency, but a tiny drill bit can’t survive that workload, which drives up cost and limits throughput. In practice, the smallest common drill diameters used in offshore volume production sit around 8 mils (0.2 mm). After plating (about 1 mil per side for IPC Class 3), that leaves a finished hole closer to 6 mils.

Designing for 4 mils simply doesn’t align with what’s achievable at scale. Could we force it? Yes, by over-plating, doubling the copper thickness and dramatically slowing the line. But that’s a recipe for higher costs, longer lead times and questionable yield.

Bottom line: A 4-mil finished hole is feasible only in small prototype runs, not in cost-sensitive, high-volume production.

When considering 4-mil finished holes in a PCB design, pause. Building prototypes in a specialized facility is possible, but impractical for volume production. Instead, explore HDI strategies with laser-drilled microvias to achieve density without sacrificing manufacturability or cost."</pre>
====Rivets====
* http://fab.cba.mit.edu/classes/863.16/doc/tutorials/PCB_Rivets/ - Guide on PCB rivets, 2 size recommendations, and how to flatten one side with a punch and hammer after installing. There are many rivet guns for sale, but it's good to see that the fundamental idea of rivets needs only a hammer and a punch.
* https://www.eevblog.com/forum/repair/rivetseyelets-for-pcb-repair/ - Places to source rivets/eyelets
* https://www.eevblog.com/forum/projects/ive-never-seen-a-circuit-board-made-like-this/25/ - Page 2 of this thread, someone suggests that eyelets are prone to breaking traces due to differences between PCB and metal expansion. You may be better off using stranded wire.
* https://maker-hub.georgefox.edu/w/index.php?title=Through_Hole_Press&mobileaction=toggle_view_desktop - You can use a press to close the rivets. (This makerspace also has some other interesting equipment, such as a Voltera V-One, along with other shops. It's a useful resource to review as the wiki pages of equipment are thoroughly documented with usage and safety instructions).

====Thermal Design====
* https://www.ti.com/lit/an/snva419c/snva419c.pdf - Copper thickness and power dissipation.
* https://www.eevblog.com/forum/manufacture/need-help-desciphering-layout-specs/ - reference for TI data sheet.
* https://lpt-inc.com/about-us/gallery/ - High power ceramic circuit board.
See also [[Software#Simulations]]

====Using Image Processing to detect PCB Errors====
[[Software#Ansys]]
====Layout Design Tools====
[[Software#Layout_Design_Tools]]

[[Category:online notes]]

Materials

2026-05-17T08:59:57Z

ViciousCarnivore: /* Ceramic */

Material resources

==List==
* https://www.eevblog.com/forum/manufacture/tough-sheet-dielectric-material/ - Discussing paper sized dielectric materials, I read through some of this. There are many options discussed.
* https://web.mae.ufl.edu/designlab/Lab%20Assignments/EML2322L-Tolerances.pdf - Typical Tolerances of machining processes. Looking at this short doc, you can see that anything that requires the highest tolerance will be ground/polished down by some sort of surface finishing. That was what was used for making the ill fated hubble mirrors according to "The Perfectionists: How Precision Engineers Created the Modern World" by Simon Winchester, which in that book was rated as the highest level of machining tolerance. Rated higher than semiconductors, though it is debatable as to which is more complex. It's not uncomon common for resources to list the top most of anything when in fact one of the earlier entries was the true winner.

==Ceramic==
* https://ferroceramic.com/ This website has a list of 15 different ceramic materials that they machine. There is a writeup on each material and it is an interesting intro to industrial ceramics that are actively used. Silicon is mentioned. Some others: Macor, Mullite. Note that these are smaller parts (20"x20"x8").
* https://lpt-inc.com/design-guidelines/ - Laser Machining of ceramic substrates.

==Metal==
* https://www.approvedsheetmetal.com/sheet-metal-fabrication-images These folks look like a fair sheet metal fabricator. Available for parts in single qty.
* https://basiccopper.com/thicknessguide.html - Metal (copper) Foil Thickness guide. Remember that what applies to copper may not apply to other metal foils.

[[Category: online notes]]

Radio

2026-05-17T08:45:33Z

ViciousCarnivore: /* List */

IntegratedCircuits

2026-05-17T08:19:04Z

ViciousCarnivore: /* DACs */

Look at the die, and you will understand how it works. Then, say: "I C".

"This is how you recycle electronics"

==List==
* https://www.eevblog.com/forum/projects/need-to-know-about-generic-arm-processor-die-manufacturers/ - 5-10k for a micro wafer
* https://www.eevblog.com/forum/projects/unknown-circuits-die-pictures/ -
<pre>
note that with identifying dies, you follow them like a maze, and look for bridges across different
sections. in this chip, there is a distinct general flow from the bottom left to the top right.
There are distinct bridges visible on the first section, and also you can see the two near identical
inputs (which in this case are a differential input according to the author). It also helps to colour
sections differently, if they can be identified.
</pre>
* https://www.eevblog.com/forum/chat/warning-lm317k-duds-from-digikey/?action=dlattach;attach=2480371;image
* https://www.eevblog.com/forum/chat/warning-lm317k-duds-from-digikey/?action=dlattach;attach=2480363;image
* https://www.eevblog.com/forum/chat/warning-lm317k-duds-from-digikey/?action=dlattach;attach=2480379;image
There are no standards for what a given component name means wrt the die. You have to decap them.
And you have to know IC design. Another thing to learn. To make it worse, technically, there can even be batch variations from one die to the next (at its root, it is chemistry, which means the source chemicals have to be correct. How many IC designers are chemists?). Endless complexity. The more you look at it, the more complex it gets.

==IC Design==
As you go smaller you get less voltage but go faster and have higher frequency. Therefore, instead of measuring voltage or current you might measure frequency changes, because high frequency is more accessible than access to voltage or current. Per amp hour 579.

==74 Series Logic==
[[File:L301741-02-112698239.gif|150px|thumb|right|Logic Gate Optocouplers]]
People don't usually talk about these, but in addition to standard optocouplers, there are also logic gate optocouplers. SCRs as well.

==ADCs==
Making analog to digital converters is as simple as A-D-C.

===Types===
AoE covers these thoroughly in 13.5.2.
A simple write up is in Modern Electronic Test Equipment 2nd Edition, by K. Brindley.
He says:
* Dual Slope - Integrator ramp up, then count clock cycles as it goes down.
* Sucessive Approximation Converter / SAR - The ADC that calculates multiple times based on the internal DAC or reference voltage, narrowing down the voltage to the correct answer (within the # of bits it is).
AoE disagrees with the definition of the SAR, and also discusses a few other types of ADCs, though ultimately categorizes them into 4 categories (though 1 and 2 appear similar and also 3 and 4 appear similar). Basic principles between them are similar, but I'm sure the devil of complexity is in the details. According to METE, you are either comparing voltages, or counting based on integration. "With a name like Delta Sigma, it has to be complex."

===Voltage references at 2.048 volts===
Here's one example:
LM4040 - https://www.ti.com/lit/ds/symlink/lm4040.pdf
It can also run at 4.096 volts. It's used in Nuts and Volts 2020 issue 5 as a (stable) reference voltage for the Nano and SS495A hall effect sensor. It is a zener diode. See also the note in [[Circuit_Building_Blocks#Simplest_Band_Gap_Reference]].

==DACs==
Two fundamental DACs
* Resistor String DACs (discrete)
* R-2R Ladder DACs
The Resistor String type will require (large) amounts of resistors and analog switches. These are practical on a chip (e.g. AD5689, DAC8564). This is 2 to the power of N resistors.
The R-2R Ladder type uses quite a bit less, and is practical for circuit board assembly from discrete components. Reference: Practical Electronics June 2025, Page 72. This is 2 x N resistors (N being the bits). There are different architectures of these.

Also consider the technique in the magazine of a complementary (inverted, I think) PWM signal along with a normal signal to speed up the settling time. (Page 73).

AoE covers basically similar material to the magazine, though with less errors and more detail.

==Packaging==

* https://semiengineering.com/the-need-for-open-molded-plastic-packages/ - Open Molded Packages. Manually wire bonded. Possible to optimize from the silicon to the chip leads. See also: https://www.qptechnologies.com/products/ocpp/

[[Category:online notes]]

Crystals

2026-05-16T07:07:49Z

ViciousCarnivore: /* List */

A rock that vibrates. Piezos. You can have your piezo and eat it too (if it's salt).

Computers are a calculating rock.

LEDs are a rock that emits light.

Magic rock.

===List===
* https://youtu.be/MbPeYd1N1Xg - How to characterize crystal parameters. This video walks through turning a crystal into a strict electrical circuit, so you can adjust the frequency, or calculate what capacitance is needed. This subject matter is also covered in AoE, 3rd edition, section 7.1.6.
* https://www.statek.com/technical-papers/ - Some simple and good data sheets on quartz crystals. Recommended. Maybe someday they will put all of them online.
* https://www.youtube.com/watch?v=yYGwfVnGAdg - The Signal Path youtube channel. Comparing Crystals with Ring Oscillators. The ring oscillators (based on 74 type logic) are much less accurate.

[[Category: online notes]]

2026-04-01T18:05:11Z

ViciousCarnivore: