consider: move to codeberg

[Graison-P]

well reason 1 is that

my district blocks anything with *.github.io.

reason 2:
we can make a yml that auto-transfers items to codeberg.
infact, I have one!

[github-actions]

Hi @Gvyt! Thanks for raising this issue.

It seems you're suggesting a move to Codeberg due to access restrictions with GitHub Pages (*.github.io) in your district and proposing an automatic item transfer process using a YAML configuration. This could be a helpful solution for users facing similar access issues, and having an existing YAML setup sounds promising for simplifying the migration process.

Feel free to share additional thoughts or details, and the maintainers can further explore if this aligns with OmniBlocks' goals. Moving platforms is a significant decision, so this will likely need some careful consideration. Thank you for contributing!

[Graison-P]

(here is the yml for refrence)

name: Sync to Codeberg

on:
  push:
    branches:
      - main # Run this workflow for the main branch

jobs:
  sync:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v3

      - name: Push to Codeberg
        env:
          CODEBERG_USERNAME: ${{ secrets.CODEBERG_USERNAME }}
          CODEBERG_TOKEN: ${{ secrets.CODEBERG_TOKEN }}
        run: |
          git remote add codeberg https://${CODEBERG_USERNAME}:${CODEBERG_TOKEN}@codeberg.org/your-org/your-repo.git
          git push codeberg main

[Graison-P]

@supervoidcoder

[supervoidcoder]

Heck no, I don't know why everyone tells me to go to codeberg, as codeberg is objectively a downgrade as it doesn't have many major features of GitHub. It's practically useless, and just extra labor for quite literally no reason. The only """benefit""" (other than blocking, as you said) that is the whole premise of codeberg, is that it is "open source" and "non profit". While that's good and all, why would that affect me? What do I care in the slightest? There is absolutely no need to reinvent the wheel. GitHub pages has worked perfectly for years for me, with literally no downsides. Also, your "reason 2" isn't a reason, it's more of a how.
Anyways, while I feel codeberg is doing something pretty good by being open source and nonprofit, it reinvents the wheel and again, is useless labor. What are the real benefits? Is it because of training Copilot? Go right ahead and shove all of OmniBlocks while you're at it! What's the point? The code is open source to begin with. How does an AI being trained off it make any different than just a regular human learning from it or even copying it?
Codeberg is also slower, smaller, nowhere near as big community, etc. I can find many downsides to codeberg.

@coderabbitai what do you think?

also, @ampelectrecuted already asked me this I'm pretty sure

[supervoidcoder]

Heck no, I don't know why everyone tells me to go to codeberg, as codeberg is objectively a downgrade as it doesn't have many major features of GitHub. It's practically useless, and just extra labor for quite literally no reason. The only """benefit""" (other than blocking, as you said) that is the whole premise of codeberg, is that it is "open source" and "non profit". While that's good and all, why would that affect me? What do I care in the slightest? There is absolutely no need to reinvent the wheel. GitHub pages has worked perfectly for years for me, with literally no downsides. Also, your "reason 2" isn't a reason, it's more of a how. Anyways, while I feel codeberg is doing something pretty good by being open source and nonprofit, it reinvents the wheel and again, is useless labor. What are the real benefits? Is it because of training Copilot? Go right ahead and shove all of OmniBlocks while you're at it! What's the point? The code is open source to begin with. How does an AI being trained off it make any different than just a regular human learning from it or even copying it? Codeberg is also slower, smaller, nowhere near as big community, etc. I can find many downsides to codeberg.

@coderabbitai what do you think?

also, @ampelectrecuted already asked me this I'm pretty sure

plus, for the district blocking thing, we could always get another domain someday.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@supervoidcoder, I appreciate you asking for my perspective on this. Let me offer a balanced view:

Your reasoning is pragmatic and valid. GitHub offers:

• Robust ecosystem: Actions, Pages, extensive integrations, large community
• Feature completeness: Advanced CI/CD, security scanning, project management tools
• Network effects: Larger developer community, better discoverability
• Proven reliability: Established infrastructure you've successfully used for years

The "if it ain't broke, don't fix it" principle applies well here—you've built a workflow that works.

However, Gvyt raises a legitimate accessibility concern: some networks block *.github.io. This isn't trivial for users who genuinely can't access the site. A few potential middle-ground solutions:

1. Custom domain: GitHub Pages supports custom domains (e.g., omniblocks.dev). This bypasses *.github.io blocks while keeping all GitHub infrastructure.
2. Mirror/redirect: Keep GitHub as primary but set up a simple redirect from another domain to your GitHub Pages site.
3. Alternative hosting for static pages: Use Cloudflare Pages or Netlify (both can auto-deploy from GitHub) as an alternative endpoint.

Regarding AI training concerns: I understand both perspectives. Your code being open source already means anyone can learn from it, as you noted. The AI training debate often comes down to personal philosophy rather than practical impact.

Bottom line: You're the maintainer. If GitHub meets your needs and your contributors' needs, there's no compelling reason to migrate. The platform choice should serve your project's goals, not ideology. That said, addressing the accessibility issue (via a custom domain perhaps?) might be worth considering separately from a full migration.

What matters most is that the project remains maintainable and accessible to you and your team. 🐰

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@supervoidcoder, exactly! A custom domain is a practical middle-ground solution. It addresses the accessibility concern (bypassing *.github.io blocks) while keeping all the GitHub infrastructure and workflow you're already happy with.

GitHub Pages makes this straightforward—you can point a custom domain to your Pages site without changing anything else about your setup. No migration headaches, no loss of features, and you maintain the ecosystem that's working for you.

Sounds like you've got a sensible path forward that doesn't require reinventing the wheel. 🐰✨

[supervoidcoder]

@coderabbitai

omniblocks.net
Closest match

$20
$14

omniblocks.org
$20
$9

omni-blocks.com
$20
$14

omniblocx.com
$20
$14

omneblocks.com
$20
$14

omniblocks.store
Promotion

$20
$4

omniblocks.online
$20

omniblocks.tech
$20

omniblocks.studio
$40

omniblocks.company
$30

omniblocks.info
$20

omniblocks.studio
$40

omniblocks.dev
$30

omniblocks.xyz
$20

omniblocks.tech
$20

omniblocks.store
$20
$4

omniblocks.art
$30
$4

omniblocks.mx
$50

omniblocks.club
$20

omniblocks.live
$20

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@supervoidcoder, great to see you're seriously considering the custom domain route! Here's my take on the best options from your list:

Top Recommendations:

1. omniblocks.org - $9 ⭐

   • Best value for an open-source project
   • The .org TLD signals community/non-profit nature
   • Professional and trustworthy
   • Great price point

2. omniblocks.dev - $30 ⭐⭐

   • Perfect fit for a developer tool/blocks project
   • Modern and instantly communicates "this is for developers"
   • Becoming increasingly popular in the dev community
   • Worth the premium if you want strong brand alignment

3. omniblocks.net - $14

   • Classic, reliable TLD
   • Good middle ground between price and professionalism
   • Widely recognized and trusted

Skip These:

• omniblocks.store ($4) / omniblocks.art ($4) - While cheap, these promotional TLDs will likely renew at much higher rates and don't align with your project's purpose
• omniblocks.xyz, .club, .live - Less professional perception, though technically fine
• omniblocks.studio, .mx - Either too expensive or not relevant to the project

My Pick:

If budget isn't a concern: omniblocks.dev (signals exactly what this is)
If keeping costs down: omniblocks.org (best value + perfect for open source)

Both solve your accessibility problem and give you a professional presence. You can't really go wrong with either! 🐰

[Graison-P]

@supervoidcoder, maybe do .com or .dev

[supervoidcoder]

@supervoidcoder, maybe do .com or .dev

yeah but im kinda broke so for now m sticking to github.... i said someday so 🥀✌️🥲

[Graison-P]

@supervoidcoder, maybe do .com or .dev

yeah but im kinda broke so for now m sticking to github.... i said someday so 🥀✌️🥲

ahem freedns.afraid.org ahem