fastify-auth VS notion-auto-pull

100% compatibility with already built fastify plugin, so things like authentication can be done in an already good way, like with fastify-auth

Fastify as its core is okay. Not great, but OK. But plugins (official ones) made me struggle. For example, I couldn't figure out how to get fastify-auth plugin to work. It seems like plugins, even official, do not keep the same standards across whole ecosystem. It would be nice if all would have TS examples.

So the example is here I copied it as is, just adapting routes. Now to my understanding, I need either sessions or cookies so that when the user hits only one time ` http://127.0.0.1:3000/auth-multiple` all sequential calls to any secured api would verify the token.

For example, Fastify allows us to write better and cleaner asynchronous code by parsing JSON requests. With Fastify plugins, you don’t have to install multiple npm packages from different authors to perform common tasks like authentication and validation.

My perfection had a name: Notion.

I manage my non-work and work-adjacent tasks in Notion. Whenever I have an idea, regardless of how big or small or silly or achievable it is, I'll add it to Notion, and use labels to categorise it by type of output (e.g. blog, silly project, website update). Today I wanted to write a short post for my site. I clicked on the filtered blog post view, and selected this one (because I hoped it would be a quick one!).

Notion.so redefines workspaces. With its intelligent organization and collaboration features, it's more than a productivity tool—it's a digital haven. Discover the art of streamlined and efficient teamwork.

A quote as I could not directly send a discord screenshot and am not sure that people want to make an account at notion.so simply to see the FAQ:

I work on a large SPA: https://notion.so

It’s a document editing application. A document title might occur in the browser’s titlebar, in the header of the main editor, in a “mention” (a link to the document), and in multiple places in the user’s sidebar - like in both their “Favorites” section and in the the contents of their team.

When the user edits the document title, we need to update all those UI bits to render the new title. I have a hard time imagining some imperative code that iterates over all the possible views that may render a title to mutate them.

Notion (Notion.so) is an all-in-one workspace where you can write, plan, collaborate and get organized - it allows you to take notes, add tasks, manage projects & more. Imagine a lego structure. Notion provides the building blocks and you can create your own layouts and toolkit to get work done.

I think Notion (notion.so) is a good tool for managing Captain's Log games (and RPG games in general) but there is a bit of a learning curve. If there is interest, I would consider writing a more detailed tutorial on how to use Notion for Captains Log (as I figure the game out). I'd also recommend Thomas Frank's website and youtube channel for tutorials on how to use Notion.

my personal thoughts: regardless of how many people prefer not to believe it, and the fact that some startups do use non-dotcom (Notion owns notion.com by the way, but still redirects to notion.so - i suspect it's because it's too much of a hassle to do so rather than .so being their preferred TLD), the truth is that the .com still has a certain brand allure to it to mainstream consumers. personally i paid 10k for my startup's .com even though the other TLDs were cheap as hell (which i also bought anyway). i thought it was crazy expensive, but i still felt it was money well spent for the branding.