4 ms·
Why? Sadly, there's not much motivation described in the README. You state "Let's move your Medium content to your very own website" and then you push it to Git
by grx 7y ago
Why? Sadly, there's not much motivation described in the README. You state "Let's move your Medium content to your very own website" and then you push it to Github and Netlify, which are yet another silos. Good work with the export, but migrating the content to the next vendor lock-in should be optional. Not to forget that these platforms also collect data about your visitors.
- anchpop 7y agoHow does Github "collect data about your visitors"? The repository is cloned, built and served by Netlify's server. And since I doubt Netlify is injecting any js into my site, I also question the extent to which they can track users.
- dceddia 7y agoNetlify is serving the content, so at the very least, they (and/or the CDN they store the files on) will have a server-side access log of every visitor. Maybe that's not "tracking" per-se, but, if enough sites are hosted on Netlify, they could correlate the visits. As far as I know, Netlify doesn't make this data available to users hosting sites on the platform. My own (perhaps paranoid) theory as to why Netlify is able to provide so much for free is that they're selling the access log data, but I haven't seen any proof of that either, so who knows. Another theory is that storing all those access logs would be huge and maybe they just store nothing...
- jpomykala 7y agoand Gatsby... now you need to maintain this. It’s much better to use something simple like Jekyll. You don’t need all these fancy stuff like GraphQl, SCSS, React etc. And Jekyll can be served directly from Github.