Sounds like my usual load. Flamethrower, shield pack, then OPS and 500kg depending on planet conditions.

If there is orbital scatter then I’ll leave the OPS and take something else.

I take both!

They watch the swarm. You can view connections of the swarm. They see your ISP owned IP and send an email.

Debian

I prefer restic for my backups. There’s nothing inherently wrong with just making a copy if that is sufficient for you though. Restic will create small point in time snapshots as compared to just a file copy so I’m the event that perhaps you made a mistake and accidentally deleted something from the “live” copy and managed to propagate that to your backup it is a nonissue as you could simply restore from a previous snapshot.

These snapshots can also be compressed and deduplicated making them extremely space efficient.

Assuming the implementation is done in such a way that I am not indirectly owned by the manufacturer of the BCI and am capable of maintaining its software and firmware myself…yes yes absolutely yes stick that shit in my head.

But if it is not open source and I’m expected to be tied to some corporate entity just to utililze it, no, absolutely not.

There are 0 solutions in a reverse proxy if it is not capable of absorbing the amount of traffic required to maintain service while under a ddos attack. How exactly does a reverse proxy do anything to protect from a ddos?

Edit: I see perhaps I misinterpreted this. Sure, there are other ddos protection services but if you are under attack RIGHT NOW and your critical services are down are you going to shop around for alternatives that aren’t Cloudflare or are you just going to go straight to the thing you know will do exactly what you need with a proven track record of doing it?

Going to CF is entirely understandable and they said that once the dust settles they will be looking at alternatives for the future that is not CF.

I’m far from a CF shill. I believe they do more longer term harm than their short term “good” has done. From an ops perspective though this action was very reasonable.

A “basic reverse proxy” does nothing to help against a large ddos. The only real thing you can do is absorb the traffic and this is not feasible for most operators to host themselves.

Trust no one. Not fully at least.

Copy them to your PC first them to the new phone.

Yeah thats mostly the one that keeps me going.

Just look at the bit rate of what you are streaming and multiply it by 3 then add a little extra for overhead.

Ah, I was wondering why I couldn’t get it to detect my yubikey. I saw keepassxc-full in the repo but that also didn’t seem to work. I’ll have to revisit it.

I mean I’m not sitting here defending soldered on ram but your unnecessary aggression and sarcasm in your previous responses overshadows the fact that while solder on ram sucks for the upgrade and repair market the underlying tech has very tangible improvements and now we can maintain that improvement and the upgrade and repair functions.

I agree, soldered ram is bad. But I disagree that LPDDR ram is fundamentally bad and this improvement allowing it to be modular while maintaining its improvements is a very good thing.

As far as your complaints of battery life on your thinpad goes, there is much more to battery life than the consumption of the memory but naturally every part plays a role and small improvements in multiple places result in a larger net improvement. I’m assuming you’re running linux which in my experience has always suffered from less than optimal power usage. I’m far from an expert in that particular area but its always been my understanding that it is largely caused by insufficient fireware support.

As a whole this looking at this article in a vacuum i only see good things. A major flaw with lpddr has been address and i will be able to expect these improvements in future systems.

So you believe that the performance improvement and power saving is not worth creating a new standard?

But the article explains that there is a technical reason.

What exactly do you mean by “not mountable”?

Just an FYI to you and anyone else who might read this but you don’t even have to link a PSN account for cross play. I have no PSN account and cross play works just fine.

The primary reason a private track is private is to make it feasible to maintain a curated community. Many users are not good torrent citizens. Many users are not good netizens in the first place. More than a few will look to actively do harm. Keeping a mostly closed community allows the vetting of users and those who end up breaking the rules are dealt with swiftly.

The extra barrier of entry also helps prevent bad actors from operating on the site. This is of course not a full proof thing but it is obviously much better than a public site.

Additionally running a private tracker and site takes server resources that are not free. Limiting the total number of users is a way of maintaining uptime by staying within your operational limits.

I’m sure there are other benefits for private trackers but these are at least a few.

I am not going to explain why someone on the internet was mean to you. Given the tone of this post I wouldn’t be surprised if it was deserved.

Are you asking about why private trackers are private or are you asking about why a handful of people were mean to you who also happened to use a private tracker?

Edit: typo