Unless you desperately want COMMONNAME.TLD, I’d go with the .COM for the lack of headaches. They’re ~$20 a year, which doesn’t seem like much money for the simplicity.
Unless you desperately want COMMONNAME.TLD, I’d go with the .COM for the lack of headaches. They’re ~$20 a year, which doesn’t seem like much money for the simplicity.
Car keys don’t though, as far as I can remember.
It's a stark reminder that even paid models aren't immune to market forces and operational challenges.
Maybe the real takeaway is that no business model is foolproof, and unless you can self host something you can never know when and how it will end.
[1]: https://blog.pinboard.in/blog/ [2]: https://x.com/Pinboard
___ ______
/__/\ ___/_____/\ FrobTech, Inc.
\ \ \ / /\\
\ \ \_/__ / \ "If you've got the job,
_\ \ \ /\_____/___ \ we've got the frob."
// \__\/ / \ /\ \
_______//_______/ \ / _\/______
/ / \ \ / / / /\
__/ / \ \ / / / / _\__
/ / / \_______\/ / / / / /\
/_/______/___________________/ /________/ /___/ \
\ \ \ ___________ \ \ \ \ \ /
\_\ \ / /\ \ \ \ \___\/
\ \/ / \ \ \ \ /
\_____/ / \ \ \________\/
/__________/ \ \ /
\ _____ \ /_____\/ This .signature gratuitously
\ / /\ \ / \ \ \ refers to k
/____/ \ \ / \ \ \ i
\ \ /___\/ \ \ \ b
\____\/ \__\/ o
In a lot of cases (most?) even plain-text email is rendered in proportional fonts which don’t work for ASCII art.
The default for all mobile email clients, Gmail, Outlook, and Apple Mail is now to render plain-text in proportional. Those who get it monospaced have chosen to do that. It’s also made worse by Outlook’s insistence on removing ‘extra’ linebreaks by default. AFAIK, there’s no way to switch off that behaviour except email-by-email, and you can’t know if your recipient has it or not.
Here’s are my pets in ASCII, who go out in the headers of my emails:
.-"-.
^...^ |\./| /|^ ^|\
(=^I^=) )) =(^,^)=)) {/(_O_)\}
/ " \ (( | | (( _/ ^ \_))
( |"| ))) (|||))) (/ /'\ \)
==m m== =m'm= ""' '""
Terence Eden has a really good blog post about just this topic: https://shkspr.mobi/blog/2021/01/the-unreasonable-effectiven...
Each private browsing tab has its own cookie / data bucket[1]; and
Private browsing tabs and windows are preserved across restarts. (This is optional and can be configured to forget them upon restart.)
These make it practical to use private browsing for nearly all browsing, which isn't really the case in other browsers, where private browsing is clearly designed as an occasional-use thing. (And of course if you use private browsing for most things, you can still open regular windows for sites where you want to stay logged in.)
[1] If a link or script in a tab opens a new tab or window, then they share the same cookie bucket. This preserves compatibility with sites that require such a flow.
I am totally stumped – how do you enable this on the Mac? I can’t find the option at all, and Google is no help.