starshipwinepineapple @ starshipwinepineapple @programming.dev

Posts

2

Comments

138

Joined

1 yr. ago

I see that code.forgejo.org currently has version 11.0 deployed which afaik is not released yet, so is that instance just for testing purposes?

Correct, you just don't see the disclaimer if you go straight to code.forgejo.org. if you are on the main forgejo page and click "try it now" you'll see the disclaimer:

"FOR TESTING ONLY, ALL DATA CAN BE WIPED OUT AT ANY TIME"

So to break it down:

• codeberg e.V. - nonprofit democratic organization that owns codeberg.org and forgejo (or at least funds forgejo)
• Codeberg.org a public forge that runs forgejo
• forgejo.org - the forge software that can be self hosted
• code.forgejo.org - test public forge, data can be deleted without notice

Also worth noting there are other public instances of forgejo and codeberg also encourages of alternative libre forges

What is the relationship between Radicle and the Radworks ($RAD) token?

Radicle is a true peer-to-peer protocol. It doesn’t use nor depend on any blockchain or cryptocurrency.

Radworks, the organization that has been financing Radicle is organized around the RAD token which is a governance token on Ethereum.

From the FAQ in case it's relevant to anyone

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).

This is what i did. There are many static website generators that can help. I use Hugo which let's me write in markdown, download themes (modify if i want), and it builds the site which can be hosted for free on codeberg/cloudflare/gitlab/github 'pages' feature. All support letting you use custom domain if you have one.

Codeberg pages comes to mind (for a simple personal site anyway)

Looks fairly impressive, including live collaboration

Very cool. And the snippet execution is really neat.

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.

Liberapay might interest you. Not quite the same but maybe close enough

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

Codeberg pages is indeed a thing

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.

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.

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?

private

Just make sure to read their FAQ

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!

What is the point in being Archbased and only now supporting Btrfs out the box?

It sounds like ext4 is still an option during install, the change is just that the default filesystem is btrfs.