0xSim

The boy scout technique: fix your types when you’re working on a bug or a feature, one file at a time. Also try to use unknown instead of any for more sensitive parts, it will force you to typecheck.

It is opt-in though? The site can’t track you until you agree with its cookies policy

The EU did its job correctly by forcing sites to ask for consent. How that rule is implemented is up to the sites, and they often choose to do it in the most annoying possible way. And then tell you to blame the EU for it.

Also as a website owner, you only need to ask for consent when you use more than “strictly necessary” cookies (https://gdpr.eu/cookies/), i.e. cookies that are needed for your site to function normally.

I see Lemmy is already at the “X is bad, updoots on the left” stage

“Can we focus on Rampart, please”

I’m pretty vanilla with my plugins:

• Omnisearch - disclaimer, I’m the main dev
• ReadItLater - a scraper to quickly save articles that I reference in my own notes
• Excalidraw
• Linter - mainly to automatically format my notes with a createdAt metadata and an h1 title
• Dataview - I don’t use it extensively but I have a few js snippets to query external APIs like Github or Mastodon

I try to avoid plugins that stray from “standard” markdown, to not rely on Obsidian.

“deleting” only flags the comments as such in the database, but that still makes them unreadable. That means unreadable conversations and lost information for users.

Agree with this.

From the op:

“they’re for power users and regular users won’t understand them”

It’s right though. 90+% of users are fine with default settings, so it makes sense to hide them. Otherwise, at best it is confusing & intimidating, at worst a lot of users will have an awful UX because they tweak settings they don’t understand.