Interesting site - I switched to librarything a while back

anyone know what kind of interface this is? I have an unreachable ssd that shows a power light but not any mount access console or ui

Think it's micro USB 3.0. Or most cables are also listed under Seagate/wd ssd

Possibly also called micro B

micro B!

that's it

lifesaver thank you

not usb but usbB for byob (buy your outdated bullshit)

When you get the update on VSCode but the announcement hasn't come out yet

just deconstruct the binary 😛

Ah, 739301 new 0s and 183749 new 1s!

progress!

I've seen people changing "FAANG" to "MANGA" due to Facebook becoming Meta 😆

https://www.internations.org/press/press-release/where-expats-should-not-move-in-2022-40279 @d1onys1us 👆

Oh wow that’s awesome! Thanks Kevin

mexico is ranked #1 🙂

Yeah I saw that, i was a bit surprised to see Japan so low. I usually see Japan ranked highly along with Singapore for very safe / nice to live in cities

yeah, i think its more to do with economy + covid

japan's work culture is also abysmally bad

I create a new workspace and also a new Github Repo.

Vault Convert

to remote with the new Repo Target copies the files but still gives me an

"Error: Command failed with exit code 129:...

at first glance it looks like adding as a remote vault works

Does anyone know if I can or how I would re-order the sidebar in dendron published site in a non alphabetical way

nav_order property

Holy moly you know what would be so cool

What if we were able to do “note references” as native to GitHub/GitLab README. I guess that’s possible within vs code, as long as we have dendron inside of the workspace we can do it. But then we’d have to open the preview and sometimes devs are already split screening.

I’m just thinking of how someone said “I should have put this ____” in the readme, in my head it’s should’ve put in dendron. But it would be nice to dedup here and have it work the same functionally (can easily see it in the vscode editor without preview, and can see it on github/gitlab readme. The former is more 80/20 imo and the latter i don’t even think can be done unless they extended their markdown flavor to support it )

I've had this problem in tech docs. I work with Sphinx for docs on Python projects, and because there is an

.. include::

directive (pretty much like note refs), you can choose to include the contents of the

README

file,

CONTRIBUTING

file,

LICENSE

file, etc. from the root of the repo within a note somewhere in

docs/*

files that ultimately get published to the site. This, among other things, led to me to opening this issue: https://github.com/dendronhq/dendron/issues/1565 At the moment, since Dendron supports the files inside of

notes/

, but not the notes inside of the root of a vault (community docs like

CONTRIBUTING

,

README

, etc.), they sort of sit separately when it comes to note ref inclusion support and lookup support. These may be considered as "non-note" files, in a sense, which could also be an extension of the discussion here: https://github.com/dendronhq/dendron/discussions/1975

I think the Dendron wiki kinda has the same problem at the moment, maybe other vaults, where users have to duplicate the content of the

README

file to something like the

notes/root.md

or other note to manually keep in sync

Random thoughts on documenting... - I love User Defined Markdown snippets (more so than Dendron schemas and templates) - I use 3-4 snips, multiple times a day to give my daily log some structure Examples: - Support ticket snips - Meeting snip - Context switch snip - Etc. - These are small (most f the time) chunks of structured documentation, mostly taking place in my daily journal, but some becoming stand-alone docs - They (and by proxy Dendron) are missing one killer feature... The ability to write them to a database! They end up in a daily journal somewhere OR in their own endless doc, but I want to query them, run analysis on them, etc. ESPECIALLY my Bug Report and Support Ticket snips. There is a LOT of valuable knowledge in there. #AppDocs, #DocsAsApps, #DatabaseMyDocs!