So you have. My bad. Seem to have filtered it out since it pops up in places where I'm usually mentally filtering for relevance to the issue in question.
#2) I stay away from Italics because they actually make reading more difficult for those of poor sight. This is counterproductive for making sure you can get the most important bits of your message across and if caught without my glasses, your italics are very difficult to see. Caps stand out, generally have thicker, or less visually ambiguous glyphs, and are immediately visually recognizable. I'd use bold, but the editor doesn't seem to support it through any syntactic convention I'm used to.
I consider capitalization to be a way of making sure text stands out, as I've been legally blind for most of my life, and while I'm not as bad anymore, I'm painfully aware of the challenges people with visual impairment face, Therefore, Italics generally take on a less meaningful role in the context of emphasis for me, due to their ability to be more easily mistaken when being looked at. So unless communication is something fairly trivial, or an out-of-band thought, I generally use bolding and capitalization imstead.
By the way, screen readers were not well known for reading out typographical characteristics, so often, a visually impaired person will have to figure out where it LOOKS like emphasis may have been in text. For more don't's to make your content consumable by the visually impaired, have a look at
Section 508 Accessibility Guidelines, it should be trivial enough to Google.
Have a gander at https://www.w3.org/WAI/
And even
https://sw00000004.schoolwires.net/site/handlers/filedownloa...
Or for that matter ANY guide on internet accessibility.
Furthermore, I don't understand why you thinking it's yelling takes anything away from the conventional point of yelling, which is to... provide an auditory form of emphasis via audio signal amplitude modification. The changing of typographical glyphs, draws the eye to content (when said change can be discerned), and primes the mind that Thar be a point to be made here. Perhaps that is my own brand of social ineptitude, nevertheless, I do make a habit of questioning anything that doesn't make sense on functional and aesthetic grounds due to an interest in minimizing overhead in communication and minimizing the number of restrictions on the myriad ways people may attempt to express themselves.
I don't want to derail the thread anymore, and despite this finer point of typography and content rendering in a way which is conducive to the visually impaired being a rather passion invoking topic for me, I assume everyone else is not here for that. I'd prefer not to have too continue, seeing as it breaks yet ANOTHER guideline.
I'd also like to direct your attention to
Eschew flamebait. Don't introduce flamewar topics unless you have something genuinely new to say. Avoid unrelated controversies and generic tangents.
Be civil. Don't say things you wouldn't say face-to-face. Don't be snarky. Comments should get more civil and substantive, not less, as a topic gets more divisive.
Both points which you (though you are doing it I assume in pursuit of the execution of your your duties to the best of your ability) are straying rather close to.
Instead of providing a reasonable and substantive reply to any of the content in my original comment, you have quibbled over the way it was delivered, detracting from the quality of the conversation despite knowing the typographic convention was being deployed in a way reasonably discernable as conveying emphasis.
So if you are a moderator, consider your message received. I will do my best to abstain from typographic conventions that offend your company's sensibilities to the detriment of my own personal readability without my glasses, and to anyone else's.
Thank you for the link as well. I hadn't noticed the Guidelines on the bottom, again, de-emphasized textual prominence, being a bit of an issue for me.
If you have any ability to escalate feedback, implement bolding and accessibility aids for the love of all the visually impaired.
If you'll excuse me, I'd like to see what I can learn from other's input, I have largely tried to keep comments substantive and on topic.
There are many industries with similar, parallel, practices that are directly at odds with serving the "user." For example, groceries. A typical grocery store presents a selection of products in a grocery aisle. This presentation is not optimized to give the shopper the best experience, lowest prices, or highest quality products.
The products, and product displays, are optimized to extract the most profit from the shopper, often resulting in inferior products. Grocery stores also collect and analyze reams of data about individual shoppers -- again, not for the purpose of providing better value for the shoppers, but for extracting maximum profit from them. Want that data back? Good luck!
My wife lost her purse with (it turns out) the master key to my minivan. The minivan is maybe worth $4k. (I'd have to fix it before I could sell it.) Getting the key replaced is $750. Because that is what Toyota wants to charge and nobody else can do it.
If I had an older car, it would be a cheap visit to the local Home Depot to duplicate the remaining key.
I haven't replaced the key. I don't value the threat model that they theoretically protect me from. I do value the convenience of being able to replace the key. But it isn't worth $750 to me. Instead that is just one of several things that are on my list of "replace if X happens".
Not very successfully.
> your printer tries to stop you from using ink cartridges from a different manufacturer
I can inject ink into the port, for cheap.
> your car will often strongly discourage you from getting it serviced by anyone other than an authorized dealer.
Only the top-range cars, for rich and upper-middle-class people, who have the ability to buy different but won't because it's a silly status symbol.
A better comparison would be walking to the checkout line with $brand_A sugar and watching the clerk put down $brand_B and start the motions of scanning the barcode forcing you to make the active move of stopping them to say "no, I know what brand I picked out, get out of my way and let me buy $brand_A"
Simply suggesting a what works best on the side of a box can't reasonably be compared to actively halting an operation deliberately initiated by the user.
The problem is twofold:
1. There should be a single checkbox that says "keep your grubby mitts off my machine." As it is now, users must proactively keep Microsoft out. Even then updates can give Microsoft the keys again.
2. Microsoft cannot be trusted to work in the user's interest. They always steer the user towards Microsoft products.
Corporations have more rights than individuals, and they have less responsibility. We as a society have decided that Corporations are more important than the individual and we made that determination because of jobs. We must treat corporations gently or they will move all of their jobs to other countries. What you are railing against is just a small piece of the puzzle.
I believe it to be accurate to say that there is a party with a vested interest in making sure that Corporations have more rights on paper. I do not believe it terribly fair to make the assumption however that EVERYONE is okay with that.
Don't thank God, thank the people that actually made it possible. RMS, for example. You don't have to use LFS to be free. You can use any other free software distribution.
These types of practices only started when people started fighting over arket share once PC's started to become more popular, and most of the people who were working on them were either too busy making cool stuff to complain, or being ignored as geeks.
The Free Software movement, however, has been there for a long time. Just nowhere near as well funded.
Having rules this complicated and debatable as to when they've been violated is like having no rules at all. The rule that users should have complete read/write access to all of the software running on their own machine is enough.
Reroute their water into your system?
Siphon off their power? (Which embedded cryptocurrency miners and unwelcome analytics and data gathering are a perfect example of.)
Or use their cellular data, for that matter?
I realize there may be a lot of dislike of this ethos as it may be seen as leaving money on the table, but fundamentals are only fine to skip over when you actually show a credible mastery of them in the first place.
The tech industry's ability to ask before doing has been far from proven. It's only now that people have started to understand enough to realize just how much has been going on out of sight.
I wish, but this hasn't been the case since 2005. LFS won't help if your firmware limits kernels to those signed by Microsoft, or help you decrypt the signal sent to your monitor with your monitor vendors pubkey, or stop TCPIP running on the proprietary copy of Minix that Intel installed for you.
General purpose computing was lost a decade ago.
I've also tried to avoid EFI and Intel processors. My previous laptop used OpenFirmware and a Geode processor, which I'm assuming never had a hidden OS/Web/etc. stack like Intel's. I eventually upgraded about 4 years ago, when the first laptop (a refurbished ThinkPad x60s) got the FSF's "respects your freedom" certification. It's not perfect, since it's got an Intel processor and I think there's EFI running underneath LibreBoot, so I've been keeping an eye out for a replacement.
I don't think we need to give up. There are some promising developments, with "bottom up" efforts like RISCV and "top down" mitigation efforts like those of Purism. 'Consumer electronics' may be a lost cause (without legal intervention, at least), but there are still options for those who prioritise digital freedom above convenience, price, etc. (e.g. Talos II)
While your entire principled nature is worth admiration, may I ask what your objection to EFI is?
As far as I know it's an open standard, and there's nothing fundamentally bad about it.
I know lots of people have issues with UEFI Secure Boot (mostly based on FUD), but secure boot is strictly optional. Not to mention many UEFI firmwares lets you load your own keys: I.e. it respects your freedom.
Are you sure you're not accidentally conflating UEFI with Intel Management Engine (which is indeed spyware)?
Pretty sure
> may I ask what your objection to EFI is?
> I know lots of people have issues with UEFI Secure Boot (mostly based on FUD), but secure boot is strictly optional.
I'm not the most knowledgable about this, but as far as I understand it secure boot is a hard requirement for Windows 8 hardware certification on ARM, although as you say it's optional on x86 (presumably for legacy reasons, like users expecting to have control over their machines). This is essentially the same strongarming of OEMs that contributed to killing OS/2, BeOS, etc. so the fact it's (currently) optional for certain machines doesn't quell my concern to having so much of the world reliant on Microsoft keys.
> Not to mention many UEFI firmwares lets you load your own keys: I.e. it respects your freedom.
That's not a feature I have any intention of using, and prefer to "vote with my wallet" by trying to avoid it and support alternatives.
(This is based on my existing understanding, supplemented with skims of pages like https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_In... )
> As far as I know it's an open standard, and there's nothing fundamentally bad about it.
Purely anecdotally/ranting, my only real experience with EFI was trying to boot from a USB stick on someone's machine (to try and recover some of their data, if I recall). I couldn't figure out how to even get a menu or anything, so I gave up.
In contrast, it didn't take me long to feel quite at home in the Forth prompt of OpenFirmware; despite never having used Forth before.
Fair enough, but it is a security feature I can use to harden my system against attackers. Several Linux-distros support this OOB these days.
But if you're not interested, no pressure. Everything works fine without it.
> Purely anecdotally/ranting, my only real experience with EFI was trying to boot from a USB stick on someone's machine (to try and recover some of their data, if I recall). I couldn't figure out how to even get a menu or anything, so I gave up.
EFI is different for sure. I can't say I blame you for not wanting to read up all about it[1] when you had other stuff to do.
That said, EFI is conceptually and practically much simpler than traditional BIOS boot. It doesn't rely on magic bytes being written in specific sectors, it doesn't put a limitation on boot devices or types.
(Overly) simplified: It just says that if your medium of choice contains a file a \efi\bootx64.efi on a FAT-partition, your machine will be able to boot that thing with no further action required on anyone's part.
As such creating a bootable medium involves 1. having the right FS-type, 2. copying the files.
I haven't looked into OpenFirmware so I can't really compare, but compared to traditional BIOS I find EFI conceptually much simpler, much more manageable and to top it off much more secure.
I'm happy.
[1] https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-...
It is; but BIOS is a very low bar to beat ;)
Switching from the Amiga to the PC around 2000, it surprised me that such a primitive, legacy system like BIOS was still in use at all.
I can literally pop open a dialog box asking for permission to browse your Documents and extract some 'interesting' data and I bet 70% of users will click "ok", since, well, that's what The Computer (like it's its own sentient entity) "wants me to do", and I need to get my work done.
Your suggestion simply cannot work, because 99.9999% of users don't hack their own .vimrc and have no idea what the heck those annoying boxes are asking of them, but they do know that by clicking "OK", the box goes away.
Yes, there are a LOT of defaults people will just "go with" on the basis of path of least resistance. That does not absolve we programmers and software engineers to write well behaved, principled software that respects the sanctity of the user's digital sovereignty.
A computer is a tool, not a playground for the first person to throw code at it. Attitudes in the vein of your comment aren't uncommon, but that doesn't make them right.
The fact it has taken so long for technical literacy to get to where it is at is because most people have grown accustomed to the machine making decisions for them because it didn't occur to the programmer to present the option to think for themselves. Or, that saintly programmer wanted to, but got shot down in the name of UX and quick KPI boosts rather than creating an experience of the computer as a tool a user can do something with.
So again, I beg to differ.
This is why computing is going off the rails, and computational literacy is critical.
The computer belongs to the User. It's sole purpose is to compute, FOR THE USER. If your software is running on someone else's machine. And you want data exfiltrated back to you, normatively speaking, you should ANNOUNCE your intention, EXPLAIN it, and ASK for permission, this includes honoring their decision if they say NO.
The industry has clearly been sliding down a slippery slope in which businesses have unilaterally decided that running THEIR software exempts them from having to respect the User.
This is madness. If a society operated on the types of practices that are considered "appropriate" in computing, we'd be liable to label them as savages.
Keep your interbusiness competition OFF MY MACHINE!
(Thank God for Linux From Scratch!)