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)

  • 2 Posts
  • 25 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.










  • Rise of Nations (originally released back in 2003) had/has some interesting ideas to reduce some of the busywork:

    • Worker units will automatically try to gather/build nearby after a short (configurable) delay if they’re not doing anything.
    • Cities (the main worker-producing structure) has a rally point option that’s essentially “all nearby empty resource gathering”, so you can queue a dozen workers and they’ll distribute themselves as they’re created.
    • Production buildings can be set to loop over their current queue, letting you build continually without intervention as long as you maintain enough resources each time the queue “restocks”.
    • Units that engage in combat without being given an explicit target will try (with modest success) to aim for nearby units which they counter.

    For the most part, none of the implemented options are strictly better than micromanaging them yourself:

    • You will always spend less time idling workers if you micromanage them yourself.
    • The auto-rally-point doesn’t always prioritize the resources that you would if you did it yourself.
    • Queueing additional units is slightly less resource-efficient than only building one thing at a time.
    • Total DPS is higher if you manually micro effectively.

    But the options are there when you need them, which I think is a a nice design. It doesn’t completely remove best-in-class players being rewarded for their speed as a player, but does raise the “speed floor”, allowing slower players to get more bang for their buck APM-wise, and compete a bit more on the strategy/tactics side of the game instead.






  • 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.