• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: August 2nd, 2023

help-circle

  • I’m lucky to have a friend group who all get together semi-frequently on Discord to try out any new games we’ve found and enjoy. We all have pretty similar tastes in games, sometimes a few of us will be playing something others might not enjoy and vice versa, but in those instances we’ll still hang out and chat but just play our separate games instead.

    I would agree that one roadblock is that we all have less time now as adults with careers (and other responsibilities) than we did when we were students, but we do our best to make time all the same.

    In terms of public multiplayer with randoms - not for me, tbh.




  • Well, this is pretty fucking horrific if true.

    Setting aside the factual accuracy of LTT content (which is a separate discussion entirely), the main thing that they did well and that I generally enjoyed was their brand of jank content - like building impractical virtualized gaming setups, stupid water cooling projects, stuff like that.

    If even a handful of these accusations hold water then I would no longer be able to enjoy that content knowing what took place behind the scenes in the process of creating it.

    If all of them turn out to be true…I am neither Canadian nor a lawyer but it sounds like charges could be brought. In that case I don’t see any way that trust in LTT/LMG could be rebuilt outside of some major team members stepping down.









  • It’s been pretty good. I have noticed the default sort order (‘Active’) results in the feed getting stale pretty quickly. Changing the default to ‘New’ has been a better experience so far, at least at the current level of activity.

    I have had a few issues subscribing to communities on remote instances (i.e. not showing up in search, or showing up but with an empty feed when content definitely exists when I check the web UI) - this does not appear to be an SFW/NSFW issue, and some communities from the same remote instances appear correctly.

    Hard to tell if this is an instance/protocol issue, or an app issue.




  • I recently quit my old job which was desperately trying to claw employees back into the office (first 1 day a week, then 2, then 3) for a fully remote role. It’s been a breath of fresh air. My new team is spread all over the country and yet everything runs so much more efficiently compared to my old employer.

    They do have a small office available in case anyone prefers that environment (or perhaps their home isn’t suitable for remote work) but there is no expectation or requirement to come in, other than a suggestion that each team meets face to face maybe a handful of times per year, if only to get lunch/drinks together or have a social day.

    It’s working out great for them as it lets them scale the number of employees they have significantly while not spending any more on commercial real estate.


  • Sounds like the dev was unsatisfied with the low sponsorship numbers on his project, which when you consider how many devs only ever interact with Moq via the package manager or command line might be a fair complaint…but the decision to just start harvesting user data like a lowlife as an alternative source of income is some galaxy brain shit.

    It’s not like this would even be sustainable. What did he think was going to happen, devs would just blindly accept a new shady looking package appearing in their dependency stack with no further investigation?

    As a result of this stupidity Moq will now be on the shit-list of every corporation using .NET, especially those based in Europe due to GDPR implications.