While I think shareholders can be a driving factor, I see it way more often with VC-funded companies. The “2.5x year over year” growth mantra that places like YCombinator stipulate have disastrous effects on small tech companies. Often, these startups have an incentive to keep taking additional funding rounds, which appears to tighten the grip the VC has over them.

Try growing the next Microsoft or Google or Amazon out of that model. I’m not convinced that it’s possible. At least if you bootstrap your own company, you don’t have the same binding obligations…even if it takes way longer to get to a place that’s self-sustaining.

I mean, it certainly looks nicer. At least they’re thinking about ways to make the experience better, for those that use it.

I’m still really happy with SteamOS, the only real downside is that newer AAA games are simply too demanding. Not so much of a problem on the desktop, but certain games just look rough and run at sub-30 fps.

Yeah, I get that it’s not that new, especially since it’s a rebranded fork. But, as a fediverse project with its own brand and design sensibilities, it’s relatively new, especially compared to Mastodon.

Unfortunately, I’ve used the Antennas for like two months, and they’re janky. The “non-retroactive data fill” point that you make is only partially true, and seems to mostly apply to filters pertaining to a collection of users, or a collection of servers as a data source. It’s a confusing UX papercut. Worse yet, my Fediverse Devs antenna example has been around for two months, and barely produces anything most of the time.

I don’t believe that an “official branded app” is strictly necessary. What I meant was more in line with “Firefish could really use apps developed for its features specifically.” Sadly, Misskey compatible apps continues to be a wasteland compared to the plethora of Mastodon ones.

The whole “the flagship instance is a sandbox test instance” is kind of a sometimes-true sometimes-not situation. It’s definitely less stable now than it was two months ago, but that kind of messaging and expectations management didn’t seem to really happen until sometime after the CalcKey migration.

And yeah, proper group / community federation with Lemmy is a huge deal! I’m looking forward to what Pixelfed is doing with Groups, as they look somewhat similar, and aim to maximize compatibility while providing good management tools.

Wow, thanks for the great in-depth feedback! 🤩

Yeah, there’s definitely other areas I could’ve delved into, like Public Clips or MFM or pagebuilding. These in-depth reviews are challenging, due to trying to strike a balance between features and actually getting something published. Most articles of this nature takes me weeks, sometimes even a month or more.

The UI definitely has a learning curve, too, but as a veteran Fedi user, it suited me just fine. I’ve dealt with far, far worse 😂

The instability really bums me out. I’d like to think that things are slowly improving, but the lack of transparency (and frankly useless error messages) make it really hard to triage where the problem is and forge a path forward. The lead dev has also been sick recently, and suddenly is not very active online.

Finally, I think Firefish takes part in a long tradition of Misskey forks, where a half dozen systems all branch off of each other. It’s a shame that more of them don’t collaborate on the same platform, leaving many devs to cherry-pick across forks. I wonder sometimes whether this hurts development more than it helps.

What’s weird is that the site is still up and works fine. My guess is that maybe the developer lost interest, or was busy with other things.

Hey, final update here - I managed to get the game working again! I think a patch came through somewhere that broke something - maybe it was ProtonGE, maybe it was Valve patching Proton Experimental, maybe it was Bethesda putting out something weird in a patch. Regardless, I got a tip that you can upgrade your Linux kernel to 6.5.x, and upgrade to the latest Mesa git drivers. The game is now running smoothly again without any issues on Wayland!

Alright, bit of an update: after investigating my hardware, doing a fresh OS install, and trying just about everything that everybody’s suggested to me so far, I have logs. Definitely amdgpu related, but not 100% sure what is going on yet. This was on Wayland, searches for similar error messages suggest a possible driver bug, maybe issues with particular kernel versions? Still investigating.

amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800131efe000 from client 0x1b (UTCL2)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201031
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x1
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800131efe000 from client 0x1b (UTCL2)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201031
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x1
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800131efe000 from client 0x1b (UTCL2)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201031
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x1
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800131eff000 from client 0x1b (UTCL2)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800131eff000 from client 0x1b (UTCL2)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800131efe000 from client 0x1b (UTCL2)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
Sep 24 02:30:00 Asmodeus kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered

Yeah, I’ve tried several, of both the GE and Experimental varieties. The problem persists, sadly.

It feels as though the game is suddenly only capable of loading interior spaces, despite the game running great as recently as two days ago.

Unfortunately, I’m not sure as to how to find them, or enable them if they’re not already working. I agree that logs would definitely help here.

Yeah, it’s possible. I’m curious, though, as to why it affected my other saves retroactively? Like, I can run around within TMD / the old Red Devils facility just fine, but the game craps out when I set foot on Mars.

Yeah, I agree. Something that I’m tinkering with right now involves removing the comment form found at the bottom of articles, and replacing it with instructions on how to federate with the conversation tree instead.

Yes, the reader’s guide is here: https://wedistribute.org/2023/09/follow-wordpress-on-fedi/

Sure, as an open source project, everybody owns the code. But, Automattic is the corporate arm directly involved with the project, employs many of the project’s developers, and holds the trademark.

Interesting. Are Lemmy users themselves not Person/User actors? It seems like Lemmy might benefit from allowing those types to be followed, or at the very least, viewed.

Would it at all make sense or work for wordpress bloggers to “at” lemmy communities in the same way masto users have to in order to post to lemmy? It would be just like hashtags, which I presume could also work over on mastodon etc?

It’s an interesting thought, but: as an author, I have no pre-emptive concept of who is going to be reading my posts, or which community I should share something to specifically. I think it would be easier to just make certain kinds of Actors and activity types visible to Lemmy, so that those posts can then be reshared to whatever communities that somebody cares about.

If this diagram were actually true, pretty much every platform in the space would have died years ago.

I’m in the process of writing one! Just finished a basic guide for readers, now working on one for admins.

Forgefed is super cool, and holds a lot of promise for collaborative coding on the Fediverse itself.

I wrote about some of the development and background of the project here: https://wedistribute.org/2023/06/the-future-of-code-collaboration-might-happen-across-the-entire-web/

Yeah, I love Friendica. The UI definitely needs more love, but it’s really come a long way. The team and dev community is also very welcoming, lots of great people there.

I personally really like Firefish, though it definitely needs better client apps that can support all of its features. https://joinfirefish.org/

I’ve read denschub’s positions in the past, and fundamentally disagree with him. While he raises a lot of interesting points in his writings on the subject, most of the limitations described have been largely overcome.

Unfortunately, he makes up a significant part of the current core team, and seems to default to hostilities any time the subject is breached.