@filippo

Maybe, as a bank, you should not be using a random library taken from the internet, with a single maintainer and some 100 stars, and make it a critical dependency of your banking operations.

Maybe, as a bank, your IT should write and maintain such a library and open source it.

Maybe, as a bank, you should not continue to use the first library, and do the second thing after the first library was able to take down critical parts of your infra the first time.

Because we live in a society, and as a bank, you should be contributing to it, too.

But then, what do I know.

@julijane

@phpmacher @taseroth @haudrauf Ah yes, there is "Add new graph" which does the "MD mode".

@alxlg @taseroth @haudrauf @phpmacher OK, I just tested the latest build of Logseq in "DB mode" and there are no more md files at all. There is just a single db.sqlite file that contains all the markdown and the `assets` folder. The sqlite database stores everything in a single key value table which is somewhat cryptic. I can export the DB to a flat list of md files but it will loose some metadata it seems.

If it stays like this, it would make my markdown-first workflow impossible, it seems.

@alxlg @taseroth @haudrauf @phpmacher Just to make sure, I am not defending myself or demanding anything. I was just trying to figure out wether the future Logseq will support my preferred workflow. I guess I‘ll just have to try myself.

@taseroth @alxlg @haudrauf @phpmacher Yes DB-first, MD optional is still the way I understand it according. to https://discuss.logseq.com

Is that not the case?

I want alll my metadata to be stored in the markdown files and the DB should be fed by my markdown files. The DB should not generate or update markdown files or something.

@alxlg @haudrauf @phpmacher @taseroth This is all somewhat confusing. If I understand the gazillions of forum posts on this topic correct, self-hosted synching will not so easily be possible in „DB mode“ and the markdown files are no longer the actual source of truth. And now I understood your reply so that „MD mode“ is eventually going away.

I guess I just have to wait and see how it will work once it is released.

@alxlg Oh, that doesn't sound good. The reason I use Logseq was because the main "source of truth" are simple markdown files on my disk and everything else is just some nice extra value add.

So I guess I need to start looking for a markdown-first alternative. If such thing exists at all.

Man, this whole #Logseq DB transition is confusing.

So Logseq MD will continue to be supported on desktop and mobile and I can always decide whether I use DB or MD for new graphs, correct?

What features will not be available or not work as well when I choose an MD based graph? (e.g., sync and RTC)

What features will not be available or not work as well when I choose a DB based graph? (e.g., self hosting with sync)

https://discuss.logseq.com/t/logseq-db-unofficial-faq/32508/9?u=bitbonk

@logseq

@marijn I was told that the files-first-approach will not go away. You will be able to choose or something.

@heisedeveloper @bot boost this please

@b4ux1t3 #spacetimedb is cool tech

@fiseni I think this is new in C# 8. That version also introduced Default Interface Methods. I guess this is related to some sort of interop scenarios. It usually does not make much sense elsewhere.
If the interface is not designed for implementation by external user code, it is perfectly fine to make a member internal though. You can still implement it in your code where internals are visible.

Help JetBrains better understand how developers work in .NET development and shape the future of the tooling for this market.

https://surveys.jetbrains.com/s3/dotnet-development-survey-insiders

#JetBrainsRider #dotnet

@wkfry I wonder what crazy things people do with DI. We‘ve been using it successfully for ages, and honestly never had any serious problems.
Pro tip: stick with singleton lifetime almost always.

@ryanc
PascalCase
or
camelCase

(Can’t decide)

@patriksvensson The announcement post does have these credits.

https://devblogs.microsoft.com/dotnet/announcing-dotnet-run-app/?hide_banner=true#existing-ways-to-run-c#-without-projects

@simoncropp @maartenballiauw It would probably force a decision on whether to make the types internal and whether to make them conditional.

Hey, you #JavaScript folks want to build #secure web experiences? Well, join us on this #livestream where we talk about the best current practice of Backend For Frontend to keep your apps safe from token extraction attacks. Works for #react, #angular, #vuejs, #dotnet #blazor, and all web-based #frontend apps.

https://duendesoftware.com/webinars/tokenmanagement

🙏 Boosts are appreciated.

@maartenballiauw @simoncropp Thats the way we do it in all our projects that produce nupkgs for public consumption. We always keep the *internal* checkbox checked and the *conditional* checkbox unchecked.

@simoncropp I don’t think such a package exists, only the one with the binaries does, which I avoid to use. https://www.nuget.org/packages/JetBrains.Annotations

I can’t think of a technical reason why such a package should not exist, it probably would help keeping my copies of the annotation up to date in my projects.

I guess the package does not exist because Rider/R# is able to generate them which is more or less good enough. I think they haven’t changed the annotations for a long time.