And the voices. “Billy…”
“You fucked the whole thing up.”
“Billy, your time is up.”
“Your time… is up.”
I think 8 hours starts to get into territory where they might get an informational message about the delay? That also starts to be long enough that the emails might get lost in the distant past in the client and never be seen, by the time they arrive.
I think when I used to do this, it was one advisory message every 24 hours that a message was holding in the queue, and after 5 days it would bounce, but I have to assume that those limits have shrunk in the modern day. How much, IDK; it might be worth experimenting with it though before committing to creating that situation since it might not go okay.
SMTP is designed with queues and retries
Unless something has changed massively since I was deeply involved with this stuff, the people that sent you email may get a notification after some hours that their message is being delayed, and maybe after like 24-48 hours they might get a bounce. But if it’s just your SMTP server going down for an hour or two every now and then, the system should be able handle that seamlessly (barring some hiccups like messages showing up with timestamps hours in the past which sometimes is confusing).
You’re the only one talking sense and you are sitting here with your 2 upvotes
The AI company business model is 100% unsustainable. It’s hard to say when they will get sick of hemorrhaging money by giving away this stuff more or less for free, but it might be soon. That’s totally separate from any legal issues that might come up. If you care about this stuff, learning about doing it locally and having a self hosted solution in place might not be a bad idea.
But upgrading anything aside from your GPU+VRAM is a pure and unfettered waste of money in that endeavor.
You’re going to think I am joking but I am not. Multiple people have sworn to me that this works for a common failure mode of HDD drives and I’ve literally never heard someone say they tried it and it failed. I’ve never tried it. Buyer beware. Don’t blame me if you fuck up your drive / your computer it’s connected to / anything else even worse by doing this:
Ask GPT to rewrite your configuration, check over it with diff to make sure it didn’t do something dumb, bingo bango
Tor’s obfs4 protocol is pretty difficult to block, and it has some other transports that are options if obfs4 is unusable in a heavy censorship regime. This page is a good overview of how to start; with the right transport and bridge setup it’ll be extremely difficult for your ISP to prevent you having access.
You could make your home server a securely-accessed onion site and connect to a remote-access-via-web service you’re running there. That part might be a little challenging (and this process overall may be overkill) but it’d be very challenging for them to block it, I think, so if you’ve tried some things and had no luck, that might be the way to do it.
Be careful obviously
Honestly having GPT write one-off code for you for particular selected pieces (esp ones that require a lot of domain knowledge) works pretty well in my experience
Does it work out okay with 12 cores purely on CPU? About how fast is the interaction?
I played around a little with Ollama and gpt4all but it seemed to me like it wasn’t fast enough to be useful on pure CPU, but if I could just throw cores at it then I might revisit the issue.
Sewer lines need to be vented in order not to create a pressure differential that causes problems. There are a couple different approaches, but that shit isn’t one of them; it kind of looks like something a plumber just threw in there to solve their immediate problem and then scooted away from free of consequence.
I wouldn’t recommend plugging it, as you might be taking away a needed vent from the whole system… the two options I could see would be:
deleted by creator
deleted by creator
Also, export your DBs first, and snapshot the export instead of the raw DB files