starshipwinepineapple

Even if it was github, they have mandatory 2fa now which would help. Still some risks for people who reuse passwords on other services or if their 2fa got compromised (sim swaps), etc but wouldn't be full blown catastrophic

Depends on the programs, but likely statistics if it is a halfway decent program.

• Statistics is harder to learn on your own than the CS needed for data science. So it's better to go statistics and then you can learn the CS parts on your own before doing a data science program.
• There's generally a bigger need for statistical foundation than CS foundation in data science, or at least with the angle for any data science needed for data journalism.

I think you need a polkit authentication agent installed and running to prompt you for your password.

Alternatively you can sudo codium path/to/file (assuming you have aliased codium to use your flatpak)

From the github

@snowe2010's goal is to earn $200 per month pay for our 📫 SendGrid Account: $20 a month 💻 Vultr VPS for prod and beta sites: Prod is $115-130 a month, beta is $6-10 a month 👩🏼 Paying our admins and devops any amount ◀️ Upgrade tailscale membership: $6-? dollars a month (depends on number of users) Add in better server infrastructure including paid account for Pulsetic and Graphana. Add in better server backups, and be able to expand the team so that it's not so small.

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)

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:

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?