So, therefore: passwords shouldn't exist, and you should create sessions via email links/tokens. Then also offer Passkeys as a faster login.
1,050 karma · joined July 18, 2010
So, therefore: passwords shouldn't exist, and you should create sessions via email links/tokens. Then also offer Passkeys as a faster login.
Aside from email accounts potentially being compromised or SMS interception, this is honestly the way all sites should be going now. But more seriously, there should be a way to use only Passkeys with a backup identification method in case you lose your Passkey.
The new threat? Browser password managers are insecure. Anyone can sit down at my machine if it's unlocked and Passkey their way into any of my accounts. What good is that? Why doesn't Chrome use my Google account password before allowing auto-fill/login? (Obviously I don't use Chrome's password manager, but it's a real concern for everyone else.)
https://aphyr.com/posts/379-geoblocking-the-uk-with-debian-n...
Health insurance isn't tied to a company? Your ability to survive and feed your family isn't tied to your company? Lack of opportunities in the job market? Lack of equal salary/benefits at alternative companies? Non-competes, H1-B visas....
> so if you don’t like how they chose the leader or what they’re doing, you can leave.
Just one small thing Ben: leave to work for who? Who isn't hiring CEOs and running businesses the same way as everyone else?
I mean.... ParEdit [1] and ParInfer [2] have been around for a long time now. Structural editing is basically ancient. Lispers have been doing this for a long while, `slurp`ing and `barf`ing their parens.
[1]: https://paredit.org/
> ...because this is a frontend like LLVM or GCC that compiles instead of bytecode, uh, to Python AST, um, so this Lisp compiles entirely to Python
How is it faster to press `*` than `Ctrl-I` in any other rich text editor?
> The idea that it is meant to be seen is no more than a personal preference.
Actually, the entire philosophy of Markdown is that, even if you didn't process it into HTML or some form of rich text, it uses common conventions that have been used across Usenet, IRC, and plaintext files for years, and is thus readable without ever being processed. In fact, you can likely take various plaintext files and process them and they'll gain many incidental markups and highlights.
Meaning, Markdown is Markdown without needing to be turned into HTML or rich text. It is, in itself, a great way to universally markup text as people have been doing online for years.
Yes, Salesforce consumes companies whole. Just like they did with Heroku and others.
Yes, and, Guix is actually a "meta" package manager that understands other packages like Python PIPs and Node NPM packages, so you can define all of that in one build config file.
Rather than wanting the web platform to be first class, they really want it to languish as a second-class citizen. Really sad, seeing as they also fired devs, and invested in "AI" instead.
I could probably use Obsidian/Logseq mobile if I wanted to. (Again, because it's Markdown... which is about universal now.)
And like, it's Markdown. It's meant to be readable as-is, so I can probably figure out any alternative method. I'd obviously miss out on tag searching and graphing, but I don't have heavy mobile use right now.
Edit: Yeah, the GitHub mobile app ain't the worst. I can probably find a way to get local git on my phone, and then just use Obsidian Mobile if I want to get fancy.
Fine, I uhh, I'll speak for it.
Foam is to VSCode, what Org (and Org-Roam) are to Emacs.
As a former org-roam user, I ended up preferring it because my end goal was to convert my notes to HTML and blog posts, and org is poor at that as HTML is not valid org code whereas it is in Markdown. There's just a whole host of markdown-it plugins [1] out there to add footnotes and all sorts of things to Markdown, and Foam also understands Jekyll frontmatter YAML, which is perfect for blog post tags/categories.
[1]: https://www.npmjs.com/search?q=keywords:markdown-it-plugin
And because it's just an extension to VSCode, it works with every other extension: https://foambubble.github.io/foam/user/getting-started/recom...
This gives it similar power and flexibility to Org-Roam, as you can extend the model to improve the editing experience.
So why don't I use Obsidian, Logseq, and others? Because they're dedicated apps, and now I have to bring various half-baked plugins into them to give me the power my editor already affords me. With notes, half your time is spent editing, so why wouldn't you want your editing to be as close as possible?
Secondarily, nothing stops me from using everything altogether, since it's all Markdown, I can load up my note repo in Obsidian or Logseq and others, and continue editing in VSCode and Emacs!
It's just chill and sets the mood.
Under Eric Schmidt they were engineer-driven, during the golden era of the 2000s. Nowadays they're MBA driven, which is why they had 4 different messaging apps from different product managers.
https://calendar.google.com/calendar/u/0/embed?src=9t07jqib6...
"Randomly" is colloquially used to mean "chaotically" in a lot of contexts, and the chaotic they mean is "unpredictable enough as to seem or feel random".
While DVORAK may only be a 5% improvement over QWERTY, a steno keyboard is vastly superior in typing speed and ergonomics, as it's used by courtroom stenographers keeping up with recording speech. (And if you learn on a proper steno keyboard, your muscle memory won't get all confused because the keys are entirely different.)
This is a very problematic take, and is simply inaccurate when it comes to the web.
If you write zero CSS, a web page will render just fine on any display. Text will auto-wrap and be legible. The web is "responsive" by default. It's the designers who try to rigidly align things with specific widths, explicit sizes, and absolute values that make web pages harder to read and use.
Meaning, any given element shouldn't have a `width`, it should have a `max-width` instead. Text should have a relative font size to headings or other text. Alignment should take into consideration overflow, as it will by default with flexbox and grid. Everything by default will flow in some way and try to make it onto the page.
It's all the violence of designers that makes things both less device friendly and less accessible, just like these poor contrast decisions.
Uh, the Switch is an NVIDIA Tegra SoC...