Security architect, consultant, and writer.
#appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
I think I have found my mission in life. Here's the plan that ChatGPT made for me:
Define the proposal. State that teh is an optional alternative spelling of the, with identical meaning, pronunciation, grammar, and formality.
Create a campaign name. Use something credible such as “The Teh Project” rather than presenting it primarily as a joke.
Register a domain. Build a permanent website explaining the proposal, rationale, rules, adoption status, and project governance.
Publish a formal specification. Define capitalization, pronunciation, grammar, search behavior, autocorrection behavior, and compatibility with the.
Create a public repository. Store the specification, website source, dictionaries, integrations, citations, and issue tracking on GitHub.
Write the main argument. Explain why teh is unusually common, universally understandable, unambiguous, and suitable for recognition as a variant.
Address objections. Explain why recognizing teh would not require accepting every common typo as standard English.
Create optional dictionaries. Publish opt-in en-US-teh, en-GB-teh, and similar dictionaries that accept both the and teh.
Build software integrations. Add support for CSpell, Hunspell, LanguageTool, Vale, LibreOffice, VS Code, Vim, browsers, and mobile keyboards.
Create an adoption pledge. Let writers, editors, publications, and software projects publicly recognize teh as an acceptable alternative spelling.
Recruit intentional users. Encourage people to use teh naturally as an article, not merely when discussing or joking about the campaign.
Recruit independent publications. Ask blogs, newsletters, journals, authors, and documentation projects to permit intentional use of teh.
Document intentional usage. Record the author, publication, date, quotation, URL, country, genre, and evidence that each use was deliberate.
Build a durable citation corpus. Archive examples through print, ISBN publications, institutional repositories, DOI records, and web archives.
Separate independent evidence. Do not count campaign-owned pages, copied text, automated posts, or repeated material as independent adoption.
Commission research. Encourage independent studies of comprehension, reading speed, attitudes, corpus frequency, and perceived correctness.
Seek independent media coverage. Pitch the project as a serious spelling-reform experiment and allow journalists to cover both support and criticism.
Update Wiktionary when evidence exists. Propose changing teh from only a deliberate misspelling to a documented nonstandard alternative spelling.
Use Wiktionary discussions properly. Present durable citations and disclose your involvement instead of recruiting supporters to overwhelm the process.
Edit Wikipedia only after outside coverage. Wikipedia should document the campaign and its effects using independent reliable sources, not declare the spelling valid.
Disclose conflicts of interest. Use Wikipedia talk pages and requested edits rather than directly rewriting articles about your own campaign.
Avoid coordinated wiki editing. Coordinate real-world adoption, but do not organize voting, account creation, or editing campaigns on Wikipedia or Wiktionary.
Submit to upstream word lists. Propose teh to the English Speller Database/SCOWL as an experimental or nonstandard article variant.
Submit downstream changes. Work through LibreOffice dictionaries, Mozilla dictionaries, LanguageTool, CSpell, editor extensions, and Linux wordlists.
Use gradual classifications. Start with “recognized nonstandard variant,” then seek “informal accepted variant,” and eventually “general alternative spelling.”
Approach typo correctors later. Ask tools such as codespell to stop correcting teh only after substantial intentional adoption exists.
Submit evidence to dictionaries. Send lexicographers independent quotations, corpus statistics, research, software adoption, and style-guide decisions.
Approach style guides. First ask editors to retain intentional uses, then later seek unrestricted acceptance in formal writing.
Publish transparent metrics. Track independent adopters, publications, citations, software integrations, dictionary entries, and corpus frequency.
Set a realistic first goal. Establish teh as a documented, intentionally used, nonstandard alternative spelling before pursuing full formal equivalence.
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
For example:
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
Security architect, consultant, and writer. #appsec #Identity #windowssecurity #passwords #infosec #security #fedi22
This is bizarre coming from a company that is supposed to help improve email practices: