Linkwarden and Wallabag are both excellent. Omnivore is up and coming, but might still be difficult to selfhost.
Linkwarden and Wallabag are both excellent. Omnivore is up and coming, but might still be difficult to selfhost.
I stand with my (forever) baby hippo Fiona.
I guess it depends on scale.
FSearch
Recoll
TypeSense
What, no LaTeX?!
+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.
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.
And “cake” is officially “hamburger”
FWIW, Lance buys the machines himself using his patron funds and doesn’t let manufacturers into his process. Most don’t even know they’re being reviewed unless he has issues or specific questions he can’t get the answers to elsewhere. He’s frankly more qualified to test and compare such features than nearly anyone else, since he has thousands of hours of stick time with hundreds of machines at this point.
To get back to the bulk of your question, in many other industries where water heating is done, there’s cheap thermoblocks and good thermoblocks.
Double boilers have been around long enough that improvements today are incremental at best. Heat Exchangers and Thermoblocks on the other hand seem to be improving by leaps and bounds still, and Thermoblocks in particular are getting a lot of development in other industries.
It looks like Ascaso is using decent blocks and is properly PID controlling them. Obviously it’s not going to be as stable as say a full brass double boiler, but the results seem to outperform most heat exchangers.
Value is tricky though. You’re right, it’s a crowded market at that price. Personally at this moment, given this review at face value I’d still go with a Silvia Pro X today. But I expect in a few more years heat blocks might be able to match performance with dual boilers for cheaper and with less work.
That is weird. Thank you for bringing that distinction to my attention, I’d always assumed it was FOSS and just locked a few features behind a paywall on Google Play.
Looks like the mobile version is created by the same person who initially created Stellarium (and the current project coordinator for the FOSS version), but forked and taken closed source? Very confusing.
What do you mean? I use it frequently.
I can recommend Grandstream. They have a great UI, tons of features explained in plain English, and powerful Access Points for a fair price. Zero cloud features necessary. Also a US based company, if that matters to you.
But even cooler, the controller is built into the Access Point and is peer-to-peer if multiple APs are in use.
I switched a month ago from a full Unifi network and couldn’t be happier. Do note that they need PoE injectors to power the APs, but unlike Ubiquiti’s they don’t ship with them.
I’ll say that it can lead to uneven extrusion and even skipped steps on your extruder. How much, and how much that amount matters is entirely dependant on the setup and your workflow.
There are a few 3D printed solutions to keep filament tension neutral using a buffer system. It’s not a bad idea to check out some of them.