/ internet architect : network engineer / ☧ Α Ω |the Way| sola Scriptura ΧΣ μόνος Δυνάστης •data analyst• {anon to the clueless} ~proponent of we the people~
Joined June 2008
- Tweets45.4K
- Following5.9K
- Followers5.4K
- Likes48.5K
wheeeeee
Code-execution flaw in UEFI firmware threatens most servers on planet Earth arstechnica.com/security/202…
ken posting a lot more on x it seems...not all doctors are bad, he posts some good stuff, check his feed 👍
Many Americans are trying to make better choices and big-food is actively making this difficult by making the Ingredient List very difficult to read. This would be an easy fix...
1. Increase Font Size
Current Regulation: Minimum font size is 1/16 inch (1.6 mm).
Recommended Change: Increase the minimum font size to at least 1/8 inch (3.2 mm) or a point size equivalent of 12 points, which aligns with accessibility guidelines for printed materials.
Reason: Research shows that many older adults, individuals with presbyopia, and those with low vision struggle with smaller font sizes. Larger fonts improve legibility across demographics.
2. Improve Contrast Requirements
Current Regulation: Text must contrast with the background, but no specific standards are defined.
Recommended Change: Implement a minimum contrast ratio of 4.5:1, as per the Web Content Accessibility Guidelines (WCAG) for readability.
Reason: A defined contrast standard ensures that text is distinguishable from the background, benefiting individuals with visual impairments.
3. Mandate Clear Typography
Current Regulation: No restrictions on font style.
Recommended Change: Require sans-serif fonts (e.g., Arial, Verdana) and avoid decorative or stylized typefaces.
Reason: Simple, clear fonts enhance readability, particularly for people with dyslexia or cognitive impairments.
4. Allow Dynamic Labeling Adjustments for Smaller Packages
Current Regulation: Labels on packages smaller than 12 square inches can use reduced font sizes.
Recommended Change: Require the use of fold-out labels, QR codes to provide legible ingredient information without reducing font size.
Reason: Smaller font sizes compromise accessibility; alternate methods preserve readability while accommodating limited space.
5. Use Plain Language
Current Regulation: Ingredient lists must use common or usual names but may still include scientific terminology.
Recommended Change: Mandate plain language descriptions alongside technical names (e.g., "sodium chloride (salt)").
Reason: Simplifying terms ensures greater comprehension for individuals with low literacy skills.
6. Standardize Allergen Formatting
Current Regulation: Allergens can be declared in the ingredient list or a separate "Contains" statement.
Recommended Change: Require a consistent allergen section in bold or highlighted text, clearly separated from the main ingredient list.
Reason: Improves visibility for people specifically looking for allergen information.
7. Add Digital Accessibility
Current Regulation: Labels are static with no interactive features.
Recommended Change: Encourage the use of QR codes or NFC technology on packaging to link to accessible digital formats (e.g., larger text, audio descriptions).
Reason: Provides enhanced accessibility options for individuals with disabilities.
These stroke-of-the-pen changes can be made Day 1 and any argument from big-food would reveal their obvious attempt to keep The People in the dark...
@RobertKennedyJr @MartyMakary @DoctorJanette @DonaldJTrumpJr @US_FDA @FDAfood
anyone have a favorite digital LXX?
i need a good one i can look at on my phone
i have accordance but their mobile app is horrible
you mostly see people talking about proton, i would recommend tuta over proton 👍
**for the avg user, that is, neither are needed if you are a tech person
🚨 BREAKING Gmail Users Need to Read This!
⚡️Google just admitted it's spying on your emails⚡️
About time to switch to a #private alternative. Enjoy! 😃 🔐👉 tuta.com/blog/best-private-e…
#GmailAlternative #DeGoogle #Google #Tuta #privacy
it's 2026, the gospel is... "Jesus"
get a copy of His word and read it (start in John)
generally, when you see/hear"what is the gospel" these days it = a loaded question
people have been telling you to de-google for a long time now...if you continue to use them, that's on you
it’s good to check what browsers you main
i would say brave, librewolf, mulvad
...but you may need one for testing the diff engines, take a look here:
@privacytests
privacytests.org/
i would like to see a few more tested like orion (good for old devices)
this is pretty horrible:
If X labels your post as low quality or misinformation, people who don't follow you see a warning on it, and they can't like, reply, repost, bookmark or share it. The code doesn't say what gets a post that label.
it is curated (for you) though 🤷♂️
Who shall lay any thing to the charge of God’s elect? It is God that justifieth. Who is he that condemneth? It is Christ that died, yea rather, that is risen again, who is even at the right hand of God, who also maketh intercession for us.
— Romans 8:33-34 kjv
agreed
Holly needs to be called out for these falsities (statements). We servants of the King will not stand for your perversion of God's word...and yes, posting/teaching such 🗑️ is unscriptural nonsense.
pro tip: when you see a post, click on their profile pic, click on the join date, see where they are posting from
if you are posing as an american and posting about some hot topic...but your profile says you are posting from nigeria or south asia...you can bet you are getting a 👎
what you generally find is a mismatch on the profile and the profile detail (click on the join date)...surely grok should be able to pick up on this
the content usually is a "mismatch" as well
here's an idea, publish bugs/exploits publicly
create a central reference "place" to do this, vendors should also monitor this "place"
then you don't have backroom shenanigans happening in a company regarding such matters
