I use hyprland and can bind stuff through their config, whether that is some library functions or executing a script i wrote. I'm sure there are other ways to do similar with different desktop environments.
It you're looking for ideas-- Something you're passionate about. Find a problem you're having, fix it, and make it open source. That's the best way to make sure whatever you do doesn't get abandoned. Good luck
I sent you a DM to test DMs in the instance. I think it went through ok. As far as deleting goes, i don't see a way to delete in voyager so I'm not sure on that part.
It's a shame that the fediverse doesn't have a better way to stop these mass DMs though
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:
boot from live usb (arch or cacyos).
mount btrfs partition and access your snapshots.
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:
Static website builder. I use hugo but there's a few others like jekyll, astro
Use a git forge (github, gitlab, codeberg).
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.
The best way i found was obsidians import which was what i was trying to avoid. I was making standalone markdown files and after the import i needed to do some cleaning since obsidian or onenote did OCR on the images to create alt text but quotes in the alt text broke image links.
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
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.
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.
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!
Is Arch Linux the right fit for a newbie to Linux? The right answer is "it depends", not "never". Would I recommend Arch to my mom? No. Would I recommend it to my programmer colleague who already lives in the Powershell? Sure, why not.
Yup, i had a lot of people tell me that arch wasn't a good beginner distribution, and had some friends try to talk me out of it. But i was planning to move to Linux for over a year and had set up Linux servers in the past. Just hadn't used one for my main PC. I've been on arch for over a month and it's been fine. I still wouldn't recommend it to every beginner but I'm not going to say it's never appropriate.
Codeberg pages comes to mind (for a simple personal site anyway)