Re: Ad-hoc Server Pro Online Download
Leocricia Flinchum
These secondary servers may be started and stopped on an ad-hoc basis (depending on how crowded the existing secondary servers are), and they will be given a new public IP address when started (perhaps using AWS or Linode-like cloud hosting services). Upon startup, the secondary server will authenticate with the main server, and tell the main server its public IP address (so that the main server can inform incoming clients).
To use a secure WebSocket (wss://) connection, I will need to get a certificate for that server, which probably means I need a sub-domain name to give to each secondary server. But domain names take quite a while to propagate through the Internet, so I won't be able to instantaneously start and use the server.
Unless I get a certificate using the IP address only (meaning that my secondary servers will not have a domain name). Which doesn't seem very secure since cloud hosting services do not retain a fixed IP address upon shutdown of the server.
How should this be properly done? Is there a way to just launch a secondary server instance, and have it set up TLS all automatically? Or should I just forget it all and not use TLS for the secondary servers?
Firstly name "Propagation" isn't real, or rather, it's a legend based only loosely on the facts about DNS caching. If you're serious about this game spinning up servers and tearing them down in real time you will eventually need to learn (or need to hire someone who knows) about this stuff. If you've gotten the idea that "propagation" takes hours, or even days, that'll be from using cheap web-hosting which can't be bothered to offer better service because it doubts you know the difference.
The simplest way to do this, if this is going to be some big service with lots of servers spinning up and being torn down, is to buy a wildcard certificate, that is, one which says *.example.com and works for any server named anything.example.com (no extra dots though, be aware of that, it won't work for something.subdomain.example.com because of the extra dot). Let's Encrypt does not offer wildcards, but, they're not terribly expensive if you only need one to run your whole service.
On the other hand if you're doing things on the cheap, use Let's Encrypt's DNS-01 validation method to let you issue a certificate for a suite of server names in advance of knowing what their addresses will be. So maybe you use this validation to get a certificate listing server01.example.com, server02.example.com and so on up to server40.example.com, you can now use this certificate (and the accompanying private key) for any machines with any of those names that gets spun up. This way of doing things isn't ideal security-wise, but you say you don't care too much about that.
Using the DNS-01 method means you don't need to have the servers actually working when the certificate is issued, just control over their DNS records. You need to figure out the rough number of servers you might need somewhat in advance, but frankly if you're building a game not sure if it'll have five players or five million players, chances are your worst problems aren't going to be with TLS.
Displaying a bunch of html files in your own local web server is easier than it sounds. The package manager npm for the web application framework Node.js comes with a zero-configuration http server that can be started within seconds without any configuration.
Either npm or Node.JS will be available as a package for your distribution. If there is a separate package for npm, then install that, because it will install Node.JS as a dependency. Otherwise just install Node.JS which will contain npm. The package name of Node.JS will be "nodejs" or just "node", depending on your distribution.
If you are too lazy typing the address into your mobile browser, you can use QR codes. Copy the address with CTRL-C into the clipboard, go to one of the many online QR code generators, paste the address with CTRL-V and scan the QR code with a QR code scanner app.
Whenever you modify the displayed file, the page is automatically reloaded. Usually that happens in fractions of a second, so fast that you don't even notice it. If a ressource in that page changes, for example an image or a stylesheet, the DOM of the page gets updated without a reload and only that particular part is updated.
If you want to enable directory listings add --directory to the command line options. And, by the way, you can start as many instances of Browsersync as you want. It will pick the next free port if its default port 3000 is occupied.
The real fun with Browsersync starts, when you point a second or third browser for example on your phone or tablet to your local server. All browsers are synchronized, all mouse clicks, inputs or other user interactions are mirrored across all connected devices.
And wouldn't it be cool to present your new company web site instead of local files and let all people around you follow while you are clicking, scrolling and sending forms? A piece of cake with Browsersync: browser-sync start --proxy Now everybody connecting to your local server will see instead. But be aware that the synching is unidirectional! Everybody connected can control the browser of everybody else.
However, my concern would be: how does the PSNProfiles comunity feels about this? Ive seen other cases where games with locked trophies due to dead servers are unlocked by random hackers in lobbys, and if you happened to be one of those unlucky players, you would be forced to hide your trophy list on PSNP.
So, my question is. Is this the same as those cases? Is using third party tools to unlocked online trophies cheating?. The issue with dead serves locking trophies is that you get taken away a part of a product you paid for. I know its in every ToS, but the problem remains. Is the community at fault for trying to get back what was offered in the first place? Should this be punishable since locked online trophies are unobtainable, hence, not valid anymore?
Firstly, xlink seems to be a program that tricks the game into LAN modes. This will mean that you can indeed play online with others, but the matchmaking will be ad-hoc or lan and not online. If it was that easy people would already have earned the trophy
Secondly, PSNP staff already have a statement on what is allowed and what not. If, somehow, somebody made an application that let people connect to each other, it needs to be open source so that it can be checked and it needs to be in an external matter (so not something you install on a PS3, aka homebrew. The most famous example of servers coming back by the community is gonespy.
I used hamachi back in the minecraft days, you don't have to rent a server then so it was pretty cheap. It was a very long time ago though. But this program creates a Lan environment as well so it's kind of similar to xlink.
But plain hamachi, cq creating a LAN environment /server is not the same as a server were games themselves connect to. And that is the doubt I have with this method. But I would love to have it wrong.
So the latest achiever for online trophies got them on June 28th - 29th. They recently platted the game. I would rule out cross-save since they got the trophies 4 days apart. They are also the number one player in Bahrain, and theyre sitting in top 800 in the world. I would like to think they wont be risking getting banned with those stats. So... there is a way to get online trophies legitimately?
Nope, that person is a hacker and used illicit methods to gain those trophies so report them. There is no way to legitimately earn the online trophies any more so all you can do is chalk this game up as a loss and move on.
7fc3f7cf58