Even on Windows, Proton drive is hot garbage. It never syncs my files correctly. Has a tendency to leave half encrypted uploads just lying around. Eating up desk space.

Don’t even get me started on how long it takes to upload anything. Got a 1 GB file? Good luck!

And that’s before getting into the fact that it’s proton’s third product. It was announced in 2019. 5 years and they still don’t have proton drive as a working product.

Another gripe I have is that the Linux VPN client still doesn’t support wireguard. Sure, you can download wireguard configuration files. And they work just fine. But changing servers is a pain in the ass because of it.

It’s made me seriously consider dropping my visionary plan and moving to a more competent provider.

That being said, proton mail has been fantastic. And I have a ton of domains on it. So it would be a pain to move. I guess I’m just in a stalemate.

I mean sure maybe 10 years ago. But most static sites like blogs and such can fit entirely on a cloudflare page worker under the free tier. Or heck, even the free allotment on AWS S3 or other object storage providers.

I mean, perhaps this isn’t a static site and it’s built on some sort of CMS and has a postgres database in the background. In that case it probably runs around $5 to $10 a month.

Of course, this all presumes that the person setting this up is fairly savvy about the offerings available. I see a lot of people making silly decisions in this space, thinking that they need some full fat virtual private server, when all they really need is an object storage bucket behind a DNS c-name.

I guess I didn’t really see the pressure that they were under.

I hope they heal! But it’s a bummer that such an excellent resource will be taken down.

I wish more creators were willing to hand their creations to someone who wishes to continue it. But oftentimes, I fear that it’s far too entwined with a person’s identity for that to be common occurrence.

I’m also on a 7Pro with no issues with WPA3, when it comes to stuff like this, and you’re running a Telco/Cable provided access point, my blame would start there as those things are never the way they’re supposed to be, they run screwed with firmware that you can’t control the updates on and never know if they’re doing everything the way their supposed to or not.

Wha? Where did I say I was using the ISP provided modem? Oh, no-no. I buy all my equipment outright and my AP is the current top-of-the-line Netgear Docis3.1 modem/router combo.

I’ve double checked this issue as well. As soon as I enable WPA-3 my pixel just refuses to connect, but no other device in my entire home does. Pretty sure it’s the Pixel somehow.

No kidding, my Pixel graveyard is too damn big… I wish other phones had nearly the AI/Assistant features that Pixels had because I definitely don’t want to switch to the Apple ecosystem and found the OnePlus experience flawed, while the Samsung experience feels bloated.

I’d go with a Fairphone, but for some reason it’s impossible to get “officially” here in the U.S.

I’m on the Verizon variant of the software - so same version but with an .A1 tacked on.

Edit: Oh, also, Pixel 7 Pro here.

Also appears to break Wi-Fi.

Does the violence of Doxxing accomplish that? I see no evidence that Doxing has done anything but embolden them. For me, if I look at the actual impact of these sorts of things, it doesn’t seem that Doxxing is effective at actually fighting back, and is, in fact, making things more dangerous for folks like you and me, not less. Sure we get that rush of dopamine when “Karen the Racist” is fired for her own stunts when revealed to the company, but we don’t check back in within 6 months to see that these people have largely recovered.

Retribution only begets more retribution. Personally, I’m more for restorative justice - even for those we find reprehensible.

Heck if the purpose is to “defend ourselves”, going the route of retribution seems counter to that goal.

As for social costs - they already exist. I wouldn’t be a friend with a proud neo-nazi, nor would most people. But this level of Doxxing is amplifying that social cost to unproductive levels - and I fear it serves as nothing more than a leftist/liberal virtue signalling performance.

If a drug dealer should receive compassion because of the systemic inequities that led him to “offend” - thus deserving restorative justice, why are closet Nazi’s that much different? We already know that retributive justice doesn’t work, and many of us would rather see it dismantled. Is every Nazi unfixable? I think the only people that can really answer this question are Germans. (And if anyone from Germany is here now, I’d love to hear your view on this - if it worked, what didn’t work, etc)

I never claimed the article to do that. I claimed that despite the article not doxing anybody that the comments in the thread were.

And It was just one of many issues with the thread. It was very much. Also a hostile and toxic place to be. It stood head and shoulders over other similarly distasteful posts which is why I had issue with it.

As on Reddit, no one really cares about the not so popular posts. But this post was top of the all feed drawing in more distasteful discourse.

My position is that doxing is a form of violence. Violence in this definition is anything that restricts your choices. (Source: Philosophy Tube). Thus doxxing is violence since it forces one to move, react, or retaliate in response to the leaked information.

It is never acceptable to me - full stop.

The only entity with “Doxxing” permissions are government agencies with robust oversight such that this violence is only used when it’s the lesser evil over not.

It seems that more and more people feel justified in their doxing. And that’s what scares me. More more people feeling justified to perform a form of violence.

Because that’s what doxing is, a form of non-physical violence.

I dunno, my OLED panel has some notable image retention issues - and a screensaver does appear to help in that regard.

Eh, I went back to screen savers due to my use of OLED panels. Better than a static lock-screen image for sure.

This article is ancient. We have more recent elections to go off of.

And according to basically everything I can find, “Moms For Liberty” and related groups suffered major losses basically everywhere the last cycle.

I’m not at all suggesting to not worry, after all, it’s worry that got us to ensure they didn’t win. But I am suggesting that your information is very out of date and that you should do a better job of finding recent points to support your claim.

Also, I think this is off topic for this community and seems far more like political bait as some have pointed out.

“Your application” - the customers you mean. Our DB definitely does it’s own rate limiting and it emits rate limit warnings and errors as well. I didn’t say we advertised infinite IOPs that would be silly. We are totally aware of the scaling factors there and to date IOPs based scaling is rarely a Sev1 because of it. (Oh no p99 breached 8ms. Time to talk to Mr customer about scaling up soon)

The problem is that the resulting cluster is so performant that you could load in 100x the amount of data and not notice until the disk fills up. And since these are NVME drives on cloud infrastructure, they are $$$.

So usually what happens is that the customer fills up the disk arrays so fast that we can’t scale the volumes/cluster fast enough to avoid stop-writes let alone get feedback from the customer in time. And now that’s like the primary reason to get paged these days.

We generally catch gradual disk space increases from normal customer app usage. Those give us hours to respond and our alerts are well tuned. It’s the “Mr. Customer launched a new app and didn’t tell us, and now they’ve filled up the disks in 1 hour flat.” that I’m complaining about.

It is definitely an under provisioning problem. But that under provisioning problem is caused by the customers usually being very very stingy about what they are willing to spend. Also, to be clear, it isn’t buckling. It is doing exactly The thing it was designed to do. Which is to stop writes to the DB since there is no disk space left. And before this time, it’s constantly throwing warnings to the end user. Usually these customers tend to ignore those errors until they reach this stop writes state.

In fact, we just had to give an RCA to the c-suite detailing why we had not scaled a customer when we should have, but we have a paper trail of them refusing the pricing and refusing to engage.

We get the same errors, and we usually reach out via email to each of these customers to help project where their data is going and scale appropriately. More frequently though, they are adding data at such a fast clip that them not responding for 2 hours would lead them directly into the stop writes status.

This has led us to guessing what our customers are going to end up at. Oftentimes being completely wrong and eating to scale multiple times.

Workload spikes are the entire reason why our database technology exists. That’s the main thing we market ourselves as being able to handle (provided you gave the DB enough disk and the workload isn’t sustained for a long enough to fill the discs.)

There is definitely an automation problem. Unfortunately, this particular line of our managed services will not be able to be automated. We work with special customers, with special requirements, usually fortune 100 companies that have extensive change control processes. Custom security implementations. And sometimes even no access to their environment unless they flip a switch.

To me it just seems to all go back to management/c-suite trying to sell a fantasy version of our product and setting us up for failure.

That is exactly what we do. The problem is that as a managed service offering. It is on us to scale in response to these alerts.

I think people are misunderstanding my original post. When I say that customer cluster will go into stop writes, that does not mean it is not functional. It is an entirely intended function of the database so that no important data is lost or overwritten.

The problem is more organizational. It’s that we have a 5 minute SLA to respond to these types of events and that they can happen at any random customer impulse.

I don’t have a problem with customers that can correctly project their load and let us know in advance. Those are my favorite customers. But they’re not most of our customers.

As for automation. As I had exhaustedly detailed in another response, we do have another product that does this a lot better. And it’s the one that we are mass marketing a lot more. The one where I’m feeling all the pain is actually our enterprise level managed service offering. Which goes to customers that have “special requirements” and usually mean that they will never get as robust automation as the other product line.

Our database is actually pretty graceful. It just goes into stop writes status. You can still read any data and resolving the situation is as easy as scaling the cluster or removing old records. By no means is the database down or inoperable.

Essentially our database is working as designed. If we rate limited it further then we have less of a product to sell. The main feature we sell of our database technology is its IOPS and resiliency.

Further, this is just for a specific customer, it has no impact to any other customers or any sort of central orchestration. Generally speaking the stop writes status only ever impacts a single customer and their associated applications.

Also, customers can be very stingy with the clusters they are willing to buy. We actually are on poor terms of the couple of our customers who just refuse to scale and just expect us to magic their cluster into accepting more data than its sized for.

Probably not feasible in our case. We sell our DB tech based on the sheer IOPS it’s capable of. It already alerts the user if the write-cache is full or the replication cache is backing up too.

The problem is, at full tilt, a 9 node cluster can take on over 1GB/s in new data. This is fine if the customer is writing over old records and doesn’t require any new space. It’s just that it’s more common that Mr. customer added a new microservice and didn’t think through how much data it requires. Thus causing rapid increase in DB disk space or IOPs that the cluster wasn’t sized for.

We do have another product line in the works (we call it DBaaS) and that can autoscale because it’s based on clearly defined service levels and cluster specifications. I don’t think that product will have this problem.

It’s just these super mega special (read: big, important, fortune 100) companies have requirements that mean they need something more hand-crafted. Otherwise we’d have automated the toil by now.

As somebody with autism. I find this take lacking nuance. You see for me these tools represent a huge leap and accessibility for me. I can turn a wall of stream of consciousness text into something digestible and represents myself.

I find myself constantly exhausted with the societal expectation that I review, edit, and adjust my own speech constantly. And these tools go a long way to helping me actually communicate.

I mean, after all nothing changes for me. People thought of me as a robot before. And I guess they can continue to think I’m still a robot. I’ve stopped giving a crap about neurotypical expectations.

I mean I take a less extreme take. But I definitely resonate. As somebody with autism, it’s really nice to have an impartial chat assistant to turn my stream of consciousness wall of text into something far more digestible. Trying to do so myself often takes hours to construct a message a couple paragraphs long. Where I checked and double check and triple check for anything that might offend somebody or come across strange or not flow well. Etc etc etc.

A lot of these articles don’t really investigate the accessibility aspect of these tools. And I really wish they did. I know if one of my friends used chatgpt to help with their messages, I would be completely fine with it.