First #codeberg and first #pinxi issue:
It was a good issue, which made me finally complete the pinxi/tools/gpu_raw.pl and gpu_ids.pl device ID tools to handle adding manually generated nvidia gpu ID data.
So that logic is much more solid now, and amd/intel/nvidia gpu ids are updated in pinxi.
Completely forgot to mention, I updated #AdvancedServerList to v3.5.0 which adds a new option to set a max player count to display.
This option is different from extraPlayers by not changing max players based on online players.
Also, repo is now on #Codeberg which I'm really happy about.
Finally got around to migrating all my non-trivial git repositories from MS/GH to #Codeberg - just before the 2FA-MS/GH-probably-will-require-your-telephone-number deadline. :) I'm keeping my account there since some communication  with #TyrannyOfConvenience people can still be useful.
Not to be outdone, I packaged #inxi 3.3.30 for #TinyCore and shipped it off, though their systems are not as automated so that is more dependent on when the person puts it into their repo. This does not however grab inxi from a source repo, I just get it from smxi.org because that's easier. So I am not the second person to package inxi from the new #codeberg source repos.
New #inxi 3.3.30 out the door! First release that is #codeberg primarily. Note that all the new data and docs in the codeberg #pinxi repo are not on github, and that's basically all the dev data/docs for inxi.
The tags were updated on github/codeberg since gh is mirrored to cb, but that won't last forever. Hopefully packagers adjust.
I don't think there's any practical difference between logging in with accounts registered with those services and using a password. No matter what you use, all functionality should be available.
Did it as follows:
1. Clicked New Migration button and used a GitHub token (created on https://github.com/settings/tokens/new) with no permissions.
2. After migration, I modified GitHub repo to add README saying the project was migrated, changed description and project link. Example: https://github.com/xfix/enum-map
3. I also rewrote CI scripts for Woodpecker CI (access can be requested at https://codeberg.org/Codeberg-e.V./requests).
The visible changes are the addition of 'Geoidal separation' field to the display data and a more compact display of various DOP values. As usual, there are also some small bugs fixed, and an update to the Gnome SDK version 45 in the flatpak package.
@n0toose Harness (developers of #Gitness) would rather prefer if people wouldn't know about projects that are actually owned by the community like #Forgejo (maintained by #Codeberg e.V. non-profit organization) or #SourceHut (which is licensed under AGPL and doesn't ask to sign a CLA for contributions - https://sourcehut.org/blog/2022-10-09-ip-assignment-or-lack-thereof/).
They released #DroneCI as free software accepting contributions with CLA to later make it proprietary. I think it's pretty clear to me what to expect of Gitness.
#gitness says - "“Now you have GitHub, GitLab, Bitbucket from Atlassian, but that’s really it. […] If you look at any of the git repos, whether it’s GitLab or GitHub or Bitbucket, they don’t have the true one source ethos around them anymore."
The main git blob for #inxi is now starting to morph, I've added a stripped down inxi-perl on #github, which has only pinxi, pinxi.1, and a basic READMe, and created the standalone #codeberg.org/smxi/pinxi repo for pinxi, and I just deleted the inxi-perl branch on codeberg git. This cleans everything up nicely, and also avoids flooding anyone's wall with commits during active #pinxi development, since only people who chose to follow or watch pinxi itself now will be tracking it.
codeberg 在年初发表的一篇博客中提到，面对如此巨大的用户量，可以增加一些资源如内存、CPU 来应对，但也要谨慎考虑增加的量以避免浪费珍贵的捐款
Codeberg 关于负载问题的串： https://social.anoxinon.de/@Codeberg/111080314296405187
Finalizing the #inxi migrations to #codeberg.org - split out into separate repos previous branches:
docs > repo inxi-docs
inxi-perl > repo pinxi, then deleted inxi-perl, and rebuilt it with just 2 files plus a basic readme for github.
tarballs > repo inxi-tarballs
This gets rid of a long standing difficulty for users, explaining how the svn to git converted repo worked, now it's all just one feature, one repo.
Estoy pensando en empezar un proyecto nuevo para programar algo de optimización multiobjetivo, pero no se donde alojarlo.
Voy a abandonar GitHub por quién hay detrás (Microsoft) y la movida que hubo con el tema de no respetar las licencias de los proyectos
He pensado en Codeberg aunque están teniendo problemas por la cantidad de gente y peticiones, lo que me echa un poco atrás.
También tengo la opción de GitLab, que lo tengo por ahí como mirror de mis repos antiguos de GitHub.
Migration of #smxi repos from #github to #codeberg.org are now completed. The #inxi migration was hard for their migration tool because the git data is very large and complicated, but after numerous tries, it finally got migrated.
I've now updated all the urls used, the self updaters, so that both github and codeberg versions will give users files that have the right data.
I'll probably stop mirroring at end of 2023, the github tokens last 90 days, which should be enough.
Migration of all the #smxi projects from #github to #codeberg is almost completed, #inxi is last, running the migration now. This is a tedious process, I opted to mirror via token for up to 90 days, then I'll just start removing the code from github where it makes sense, but I can't remove it all because of the updater tools that will in most cases be pointing at github, so they need to get at least the correct path version once, so will leave up the main code for a while.
#Codeberg currently suffers from high load, and we are having a hard time to stay ahead of the scaling issues.
If you mostly test our software or sync your small private projects, consider using https://next.forgejo.org for the time being.
- it runs on the same hardware and stack managed by Codeberg
- you can make use of the latest features
- better performance
- dogfooding helps the Forgejo developers (please report problems!)
- it reduces the load on Codeberg
Read on …
Doing initial tests of migrating all my #github repos to #codeberg.org - so far seems ok, codeberg docs are good, stuff works as expected. Since #inxi is most complicated, I will do that in a day or two, unless I just do it. Mirroring seems to work ok, but objectively, since it's based on a github token that expires, it's not a long term solution, so I'd rather just move the repos and call it done long term, but short term, mirroring will help packagers etc adjust.
Can anyone give any feedback based on firsthand experience on switching from #github to #codeberg.org ? I have always disliked github, but some of their most recent nonsense re their attempt to make it into a social media site, and of course, their blatant theft of copyleft code to make their copilot tool makes me ready to dump github.
I think I would miss github for maybe a few milliseconds, except maybe the much larger userbase, but objectively, I don't support anything about github or MS.
Just signed up at #Codeberg
What a breeze!
Username, email. password, and captcha.
That is all.
No 9000 questions from color of my pants to spell my late uncle used to to open time portals, from my country to my religion, etc etc.
I feel this is become a new trend, to simplify sign up process and "user profiles" at websites, for sake of simplicity and privacy.
#coding #repositories #softwaredevelopment
I made a #Codeberg account. Not much is there yet but I'm working on migrating stuff there. Issue titles have a length limit so I also have to copy over the text for issues with long titles into the top of the body.
Is #Codeberg having issues for anyone else? It's being extremely slow for me.
Is anyone else having trouble viewing #Codeberg issues while logged in? I'm getting 500 Internal Server Errors for some reason and I don't understand why
finally made a #codeberg, planning on migrating most of my code to there instead of on github
Read what happened during the summer on our blog: https://blog.codeberg.org/letter-from-codeberg-september-2023.html
Get Android App Updates Directly From the Source.
Obtainium allows you to install and update Open-Source Apps directly from their releases pages, and receive notifications when new releases are made available.
What am I doing? Why, voting to help decide @Codeberg policy as a member.
(Wait a minute, you can’t do that on GitHub? How odd… sounds a bit autocratic to me…) ;)
Seriously, though, check out https://codeberg.org – they’re doing everything right.
There are alternatives and if we want them to survive, we must support them.
@jens #codeberg pages works, but it doesn't look good on the security headers side anymore:
The headers I would like to get set:
The "_headers" file is supported by Cloudflare pages. I suppose it's still better to host on Codeberg pages without security headers than on Cloudflare pages with those.
hamblogs.club has now a new URL: https://blogs.radio
The old URL will forward to the new one.
This OPML file will always (with some delay) reflect what you see on https://blogs.radio
If you want to use your own RSS reader and it supports dynamic OPML (like FreshRSS), you can link it to the OPML file in my git repo and it will always be up to date.
After you copied all your repos, gists and other content from GitHub to #codeberg, which of the following would you do?
Below options allow only a limited number of characters. Thus, "point" means "point to Codeberg".
The following lists only repo content as examples for shortness sake.
You can read the changelog here:
Source code available on #sourcehut
Source code :
Having decided on the license, I've put the code up as it s now on #Codeberg
You can test it locally only so far, but it's a start.
The downside is that in the coming days I'll be slowly gearing up for work again, so I'll have less time to dedicate to it.
Hey everyone, I could use some input on this project / issue.
What would make this most useful to you? Do you have anything to add?
Issues and PRs welcome!
Thanks 💜 :ablobcatheart: 💜
You feel offended or disturbed? Getting rid of them is just one button away.
Please be reminded: If the users are likely also a problem for other users, save them the trouble and report them to firstname.lastname@example.org or by mentioning @moderation in an issue.
Now I have basic CI working, I've moved my project default origin to #Codeberg. I'll keep a mirror on Github and all my work stuff and old projects there, but Codeberg looks like a good home for new side projects.
So figured out the issue with postgres in #codeberg CI: if your service is named "database" your host will be called "database". D'oh!
i.e. just make sure to set the correct environment variables before running tests.
In case anyone else wants to run a #django CI pipeline in Woodpecker, here is my config:
Next thing to get working: unable to get postgres service to talk to my Python instance, using same image/env vars as with my local docker setup. Do I need to configure network as well? Where? How?
Again, very little in the way of documentation or examples to work with, this stuff feels very alpha, which is to be expected. #codeberg
So....got access to Woodpecker CI for my #codeberg repo, added .woodpecker-ci.yml file...but no Actions tab, no idea how to proceed or what else is needed 🤷
I'm working on getting Magpie Market set up on Open Collective, and stars would help with the approval process.
Please boost 🙂
The next release of Docsify-This will include several accessibility improvements, including better contrast, removal of empty links, and better labeling of various form elements.
Docsify-This might just be the quickest way to go from online #Markdown files to simple web pages! Copy the URL of a #GitHub Markdown file (or #Codeberg, or any raw Markdown file), head over to https://Docsify-This.net and paste that URL into the Web Page Builder and tap 'Publish as a Standalone Web Page' button🚀
Is autism self-diagnosis valid? Yep. 💜
Hey all, after reading dozens of research papers, and meta-analyses, and living through it, I made a thing!
I'd love it if you'd check it out! 🥰
Update: I've added *a lot* of new stuff to the project.
#Forgejo 1.20 is released. While we are porting some Codeberg changes and testing the migration, you can already experience the full potential at https://next.forgejo.org - hosted on Codeberg's infrastructure.
Join with your Codeberg account, let your team test-drive the new features, and report the problems you find before other #Codeberg usres experience them.
Read more about Forgejo v1.20 on https://forgejo.org/2023-07-release-v1/
📝 Blog post: I have published post about my migration to @Codeberg@social.anoxinon.de, it features guide on setting up redirect from GitHub and extended guide on setting up Codeberg pages with #jekyll
Edit: I promise this is the last edit :P
That and/or do a #Fediverse / #IndieWeb approach and have people publish their issues and pull requests on their own sites / instances and then notify the upstream repository about that. See eg: https://indieweb.org/issue
Is #Codeberg doing any of that?
Somewhat related, all public thi.ng projects are also archived at @swheritage: