Similar here.

Family is mostly OK on it. We used to have issues with iOS devices not noticing some new messages & calls, but that seems to have stopped a few months ago. Family is usually impatient about me getting to my phone and rings me using 3 different services in a row, one of them Snikket xD

Have not yet managed to get any friends onto it.

Thing is, its EOL, per Asus. Does this mean that it won’t be supported on OpenWRT for much longer?

OpenWRT tends to support devices longer and better than the OEM, but it depends on the popularity of the chipset inside the router.

Many different routers by different companies are almost identical internally, because they use the same chipset. Eg the RT-AC3100 seems to be a bcm53xx variant, of which OpenWRT supports a few dozen products. Support will probably only be dropped when every single one of those devices goes EOL and several years pass (ie no people left contributing/maintaining it and the builds break somehow).

Router chipsets can be very long lived. Many new devices use decade old chipset designs. Some chipset families have almost identical chips released every few years with slightly different peripherals, clocks & pinouts; but are supported by the same kernel drivers.

(This is all much better than the world of mobile phone hardware support. Maybe it’s because of different market pressures? Not to mention you don’t have a monopoly that benefits from keeping the hardware fractured. Imagine if people could make a competitor to Android that works across most devices out there)

As far as I understand, wireguard is designed so that it can’t be portscanned. Replies are never sent to packets unless they pass full auth.

This is both a blessing and a curse. It unfortunately means that if you misconfigure a key then your packets get silently ignored by the other party, no error messages or the likes, it’s as if the other party doesn’t exist.

EDIT: Yep, as per https://www.wireguard.com/protocol/

In fact, the server does not even respond at all to an unauthorized client; it is silent and invisible.

Read-only, or the ability to edit filenames & upload files?

Read only: as per other answers here, basically any HTTP server. The easiest one I know would be darkhttpd, because it requires no config files and can be run without root.

Read write: I like WFM https://github.com/tenox7/wfm

Changing virtual desktops works for me, no patches needed. I have to use it often because of how many games don’t understand multiple monitors.

Technically they have some differences, but the biggest from a user’s perspective is how they are delivered and by whom. Wine is manually installed by you from your distro’s package repo. Proton is provided by steam when you install a windows game on a Linux steam instance. If one breaks then you complain to the relevant party.

It’s a gorgeous game experience. Not to mention they put so many other gamedevs to shame with their technical accomplishments (especially in the expansion – flooding waves in a ringworld!).

Don’t look up spoilers. Get yourself a copy and play it. Find somewhere to land your spaceship :)

Replacing a TCP socket with a UNIX socket doesn’t affect the amount of headers you have to parse.

https://halestrom.net/darksleep/blog/054_nvme/

Summary: two Silicon Power P34A80’s died within a few months of use, the second one was the warranty replacement of the first. In both cases sectors suddenly became permanently unreadable.

In Kerbal Space Program your ships sometimes catch the NaN virus. If one fuel tank level is reading NaN then whatever you do DON’T try and fill it from another (full) tank. I’m not sure if it can spread to physics (thrust, mass, etc) EDIT: Yes it can happen to physics, oh dear.

I wonder what would happen if you landed a NaN-infected spaceship on a planet.

SFF = Small Form Factor. It’s smaller than traditional ATX computers but can still take the same RAM, processors and disks. Motherboards and power supplies tend to be nonstandard however. Idle power consumptions are usually very good.

USFF = Ultra Small Form Factor. Typically a laptop chipset + CPU in a small box with an external power supply. Somewhat comparable with SBCs like Raspberry Pis. Very good idle power consumption, but less powerful than SFF (and/or louder due to smaller cooler) and often don’t have space for standard disks.

SBC = Single Board Computer.

I wouldn’t attack via USB, that path has already been too well thought out. I’d go for an interface with some sort of way to get DMA, such as:

• PCIE slots including M.2 and external thunderbolt. Some systems might support hotplug and there will surely be some autoloading device drivers that can be abused for DMA (such as a PCIE firewire card?)
• Laptop docking connectors (I can’t find a public pinout for the one on my Thinkpad, but I assume it’ll have something vulnerable/trusted like PCIE)
• Firewire (if you’re lucky, way too old to be found now)
• If you have enough funding: possibly even ones no-one has thought about like displayport + GPU + driver stack. I believe there have been some ethernet interface vulnerabilities previously (or were those just crash/DOS bugs?)

I recommend using a different set of flags so you can avoid the buffering problem @thenumbersmason@yiffit.net mentions.

This next example prevents all of your ram getting uselessly filled up during the wipe (which causes other programs to run slower whenever they need more mem, I notice my web browser lags as a result), allows the progress to actually be accurate (disk write speed instead of RAM write speed) and prevents the horrible hang at the end.

dd if=/dev/urandom of=/dev/somedisk status=progress oflag=sync bs=128M

“oflag” means output flag (to do with of=/dev/somedisk). “sync” means sync after every block. I’ve chosen 128M blocks as an arbitrary number, below a certain amount it gets slower (and potentially causes more write cycles on the individual flash cells) but 128MB should be massively more than that and perfectly safe. Bigger numbers will hog more ram to no advantage (and may return the problems we’re trying to avoid).

If it’s an SSD then I issue TRIM commands after this (“blkdiscard” command), this makes the drive look like zeroes without actually having to write the whole drive again with another dd command.

Yeah not one mention of “I’ll never forget you Princess”

To add to this: “level design” typically covers things like the design of paths through the level (both physically and plot/objectives) and visibility of paths affecting player thinking and choices (ie making it clear to the player how to progress, not get lost). These are “big scale” things, not fine detail.

“Gameplay design” typically covers things like movement, interaction and item/skill progression mechanics. The are “small scale” (or for inventories & skill trees: “no physical scale”) things.

In practice the two terms do often overlap quite a bit, so you can argue basically anything to be in either category.

To be pedantic: gameplay design, not level design, but I guess the two overlap quite a bit anyway.

That looks super frustrating :|

I just finished the last level of Perfect Dark (released in 2000 for N64). The hardest part was right at the end (boss fight with rockets being fired at you, one hit and you’re dead) and there are no checkpoints. I repeated this same level so many times and had to read a walkthrough in the end – it turns out I was stuck at a red herring.

N.B. to anyone reading this: ask your isp to “opt out of CG-NAT”. Talking about IPv6 may confuse the staffer you’re talking to, it’s partially related but not the fully picture.

Something nice to see when I searched the steam forum for this game:

FoV is in the settings

Yay!

A few years back I tried playing the original Halo 1. It gave me headaches and my brain simply couldn’t enjoy it.

On a similar note: a lot of modern games using Unity or Unreal seem to be magnets for mouse delay and filtering; which makes me very uncomfortable when playing. Those that have bought Killer Frequency: does it have any of this?