It’s a bit hacky but I suppose there’s always the option of using a separate WebDAV server on the directory where frappe drive stores its files. I haven’t tried something like that, though. Unfortunately I don’t know of any integration within frappe drive itself. Seems they’re accepting contributions now so it’s possible these will be implemented in the future. WebDAV is a bit of its own beast, though, so that’ll be a huge undertaking in my opinion.

And then their non standard file format turns out to just be a zip file or gzipped JSON data 😂

from a bussy

I assume that word also means something else than what I’m thinking…

But it’s good that viable alternatives exist in case Microsoft ever considers shutting down the Java edition.

I had never even considered that as a possibility but now it seems all too possible and I’m gonna have to sit with that for a while…

I’ve actually used this to my advantage. I bought some cheap speaker/light combos which basically made the lights dance to the music. The only power connector was a wire that comes straight out of the device and into an outlet. But it did have a USB port for loading music from a USB stick. So naturally I plugged one side of a USB A into the port and the other side into a power bank and it just straight up worked.

What’s a sane, dynamically typed language?

I prefer a hybrid approach. A document explaining some common things to do and generally the idea behind why the API is structured that way (shows me you actually thought about it, and makes it more logical to find different parts of it without necessarily looking it up), and then an API spec showing all the parameters.

Not to rub it in, but in my forties could be read as almost the entirety of the modern web was developed during my adulthood.

From the stories I’ve heard from corporate software employees, this does sound like exactly the kind of thing you gotta do to show some manager the guy is buddy-buddy with that they’re actually not doing their job. And even then they didn’t listen.

We have to work under the assumption that most development is done by inexperienced or, to put it bluntly, bad programmers. I would MUCH rather have bad JS code than bad assembly. One may crash a single tab in my browser, the other may crash my entire computer.

Assuming you put everything important in home, that is…

It’s the quickest way to prove to yourself that you know what you’re doing… Most of the time, anyway…

I’m imagining a scenario where you’re working on a feature that changes the DB state (e.x. introduces a new DB migration that changes some columns) and the bug is on an unrelated part of the code from your feature. In this hypothetical, going back to the state of the upstream branch would make your local environment non functional, and the bug is on an unrelated part of the code. Fairly specific scenario but hey, you can worktree for that. It’s not particularly thorough, though.

I personally go for “wizzywig” but to each their own.

Emacs really can do anything huh

I guess it’s cause they’re on a cruise ship

I use windirstat almost monthly and have never heard of WizTree. Keeping this in mind for next time I use it.

Though at this point, maybe I should just commit honestly

This is the approach I use, not sure if it’ll work for your use case but I can assure you it works for at least a few users. It’s all sort of manual set up but from your comments it sounds like you’re just doing this for friends and family and not on an enterprise level. I admire your efforts!

First off, I have a purelymail account on which I set up domains and accounts for each user. I have mine set up so user1@anydomain.com all goes to the user1 mailbox (and user2@anydomain.com goes to the user2 inbox regardless of domain, etc.) but you can set up some pretty complex routing if you want - and if you know a bit of sieve there’s even that. Purelymail handles the actual email sending/receiving so I’m putting a lot of trust in them, but it seems like they have a good track record and I don’t think I could do better on my own. Plus they’re dirt cheap. My big concern with email is always deliverability. Anyway, you’ll see this is all set up in such a way that I’m using purelymail now, but I’m not tied down to them.

Second, I use this image (linking to the repo and not the docker hub version so you can inspect the Docker file for opsec reasons. In my set up I build it from source because I have a couple modifications) which is a dovecot IMAP server + getmail. This is python getmail not go-getmail and not fetchmail. The repo itself has some pretty straightforward instructions but the way it works is basically that users inside the docker container each map to a mail directory. So each user’s credentials is actually a Linux username and password within the container. I have mine set up so it’s like user1, user2, etc. (which confused my users initially because automatic set up forms are never set up this way) but you could set it up however you need. Then, there’s a Cron set up to run getmail which you have to configure yourself within a cron.d folder that you mount on the container. For mine I have it configured to use POP3 so that when it gets stuff off purelymail it’s automatically deleted.

Finally, you just set up your mail clients to use this IMAP server and purelymail’s SMTP but if you know how to set up a forwarder you can always have it relay through purelymail. Purelymail even has the ability to relay emails to your SMTP server.

It’s probably only ever gonna be used by like, what, a hundred people at most at any given time?

Does that mean on a microkernel you’d essentially have double the amount of code execution for a driver (i.e. driver makes a call to the kernel, kernel verifies and then executes rather than the driver just executing the call) meaning double the latency? Seems like it would cause a lot of problems.