devdiary

I differ from this opinion. Why would you expect "node" people to switch to "deno" - because it's better? I wouldn't expect that. I would expect that to happen only if "deno ecosystem" is better than the "node ecosystem". And ecosystem is not built in a day or few years. And this is a great move, help people to switch from "node" to "deno" while they keep using existing tools/libraries they use. And slowly, people can then switch to deno standard/3rdParty modules.

same question

A nice way to recognize contributors' efforts. Would be nice if GitHub has this feature in-built.

A good passwordless system should send both link + OTP so that when you open up in incognito or simply open on another device where you don't have email logged in, you can enter the OTP.

I like how notion does that - they have OTPs(they call it login code) as a 4 word sequence that can be easily remembered and entered on the other device/tab without reading+typing letter by letter. If you have email client open, just click on their magic link, if not, just copy-paste or type in their login code.

I'd have said it to be mandatory requirement but it does depend on the use case IMO.

A quick search on GitHub shows these results

1. SuperTokens - https://github.com/supertokens/supertokens-core (seems to have most extensive feature sets and support for multiple passwordless methods - email, phone, otp, etc.)

2. Paw.js - https://github.com/jrjr/paw.js (looks like an implementation of passkey, interesting)

Follow up question - what are some tools that can help implement secure passwordless auth?

Completely agree with that

Agree. I want to hear the same about magic links. The thread you linked about does not talk in context of an "average user". Security choices we make in context of an average-user vs power-user can be a lot different.

Writing is not easy, I see this article struggling after that great opening in the first para

I am so going to use it

> you have only one game in town — the workplace — and essentially everything else orbits around it

That hits hard

He's an inspiration. Here's his speech on his learning from open source development for 23 yrs https://youtu.be/oYP7W1gXzsI

That's an interesting story. Thanks for sharing

Revue looks amazing. But why so many twitter permissions required to login?

Same for me but there's no better alternative to autotools that I can rely upon

3 things that helped me become productive on new codebase faster

1. Start with a goal to fix a tiny issue. It will help you not go too deep, too early and yet give you an overview of the codebase.

2. Document the steps to setup dev environment in your own words and highlight the issues that you run into

3. Take time to learn the new Library or the tooling you encounter. Learn with the goal of familiarise yourself with the keywords/concepts of that library or the tools. It's okay even if you don't understand exactly how they work. When you really need to understand to solve a problem or a piece of code, you can use the keywords to quickly go to exact documentation references to learn more. A thumb of rule for me is to not invest more than a day to learn these new concept continuously(I can always come back to it if I see the need for that)

This is amazing. Thanks a lot for writing this post. Going to follow your advice. I have some curiosity

When you say

> this provides "legalities" to protect yourself and the customers

1. How seriously these documents are taken by the laws? As I can see that the user can always say that they didn't find the document while using the website or on the opposite side website owner can say that they had those documents available on demand.

2. Are there any guidelines/regulations by any law that makes it mandatory to list these documents or was it just a standard that got created by website owners following a practice done by others

Oh. I wonder what is "one purpose of internet" that we all can agree upon

A. To be useful B. To be right C. Other

I use Google calendar, it doesn't have this feature.

Only closest possible workflow is this 1. Create a public calendar link in Google Calendar that shows your availability 2. Create an event with your preferred time and a description : "Feel free to change the time of the meeting. Here's my availability: {public calendar link}" 3. Invite the person you want, make sure they have permission to edit the event