EncryptKeeper

joined 2 years ago
[–] EncryptKeeper 52 points 3 months ago

An ad giant already owns and controls my current TV’s OS

[–] EncryptKeeper 53 points 3 months ago (2 children)

Don’t forget easily manipulated

[–] EncryptKeeper 1 points 3 months ago

No it should carry over.

[–] EncryptKeeper 5 points 3 months ago

So as somebody who tried the game 24 hours after release, it worked for me just fine and it’s actually pretty good. Loving the career mode.

[–] EncryptKeeper 8 points 3 months ago

This isn’t even like a personal opinion or a thought experiment. Pirating was huge, then Netflix popularized streaming and pirating went WAY down, and then the streaming experience went to shit and pirating went back up.

[–] EncryptKeeper 14 points 3 months ago* (last edited 3 months ago) (2 children)

That’s my point. If any MMO is going to be tightly designed to utilize the abilities of a platform like AWS, you’d think it’d be the one owned by the company that owns AWS. At the very least because it’s an opportunity to flex the capabilities of AWS as an MMO back end. AGS is not AWS, but you’d assume there would be a team from AWS assigned to work with them specifically, as well as the fact that AGS doesn’t have to consider cost as a limiting factor when utilizing AWS as a back end, like any other MMO developer would. It’s a huge leg up they had over every other MMORPG developer, and still somehow managed to screw it up.

[–] EncryptKeeper 24 points 3 months ago* (last edited 3 months ago) (4 children)

The world’s 1st most popular cloud infrastructure company was also unable to deploy their own software on their own cloud infrastructure. I remember just being in total disbelief when New World, the Amazon-developed MMORPG struggled for WEEKS (Months?) with server capacity issues. Like… you guys own ALL the servers, the main selling point of which are their ability to dynamically scale to demand.

[–] EncryptKeeper 14 points 3 months ago (1 children)

Sounds like Kadokawa itself should be broken up

[–] EncryptKeeper 1 points 3 months ago

Bluesky doesn’t even have to be Mastodon. It just has to Twitter before it went bad.

[–] EncryptKeeper 2 points 3 months ago* (last edited 3 months ago)

Unfortunately not as self hosting is really just an amalgamation of a number of different technologies, concepts, groups of best practices, and there are nine and a half viable ways to do any given thing you’ll want to do. For my day job I manage several public systems that serve millions of requests a day and even I can’t really give you a “One definitive way of doing things”, but I have my preferences.

I think if you wanted a rough plan of what would be the most valuable things to learn in which order it would be

  1. Docker, especially persisting your storage and also how its network works. Use containerized services only on your local network at first to get a feel for things, and give yourself the ability to screw things ip without putting yourself in any danger.

  2. VPNs and how they work. You can start with a direct stupid simple VPN like WireGuard, or Tailscale if you want a mesh-VPN. This will allow you to reach your services remotely without having to worry too much about security and the micromanagement that can sometimes come with it.

  3. Reverse proxies for things you’d like to expose to the public. At this point you want to learn as well about things like server hardening, have a system in place to automate software updates etc. there’s a common misconception that using a reverse proxy is innately much safer than port forwarding directly to your services. It can help by obscuring your home IP, and if you pair it with a WAF of some kind that’ll help you with much of the chaff attacks that get tossed your way, but at the end of the day in both cases you’re exposing the web services on your local network to the internet at large, so you have to understand the risk and reward of doing this.

[–] EncryptKeeper 41 points 3 months ago (7 children)

I say this as someone who likes fediverse microblogging (Mastodon, MissKey, etc) it will never be Mastodon. Mastodon and its maintainers are staunchly against all the things that would make it a viable replacement to Twitter.

[–] EncryptKeeper 1 points 3 months ago

Why wouldn’t they?

view more: ‹ prev next ›