Max, what’s wrong? You’ve hardly touched your jar.
Max, what’s wrong? You’ve hardly touched your jar.
Real talk though: why would he ever rule out future possibilities?
I guess it depends on scale.
FSearch
Recoll
TypeSense
Yeah, and to exploit it you need ring0 access in the kernel.
In other words, this isn’t an attack vector, it’s an escalation path. It escalates past the kernel, which is terrible to be sure, but if a hacker manages to get that deep in the first place, your system is already fucked.
+1 for Gitlab. As the number of developers increases the features of Gitlab will get more and more important. Only OP can say, but if they’re closer to 9 developers than 2, I think it’s a safe bet they’ll need the extra features sooner rather than later.
The Epic exclusive bullshit always stinks. Glad they are at least offering an option to get it from their website, even though the best solution is to release it everywhere.
Its dangerous to send goalposts flying around that fast, be careful or you’ll hurt yourself.
Your response is condescending, arguing from ignorance, and arguing in bad faith. I will reply this time, because once again you’re trying to build an argument on extremely shaky ground and I don’t enjoy people spreading ignorance unchallenged. However I won’t engage any further and feed whatever you think you’re getting from this.
I haven’t suggested that people should use Obsidian over OSS solutions. I was simply pointing out your argument against Obsidian’s architecture was poorly founded.
The data you’re insinuating will be lost is pure FUD. While the format isn’t standard markdown, none of the well implemented solutions are, because as you so rightly pointed out, markdown has little to no support for most of these features.
However, obsidian’s format is well documented and well understood. There are dozens of FOSS plugins and tools for converting or directly importing obsidian data to nearly every other solution. Due to obsidian’s popularity, it’s interoperability this way is often far superior to FOSS solutions’.
Content is your notes. In obsidian this is represented by markdown files in a flat filesystem. This format is already cross platform and doesn’t need to be exported.
Metadata is extracted information from your notes that makes processing the data more efficient. Tags, links, timestamp, keywords, titles, filenames, etc are metadata, stored in the metadata database. When you search for something in obsidian, or view the graph, or list files in a tag etc obsidian only opens the metadata database to process the request. It only opens the file for read/write.
Does this help?
Tell me, are you aware of the distinction between content and metadata?
Also, what do you mean, no official export? The data is already sitting on your filesystem in markdown…?
This isn’t really the case though. Obsidian uses a database for metadata, and therefore can extremely rapidly display, search, and find the correct file to open. It generally only opens a handful of files at a time.
I’ve used obsidian notes repos with hundreds of thousands of notes with no discernable performance impact. Something LogSeq certainly couldn’t do.
The complaint in the post you’ve linked is a) anecdotal and b) about the import process itself getting slow, which makes sense as obsidian is extracting the metadata.
I’ll always champion OSS software over proprietary, but claiming this is a huge failing of the obsidian design is just completely false. A metadata database fronting a flat filesystem architecture is very robust.
Edit: adding link to benchmark. https://www.goedel.io/p/interlude-obsidian-vs-100000
KobaldCPP or LocalAI will probably be the easiest way out of the box that has both image generation and LLMs.
I personally use vllm and HuggingChat, mostly because of vllm’s efficiency and speed increase.
Find a farmers market or an Asian food market.
Nah, frivolous and infamous are wholly appropriate for a message board, I’m not writing a fucking encyclopedia article.
Every team does file complaints, but I feel like Horner and Toto are sort of infamous for frivolous accusations that make the other team tear their vehicles apart for inspection hoping they find something or don’t and just forget a bolt somewhere.
Point is, it should be a rule for everyone. If you make an accusation and it turns into nothing, we take a point off the constructors, or something to that effect. Penalize the principal without overly penalizing the driver’s for the principal’s soap opera antics.
Standard Horner BS. If someone is actually competing: complain about everything and try to get them penalized.
Eventually F1 is going to have to implement penalties for frivolous investigations, like flopping penalties in other sports.
This should go without saying, but benchmarking to test the raw performance of an engineering sample is a fools errand. Generally engineering samples are carefully selected for stability and testing features, not for their performance or efficiency.
Aaah for Fook’s sake Gene! That’s Andretti’s spot!
Sure, but he is the product of a team owner’s genitals, so really they just need to let him get back to playing in his sandbox with his million dollar toy.
I was looking into this recently, but didn’t have any first hand information.
https://ardupilot.org/ardupilot/docs/common-rtf.html#common-rtf
Ah yes, Alonso, famously good role model who tried to blackmail his employer to gain the upper hand over his co-worker.
He can fuck right off.