It’ll be an odd one compared to everyone else, but DiRT 3 with some good music playing in the background is awesome.
The physics are awesome, a bit arcady but reasonably realistic and manageable even on keyboard and the replay mode is amazing, makes even the shittiest driver look pro with its camera work.
And the rallycross modes and the montecarlo track are amazing.
With rally cross being high speed dirt circuit racing. Constant bumping and AI cars losing control and messing up if you pressurise then enough makes it a fun experience. Dirt 2 is indeed better in all areas like voice lines in rallycross ,except for the handling and rally but I started with dirt 3 so that’s what I am sticking with
It’s not quite there yet where I am, but I am certainly hoping to a bit later this summer from time to time. I have hopes of WFH (…From Hammock) at some stage, now that I have garden that is suitable.
First and foremost, the user that adviced you to look at the connection speed is 100% right. If you establish a gigabit link with a gigabit device, it makes no sense to upgrade other than future proofing.
There’s no point in going beyond Cat 6a. Keep in mind that the length of the cable is a big factor as well. For 1/2.5GbE, Cat 5e is plenty (for at least 100m). If you plan on going to 5/10GbE now or in the near future, Cat 6a will get you there with ease (for at least 100m). In both cases, keep the cable as close to the required length as possible + a 30cm/1ft service loop (slack) on each end. That will cause no more signal degradation then necessary and make for a clean install.
For the moment, short term, this is a good initiative. But I don’t think it’s a sustainable approach for app developers. Any man in the middle is a potential source of failure.
Likely need to define some basic rbac controls. They signed up, sure, but don’t receive a “user” role until after approval. Then in the home page, when signed in with no roles assigned, they get a banner saying they’re still pending approval and will not be able to post or comment.
The major concern will be retroactively applying user roles to the existing users.
I’m a fan of this approach. That way, we can return a 200/201 on subsequent registrations for the case where an attacker would query if a user name already exists on an instance. If rejected, remove the account. If accepted, add the user role.
kbin.life
Newest