deadsuperhero

deadsuperhero, 24 days ago

Honestly? I’m loving it. The biggest improvement for me was getting rid of those awful PIT menus that were ugly and sometimes hard to use. The new system is way more usable, and I’m tweaking the mappings on my controller to see what feels the most usable.

The improvement to EVA is also phenomenally good. You move a bit faster, there’s more precision, and traversal between EVA and ship is much smoother. As a salvager that gets in and out to scavenge cargo holds, this is a big deal to me.

The character customizer is also really fun to use, and feels pretty intuitive to use. There’s still work to be done in explaining what all of these vertices do, but I think the customization is a lot more flexible.

Some pretty nasty bugs emerged in 3.23 and 3.23.1, but it seems like the team is making pretty good progress on improvements? So, there’s that.

deadsuperhero, 24 days ago

One edge case that I really want to see the team nail down is crash loops. In the EPTU build of 3.23, we noticed situations where recovery effectively acted like a rewind feature, but didn’t actually prevent the cause of a crash from happening.

Having to experience a handful of the same crashes during a single play session is pretty painful.

deadsuperhero, 23 days ago

I mostly meant the old system where all options were just a bunch of floating neon text. It was…functional, I guess, but the new system is so much better from a controller perspective. It’s not perfect yet, things like elevator buttons are still in a weird spot, but most things are a lot easier to deal with.

deadsuperhero, 30 days ago

It’s a different approach with different ideas. It uses open protocols, focuses on data and account portability, and incorporates peer-to-peer concepts in its architecture. The vision behind Bluesky is to build a global square with these concepts.

I definitely wish they would’ve extended ActivityPub and collaborated on the wider network, but I kind of understand wanting to start from scratch and not get involved with the cultural debt Mastodon brought to the network.

deadsuperhero, 30 days ago

I can’t tell whether this is serious or sarcastic 😅

As far as the “global square” part of the equation is concerned: yeah, you’re right! A firehose of public statuses requires indexing to work, as a basic foundational premise.

However, there’s nothing preventing someone from standing up a PDS, opting out of the firehose / big graph service, and instead leaning on federation between individual PDSes. I’m not saying it would necessarily be a common use-case, but it’s definitely not impossible.