Currently studying CS and some other stuff. Best known for previously being top 50 (OCE) in LoL, expert RoN modder, and creator of RoN:EE’s community patch (CBP).

(header photo by Brian Maffitt)

  • 1 Post
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle

  • I feel like your preference makes sense when aligned from the perspective of a conventional forum-like platform. However I’d argue that that’s missing a core part of what kbin is/was – and by extension what Mbin is – which is the microblog integration alongside the forum-like stuff. With that context in mind, boosts (or whatever term you want to use for “retweet”) make sense to integrate imo.

    Whether or not you think Mbin should try to integrate the microblog side of things is of course a subjective - I personally think it’s a cool idea to try at least, but with how dominant lemmy has become it can be difficult to reconcile differences and incompatibilities between it and other software like Mbin.






  • Thanks for so politely and cordially sharing that information


    edit: I would be even more appreciative if it were true: https://www.rockpapershotgun.com/rocket-league-ending-mac-and-linux-support-because-they-represent-less-than-0-3-of-active-players

    Quoting their statement:

    Regarding our decision to end support for macOS and Linux:

    Rocket League is an evolving game, and part of that evolution is keeping our game client up to date with modern features. As part of that evolution, we’ll be updating our Windows version from 32-bit to 64-bit later this year, as well as updating to DirectX 11 from DirectX 9.

    There are multiple reasons for this change, but the primary one is that there are new types of content and features we’d like to develop, but cannot support on DirectX 9. This means when we fully release DX11 on Windows, we’ll no longer support DX9 as it will be incompatible with future content.

    Unfortunately, our macOS and Linux native clients depend on our DX9 implementation for their OpenGL renderer to function. When we stop supporting DX9, those clients stop working. To keep these versions functional, we would need to invest significant additional time and resources in a replacement rendering pipeline such as Metal on macOS or Vulkan/OpenGL4 on Linux. We’d also need to invest perpetual support to ensure new content and releases work as intended on those replacement pipelines.

    The number of active players on macOS and Linux combined represents less than 0.3% of our active player base. Given that, we cannot justify the additional and ongoing investment in developing native clients for those platforms, especially when viable workarounds exist like Bootcamp or Wine to keep those users playing.







  • Intel fumbled hard with some of their recent NICs including the I225-V,[1][2] which took them multiple hardware revisions in addition to software updates to fix.

    AMD also had to be dragged kicking and screaming to support earlier AM4 motherboard buyers to upgrade to Ryzen 5000 chips,[3][4] and basically lied to buyers about support for sTRX4, requiring an upgrade from the earlier TR4 to support third-gen Threadripper but at least committing to “long-term” longevity in return.[5][6] They then turned around and released no new CPUs for the chipset platform, leaving people stranded on it despite the earlier promises.[7]

    I know it’s appealing to blindly trust one company’s products (or specific lineup of products) because it simplifies buying decisions, but no company or person is infallible (and companies in particular are generally going to profit-max even at your expense). Blindly trusting one unfortunately does not reliably lead to good outcomes for end-users.


    edit: “chipset” (incorrectly implying TRX40) changed to “platform” (correctly implying sTRX4); added explicit mention of “AM4” in the context of the early motherboard buyers.




  • From the submission:

    Not a rival, just an alternative

    The realization that led us to develop PeerTube is that no one can rival YouTube or Twitch. You would need Google’s money, Amazon servers’ farms… Above all, you would need the greed to exploit millions of creators and videomakers, groom them into formatting their content to your needs, and feed them the crumbs of the wealth you gain by farming their audience into data livestock.

    Monopolistic centralized video platforms can only be sustained by surveillance capitalism.

    Even though we cannot pinpoint the exact budget Framasoft spent on PeerTube since 2017, our conservative estimate would be around 500 000 €

    With these two perspectives it seems to be doing well, even if it can’t / won’t entirely displace the major players.


  • Which is exactly how the real world works. Harm has to be identified to suggest solutions.

    According to the submission, some harms have been identified, and some solutions have been suggested [that could reduce the same and similar harms from occurring to new and existing users] (but mostly it sounds like a “more work needs to be done” thing).

    I imagine your perspective on the issues being discussed are different from those of the author. The helicopter parent analogy makes sense in a low-danger environment; I think what the author has suggested is that some people don’t feel like it’s a low-danger environment for them to be in (though I of course – not being the author or one such person – may be mistaken).

    Edit: [clarified] because I realised it might seem contradictory if read literally.



  • Unless you’re also throwing money at YouTube premium (etc), isn’t this by definition unsustainable to do? So it’s not really a viable long-term strategy either.

    Like don’t get me wrong, I don’t want all the tracking and stuff either, but somebody has to pay those server bills. If it’s not happening through straight cash then it’s going to be through increasingly aggressive monetization and cost-cutting strategies.


  • UPDATE: the shutdown has been (for now) retracted.

    The admin (jerry) has switched from kbin to a fork called mbin that has apparently been able to integrate changes faster than the base kbin project. Jerry seems satisfied with the number of issues fixed in the fork (for now), so has retracted the shutdown announcement (for now).

    FEDIA.IO update!!!

    After I made the announcement about shutting down fedia.io, someone pointed out that Melroy, a very active developer on kbin, forked kbin to mbin. I just migrated to mbin and so far it seems to have resolved all the problems I’ve seen. It’s likely too early to tell, but I think that Melroy is VERY responsive and helpful, so I am retracting my shutdown announcement. And that makes me very happy.

    https://infosec.exchange/@jerry/111235153655966812


    Followup: https://fedia.io/m/fedia/t/350673 tl;dr retraction has become more concrete. No need for the “for now” qualifier anymore.