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

  • 6 Posts
  • 2.44K Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • That’s not Cloudflare-specific; you can use any CDN that supports origin pull in the same way :)

    It’s not ideal because… Cloudflare… but at least you’re using standard web tools. To ditch Cloudflare you just unplug them at the domain and you still have a website.

    Definitely agree with this! That’s one of the pain points of “cloud” services - they really try to lock you in, making it impossible to swotch.

    without having to deal with LetsEncrypt.

    You still need encryption between your CDN and your origin, ideally using a proper certificate. Let’s Encrypt (and other ACME services like ZeroSSL) are pretty easy to use, and can be fully automated. I’m using Let’s Encrypt even for internal servers on my network, using a DNS challenge for verification instead of a HTTP one.

    Perhaps its irrational but I’m bothered by how many people seem to think that Github Pages is the only way to host a static website

    It’s strange because out of all the possible options, Github Pages is the most basic. You have to store your generated files in a Git repo (which is kinda gross) and it barely supports any features. For example, it doesn’t support server logs or redirects.

    I guess it’s popular because people already use Github and don’t want to look for other services?


  • You seem to recommend a VPS but then suggest a bunch of page-hosting platforms.

    Other comments were talking about pros and cons of self-hosting, so I tried to give advice for both approaches. I probably could have been clearer about thay in my comment though. I edited the comment a bit to try and clarify.

    I have some static sites that I just rsync to my VPS and serve using Nginx. That’s definitely a good option.

    If you want to make it faster by using a CDN and don’t want it to be too hard to set up, you’re going to have to use a CDN service.

    Self-hosted CDN is doable, but way more effort. Anycast approach is to get your own IPv4 and IPv6 range, and get VPSes in multiple countries through a provider that allows BGP sessions (Vultr and HostHatch support this for example). Then you can have one IP that goes to the server that’s closest to the viewer. Easier approach is to use Geo DNS where your DNS server returns a different IP depending on the visitor’s location. You can self-host that using something like PowerDNS.








  • dan@upvote.autoSelfhosted@lemmy.worldDo you selfhost your own blog/website?
    link
    fedilink
    English
    arrow-up
    28
    arrow-down
    2
    ·
    edit-2
    16 hours ago

    A VPS still counts as self-hosting :)

    I host my sites on a VPS. Better internet connection and uptime, and you can get pretty good VPSes for less than $40/year.

    The approach I’d take these days is to use a static site generator like Eleventy, Hugo, etc. These generate static HTML files. You can then store those files on literally any host. You can stick them on a VPS and serve them with any web server. You could upload them to a static file hosting service like BunnyCDN storage, Github Pages, Netlify, Cloudflare Pages, etc. Even Amazon S3 and Cloudfront if you want to pay more for the same thing. Note that Github Pages is extremely feature-poor so I’d usually recommend one of the others.




  • it’s legal to dump that game to a PC and play it on a Switch emulator, right?

    Depends on where you live. Copyright law varies significantly from country to country.

    In the USA, section 117 of the copyright act lets you create a copy for archival/backup purposes only. What I’m unsure about (and don’t know if there’s any relevant caselaw) is whether bypassing copy protection to create the copy violates the DMCA.

    The equivalent Australian copyright law explicitly states that you can use the backup copy instead of the original one. The US law doesn’t (all it says is that you can make an archival copy, not how you can use the archival copy), so it’s a grey area.

    Both laws are for “computer software”, but you could easily argue that a video game is computer software.






  • Their strange stock vesting schedule makes me think that they’re aware that people won’t actually want to stay for four years. A back-loaded vesting schedule never benefits the employee, only the employer.

    Other companies usually have an even schedule, for example Meta vests 25% per year (actually it vests quarterly instead of yearly). Google is an outlier too, but they do the opposite of what Amazon does - 33% in year one, then 33%, 22% and 12%. I suspect Google do this so they can list a higher total compensation (since initial total comp is salary, stock, and benefits for the first year), but getting more of your stock sooner is a good thing.