starshipwinepineapple

I think the biggest thing I've seen are the privacy concerns over them getting such a large % of the internet's https traffic that it's essentially a man-in-the-middle (which includes your tunnel traffic).

Very cool. And the snippet execution is really neat.

Worth mentioning for those who care- radicle is funded by radworks, basically a crypto organization. (Source: their faq)

It sounds like the error you're seeing is from attempting to restore the root subvol (@) while the booted into the system

To fix you'll want to:

1. boot from live usb (arch or cacyos).
2. mount btrfs partition and access your snapshots.
3. Restore root subvol from live environment

If you are still having issues you may need to chroot into the root partition and do an update to ensure your system images match what your bootloader is expecting.

This is something that doesn't really need to be self hosted unless you're wanting the experience. You just need:

1. Static website builder. I use hugo but there's a few others like jekyll, astro
2. Use a git forge (github, gitlab, codeberg).
3. Use your forges Pages feature, there's also cloudflare pages. Stay away from netlify imo. Each of these you can set up to use your own domain

So for my website i just write new content, push to my forge, and then a pipeline builds and releases the update on my website.

Where self hosting comes into play is that it could make some things with static websites easier, like some comment systems, contact forms, etc. But you can still do all of this without self hosting. Comments can be handled through git issues (utteranc.es) and for a contact form i use 'hero tofu' free tier. In the end i don't have to worry about opening access to my ports and can still have a static website with a contact form. All for free outside of cost of domain.

Im not familiar with doku wiki but here's a few thoughts

• privacy policy is good to have regardless of what you do with rest of my comments
• your site is creating a cookie "dokuwiki" for user tracking.
• cookie is created regardless of user agreement, rather than waiting for acceptance (implied or explicit agreement). As in i visit the page, i click nothing and i already have the dokuwiki cookie.
• i like umami analytics for a cookieless google analytics alternative. They have a generous free cloud option for hobby users and umami is also self hostable. Then you can get rid of any banner.

So only good tutorials/ guides are allowed?

How does one get from shitty to good if they can't try to begin with?

Does this apply to other things, like coding, as well?

1. Site wasn't properly reflexive for mobile
2. If this is a portfolio then i would remove a lot of stuff like "watch list" and "current obsession". The focus should be on your work and future projects
3. Notes are ok for a start but can be improved. I think a "posts" or "blog" would be better section title, and the content should try to teach something you've learned rather than be the notes you took for a subject. The difference is that teaching reinforces your understanding of the topic. So pick something smaller from those topics and teach it. I wouldn't redo your current notes necessarily, but going forward i would pick a more focused topic and teach.
4. i would then move the "blog" or "posts" to your front page to show the most recent content and then link to /posts where the rest of it can be found. Or highlight projects on front page instead depending on what you want focus to be.
5. move your front page content to a more "resume" section that includes a section for the tools you know. And still think about the length/space of this page. Like a printed resume, too long is bad. So make sure it outlines things nicely

Overall if it was just a personal site id say its ok. But as a portfolio site you have some work to make it align with your goals. Good luck!

1. User devices (main workstations, phone photos, etc)
2. Local NAS (sync w/ #1, backup to #3)
3. Cloud backup w/ commercial provider

They added 2 weeks to it.

Here's a txt summary of the books

And a shorter txt summary

I have had the same experience. Have used all three at some point but mostly use nginx for new servers