![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Emacs really can do anything huh
Emacs really can do anything huh
I’ve been propagandizing since grade school
Strangely enough, Lizard predates Rock significantly but took a long time to be considered competitively fair - around the time Spock was invented.
You can’t leave purgatory at will
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 [email protected] all goes to the user1 mailbox (and [email protected] 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.
You might just be asymptomatic or immune. Congrats!
I know you’re joking, but I just had the realization that S and J are probably the keys you’re likely to hit when alternating two thumbs on a mobile keyboard
Make sure to attend the pre raid Google meet so we can discuss specifics
I think that’s what they were saying. For those, it is likely indeed malice. For friends and family, it’s likely just stupidity or ignorance.
To some it comes easy. To others, the ways of the heart are an enigma.
“What’s YOUR deal?” sounds pretty aggressive, “what’s your DEAL?” sounds borderline inflammatory, but I think there’s a very neutral delivery without particular stress that sounds more like an open ended question than an aggression. Still, probably not great around fully sober folks.
…
Well now I gotta!
I know someone with a fat one they use for smoothies and shakes.
There’s many services out there like that that will charge you for basically the hardware and bandwidth (i.e. a VPS) but will give you an easy interface to host applications - even federated ones. The problem really is how do you compete with free? It’s “free” to watch and free to upload on YouTube. And all your favourite creators are probably already there because of the network effect YouTube has built over the years. And it’s a great place to discover new ones, too, even ones that have been around longer than you’ve been alive (for some folks, anyway).
From a technical perspective, though, this is pretty feasible. With huge upfront costs. If you rent hardware from existing providers like AWS/DigitalOcean/etc. you’re gonna pay out the ass for it. It doesn’t seem expensive to people who just need a little hardware but we’re talking about video here. You have to store multiple versions of a single video - that’s a ton of hard drive space. You have to encode what is uploaded by the users into a workable format - that’s a ton of compute. So if you were gonna provide it to hobbyists at a reasonable price you’d want to open your own data center (yes people still do that) which will give you some, relatively speaking, very very cheap storage, compute, bandwidth. The only issue is it costs a ton upfront and you need someone to maintain it if you don’t know how.
Nebula could be a good case study in how well this would work. The content on there is of exceptional quality. To be honest, though, that’s not always what I’m looking for. Sometimes I just want a bunch of garbage rather than a little high quality content. The big social media platforms put a bunch of it in one place. I know it’s not really a good thing, but sometimes I just need background noise while I do other shit and random YouTube videos really does it for me.
I can’t seem to find any data on how much of Nebula’s revenue is actually due to the Curiosity stream tie-in, but I know even I was wary of the $5/mo subscription without the CuriosityStream sub to sweeten the deal. So maybe even the world’s largest creator-owned streaming platform needed that investment.
Yeah, I’m usually already undressed.
Should’ve followed it with jk 1/2, that would’ve cleared things up entirely
Do you mean upholstered furniture? What’s the norm for furniture where you live?
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.