I appreciate this, but at the same time I recognize that personal sites can contain very personal information (in content) and with the way the landscape of public repos and AI is evolving, as well as general exploitation, I am still hesitant to make mine public.
I was just lamenting the public requirement the other day for automated Micro.blog backups, so this was top of mind when I saw this toot. If it was just code, I would be less hesitant, but it isn't.
personal sites are too, uhh, personal for everyone to open-source.
i also don't want to be in a situation where any rando can fork the repo, change the name in the header, and host it on their domain, with really very little effort
Add comment