Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @[email protected]

  • 0 Posts
  • 1.6K Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle
  • What’s the difference between starting to play on Thursday vs starting to play a few days later though?

    There’s likely to be bugs on initial launch, too. Even Rockstar aren’t perfect. With new games, I usually wait a while until all the major bugs are fixed before playing.







  • Unfortunately regular people don’t understand why they’d use something like this rather than just using Facebook, Instagram, Google Photos, etc. and the major limitation of self-hosting this way is that it’s only accessible when your computer is on, which regular people aren’t used to.

    A lot of people also had pretty limited bandwidth. I was in Australia on ADSL2+ with around 9Mbps down and 700Kbps up.

    I think plug-and-play NAS systems are the closest equivalent today, especially now that a lot of people have faster connections. Comcast boosted upload speeds in some markets last year - in my area their regular plans start at 300Mbps down and 100Mbps up. A lot of NAS systems are still missing the “regular person can easily set it up” aspect though, and I’m not sure if they handle sharing stuff with external users.


  • The US does! The majority of internet traffic in the USA (around 55%) is via IPv6. This was driven by two things:

    1. Comcast was the first major ISP worldwide to roll out IPv6 to customers, 15 years ago in 2011. They finished the rollout in 2014, and 70% of their customers were using IPv6 within a year.
    2. Mobile carriers use IPv6 a lot. T-Mobile’s network is fully IPv6-only, using 464XLAT to connect to legacy IPv4-only servers. No CGNAT. They’ve done several presentations about it. The other carriers aren’t too far behind.

    The fact that IPv6 usage isn’t higher is mainly limited by servers not having it enabled, not users. IPv6 usage spikes on weekends and after business hours because there’s a lot of enterprise systems that people use at work, that only use IPv4.

    It’s frustrating that other countries adopted CGNAT instead of switching to IPv6 like the US mobile carriers did. Argentina has less than 30% IPv6 adoption for example.


  • I’m still kinda that Opera Unite didn’t take off. It was a decentralized server built into the Opera browser, that was easy enough for regular people to use. You just set it up in a config UI in the browser and could enable features like chat, blogs, photo galleries, a music player, etc. At the time, everyone had UPnP enabled, CGNAT wasn’t a thing, and Opera handled UDP hole punching for it, so it mostly just worked. https://www.wired.com/2009/10/opera-unite-puts-the-web-server-in-your-web-browser/

    This was back when Opera were still based in Norway, had their own browser engine, and were very innovative. A large number of features that became commonplace were in Opera years before any other browser, like tabbed browsing, full-page zoom (browser zoom used to only increase font size while keeping everything else the same size!), restoring your tabs when you re-open the browser, pop-up blocker, a new tab page that shows your commonly accessed sites, private/incognito browsing, sidebars, and more.

    Sure, there’s a bunch of downsides to a server being built into your browser, but it was an interesting idea. People that don’t know anything about servers were able to easily try it out.


  • It’s because the outage went on for a very long time (over 24 hours to get Outlook operational again!) and more and more companies continue to migrate critical services to “the cloud” (someone else’s computer) because Microsoft convinced company leadership that it’s “more reliable” and that relying on a single vendor for everything is totally okay and can never go wrong.

    So many companies don’t think about hot/warm spares or multi-vendor failover strategies any more because they outsource their thinking to Microsoft or Google. I’ve seen plenty of cases where companies were only able to recover from major issues because they had fully redundant backups or failovers at another vendor (one example - in this case they did it right, with multi-region redundancy on Google Cloud in addition to full backups on AWS - so they were able to recover from Google accidentally deleting all their data)


  • I suspect that institutional knowledge about dealing with Exchange’s quirks is slowly going away as older employees move to other teams, companies, or retire, and are replaced with younger people who think they can solve everything using AI.

    Microsoft’s been dealing with email for a very long time, starting with Microsoft Mail in 1988 then Exchange in 1996. Most of the newer features are just bolted on to the older systems. There’s plenty of legacy cruft in Exchange server (similar to how Windows 11 still has bits from Windows 95 and even icons from Windows 3.0 in it) and that’s the same codebase they still use for Microsoft 365 email.





  • dan@upvote.autoSelfhosted@lemmy.world•Git control for novice gamedev?
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    1
    ·
    edit-2
    7 days ago

    I’d recommend learning Git entirely locally first. Git is a distributed version control system, which means that it doesn’t need a server. All of Git’s features are available to you even with just a local repo.

    Honestly, using Github is totally fine as a beginner. Similarly, using a GUI is totally fine. Dont let people shame you into using the CLI all the time if you don’t want to. It’s good to have a high level understanding so you can deal with things when the GUIs play up, but day-to-day usage is totally fine in a GUI. I like gitg because of how simple it is, but I like the Git integration in VS Code, and Jetbrains IDEs (Rider, WebStorm, etc) too. I’ve heard good things about GitKraken but it felt a bit slow last time I tried to use it.

    When you do want to have the repo on a self-hosted server for your own use, you don’t actually need anything fancy like Gitlab or Gitea. Technically all you need to do is copy the repo from your computer onto the server and set up a Git server on it. That’s it. Git works over SSH, so you’d just add a “remote” that points to the server.

    The best place to start with that is probably the official documentation: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols

    The repo on the server is not really any different to the one on your computer. All you’re doing when pushing is synchronizing them - pushing new changes from your local repo into the one on the server.

    Where web UIs have an advantage is that they make it easier to browse the repo, show it to others, have pull requests and CI support, etc. Lots of value-add features on top of Git itself.

    I’d highly recommend Forgejo instead of Gitea. The Forgejo site has a list of reasons why, so I don’t go over that in detail. Forgejo is what powers Codeberg, so you could try Codeberg first, then if you like it, self-host the exact same system. Note that Codeberg only allows open-source projects.


  • dan@upvote.autoLemmy Shitpost@lemmy.world•Pro gamer move.
    link
    fedilink
    arrow-up
    45
    arrow-down
    2
    ·
    7 days ago

    I think you need to be an uninsured American to really appreciate this joke. Ambulance coverage is $55/year where I’m from (Melbourne Australia), including air transport when needed. I’m in the USA now but ambulance rides are covered as part of the copay for ER visits ($100 on my plan).


  • If you do buy refurbished drives, ideally get manufacturer refurbished ones that come with a manufacturer warranty. If you’re in the USA, ServerPartDeals is a great store for it.

    Manufacturer refurbished drives tend to be pretty reliable because they’ve been tested to meet the manufacturer’s specs, usually including a deep stress test, and come with a warranty from the manufacturer.

    The thing that sucks at the moment is that refurbished drives cost more than the new ones used to cost.