This is why voyager had so many shuttles. Once they started beaming the poop into space instead of shuttles they could use their entire stock of poop shuttles as normal shuttles. Bit of an extravagance for the delta quadrant, really
I don’t disagree. My problem is not with their choice of monetizing sync. My problem is with their choice to package a web app for Android and desktop, provide that same web app for self hosting, but not allow you to store the data in the web app. In the discussions on GitHub they claim it’s just something they can’t tackle right now, or whatever. No. It’s functionality that was specifically stripped because that’s how every other self hosted web app works and the local storage framework they use is obviously bolted on and not well supported by browsers. In other words, they’re manufacturing problems to sell you a solution. And again, that’s their decision to make. It just doesn’t seem like they make good decisions, and we’re talking about an app you put a lot of work and data into.
I do too. My point is there’s already a web app you can self host, but you can’t store your data on your server. The web app uses the local file access framework, which is just dumb. There’s no reason for this except to be able to monetize sync, and that’s also dumb because as you said, sync thing works fine. But they’re making a bad choice to explicitly remove functionality, and that doesn’t make me feel confident about the future of the project.
Unless you need specific functionality that silver bullet doesn’t provide, i’d start there. It’s very similar to logseq, but doesn’t have a bunch of questionable design choices based around a paid sync monetization scheme. Silverbullet is self hosted and has a web app. Logseq is a webapp, packaged for Android and desktop, but only allowed file access for your data so you can’t self host sync… Because they charge for that. It’s a mess.
I’m glad you’re happy with Linux. Sometimes I find it hard to believe that things have progressed that far. I’m stuck with the feeling that gui settings and such aren’t reliable, because they didn’t used to be. Moreso, I just know how to do things in the terminal because that’s how I’ve done them for decades.
11x17 is incredibly common too. Usually it is oriented landscape and z folded to get a large diagram into a document. It’s kind of irritating that the most typical large format size is 24x36, which is a different aspect ratio than 11x17, for a variety of reasons. If you’re designing something you need to know what aspect ratio to design for. Most copiers can do 11x17, and if the standard large format size was 22x34 it would be exceedingly easy for most offices to produce good working copies of large documents. Best compromise I’ve seen is when people put a logo or header on the side that can be omitted when you switch aspect ratios.
If you’re already running a million docker containers then just get a vps somewhere to host your blog. Cheapest reliable one I found last I looked was vultr. I think mine is $15 a year.
I’ve not had a problem with nextclouds experimental selective sync. Have you tried clearing all your nextcloud dotfiles and setting it up from scratch?