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

  • 1 Post
  • 751 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

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





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






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








  • Also, nobody reads the actual posts, just the headlines. They were accidentally stored in logs:

    As part of a security review in 2019, we found that a subset of FB users’ passwords were temporarily logged in a readable format within our internal data systems,

    which is something I’ve seen at other companies too. For example, if you have error logging that logs the entire HTTP request when an error happens, but forget to filter out sensitive fields.