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.

We use a timed feeder for our cat’s breakfast. I don’t force DST on her lol.

deleted by creator

deleted by creator

I’m not really a webdev, more backend or full stack at this point. I do know about C & C++ strong presence in firmware, OS, HPC, video gaming, and elsewhere.

But by the numbers there’s a lot more webdevs than any other kind out there, and that doesn’t even touch on NodeJS leaking into backend and elsewhere.

I really wonder about their methodology. JavaScript/Typescript is nearly ubiquitous in webdev, and has been making strides in the backend space for almost a decade now. No matter how you feel about it (yeah it’s terrible, I’ve been press-ganged into it this year) it’s a real force in the marketplace.

It’s super surprising to me it’s still behind C and C++.

Pretty much.

Linkwarden and Wallabag are both excellent. Omnivore is up and coming, but might still be difficult to selfhost.

They haven’t updated the Champion yet, I think it’s scheduled this quarter? But with Alignment gone they indicated they’d make the “subclass” system diety based, as it should be.

No, you specifically need a diety in the original and in the rework.

Specifically, in the rework all alignments have been removed, therefore the alignment requirements for the champion subclasses, and the champion subclasses themselves have been removed.

Instead, in the rework you select a diety, you must then adhere to that diety’s edicts and anathemas, and then you are granted specific powers from the diety according to that diety’s domains.

Deity and Cause: Champions are divine servants of a deity. Choose a deity to follow; your alignment must be one allowed for followers of your deity. Actions fundamentally opposed to your deity’s ideals or alignment are anathema to your faith. A few examples of acts that would be considered anathema appear in each deity’s entry. You and your GM determine whether other acts are anathema. You have one of the following causes. Your cause must match your alignment exactly. Your cause determines your champion’s reaction, grants you a devotion spell, and defines part of your champion’s code.

source

PF2e Remaster paladins paladin subclass champions champions

See if it’s supported by Lineage OS.

I will confess that most of my knowledge comes from hiking/backpacking, so arm length isn’t often a large concern.

Often mentioned in the same breath as the Torrentshell but generally more adjustable (and by some measures, higher quality):

• Outdoor Research Aspire II
• Outdoor Research Helium
• Outdoor Research Foray II
• Enlightened Equipment Visp
• REI Flash Stretch

We know they hearded them off cliffs in many parts of the world, probably egged on by throwing spears and jabs.

It seems pretty unlikely they’d have regularly risked death by planting a spear and waiting for a charge. It’s not like a multiple ton animal is going to be stopped by the spear.

I guess it depends on scale.

• FSearch

• Recoll

• TypeSense

Jupiter probably also threw an icy giant out of the inner solar system when it was making the family unstable. What a good big bro to have.

Or else.

+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?