I want to move my GitHub repositories to #CodeBerg and my question is, github seems to have a robust terminal/Cli program. I tried to register for a codeberg account, but they’re accessibility solution for getting around the captcha is to send them an email with registration details. Has anyone else done this? And if you have, and if you got an account, what is their terminal support like on windows?
4 new blog posts in April. Seems I'm getting better at sharing my long(er) form thoughts :)
The workflow I now have makes it really easy too. When I have a thread here that I think deserves a blog post, I copy the link to the first toot and paste it in https://mtr.wildeboer.net where I can get a #markdown dump that I can copy/paste in my editor and work on. My blog is #jekyll based and also uses Markdown, so it is easy to do :)
Ooh, @Codeberg just updated to @forgejo version 7 and… ta daa, the spurious warnings in the code listings for proper curly quotes and other correct – but sadly underutilised – typographical elements in comments and strings are gone!
TIL: When you use #codeberg and/or #forgejo, you can pimp your profile page by creating a repository called .profile (the dot is important) with a single file called README.md in it. Once done, the Markdown in said file will be shown as default content on your profile page. This is going to be fun! https://codeberg.org/jwildeboer
#CommunitySpotlight: Are you concerned about #BigTech, but still cannot fully escape them? Do you use (or just learned about) alternative frontends for popular services?
Check out #LibRedirect on #Codeberg, a browser addon which redirects many proprietary sites to alternative viewers.
I love @Codeberg, it is such a good alternative to capitalist scamforges.
I feel they won't betray me in any way.
They wont exploit my work for their own purpose in contradiction to my own good with crappy codding assistant algorithm such as Github Copilot.
Yet the quality of the service they provide is fairly comparable to those.
In other words, You get the benefits, without the risk of being screwed up, because they are an association you can participate (financially or with giving them some of your time), therefore the platform can partly belong to you.
Please consider to such alternatives and leave Gitlab or Github.
Gitlab's source-available proprietary model for "open core" is worse than keeping that code secret, because it serves to poison community implementation of similar features.
Hi everyone, we are doing user research for #Forgejo, the software that powers #Codeberg.
If you have 30 minutes in the next week, consider participating in the interviews to help us get insights in how you interact with Codeberg and how we can improve the experience for you.
It is an #OpenStreetMap based service to find #vegan (and #vegetarian) restaurants, in other words an open alternative to #HappyCow (except for the review functionality).
I got Codeberg’s CI to build and publish my website when I update the repo. I’m not sure if I’m bad at setting these things up or if it’s finicky and poorly documented…
Woodpecker needs a better way of setting up and handling ssh keys and config.
Since the original server at Mendel University of Brno is down and the authors didn’t react to emails, I re-published the “statistical charts” module for #ConTeXt / #MetaPost on #codeberg:
For those who were not able to attend the technical alignment meeting of the informal "Threadiverse Working Group", I have taken minutes during the meeting and are sharing them here.
Thank you to all those who attended, we will meet again next month! Follow myself or the WG category to be notified about additional developments.
Attendees
Angus McLeod
Julian Lam
Evan Prodromou
Aaron Grey
Rimu Atkinson
Erlend Sogge Heggen
Laurens Hof
Other participants are not listed as they are not mentioned in notes below, but there were ~20 participants.
Notes
Participant introductions
“Forasphere”/”Foraverse” vs “Threadiverse”
Both have a topic-like structure and so much of the technical structure is the same
More helpful to focus on the differences from microblogging as the de facto implementation of ActivityPub
No matter what name, it is mostly UI distinctions with some different handling based on nomenclature
Rimu brings up discussion regarding nomenclature; related document
“We don’t call things the same words”
Aaron posits that “Circles” could be a useful common term
Julian posits that end of the day no implementor here will likely consider changing their already-established terminology
Aaron proposes a goal for the group: determine a common set of terms to use in discussions going forward; a lingua franca
Evan proposes a goal to produce documentation that other forum (or reddit-like alternatives) can use to become compatible
Additional goal (added later): reaching out to other forum devs (who aren’t already in this WG or looking into AP). Additional outreach/engagement from other forum softwares.
Julian suggests that perhaps the FEP process would be a possible path forward
Mastodon’s microblogging concept leads to other implementations following suit
Coordinated effort to increase compatibility between threadiverse-type applications is attractive
Erlend wants to see better interop between threadiverse apps. Discourse to NodeBB, etc.
Angus states that we’ve reached half-way point and summarizes (see above)
Meeting focus shifts to debate re: FEP process or Task force under SocialCG
Julian proposes on behalf of Johannes Ernst (in absentia) that the WG be organized under the FediDevs umbrella
Evan proposes that the WG be an official task force under the SocialCG
W3C/ActivityPub has many task forces already, one for data portability, one for webfinger, one for testing, etc.
Differences between task force report and FEP:
Both similar documents
FEP has a more asynchronous process for clearing out objections, less cohesion than SocialCG
Discussions take place on SocialHub
Most FEPs individually authored
SocialCG reports collaboratively edited and put forth to W3C
Some questions re: FEP process
Evan answers: Anyone can propose, comments collected. After 6 months author can determine it finalized, but implementation varies. Many draft FEPs are dropped due to lack of interest or are hypothetical in nature.
Penar asks whether FEP or W3C report process is faster
Both are roughly equivalent, SocialCG reports are “a few months” to draft, and “a few months” to be accepted/finalized.
Aaron posits that SWICG (or SocialCG) is a better group since it eventually goes into a published W3C article
Aim towards convergence, consistent UI. Safe and usable user experience where the end-user has choice.
Laurens remarks on the increased level of cooperation that has not been often found in the fediverse, sees this as an opportunity to forge a path toward what we want instead of being bound by an FEP.
Angus motions that we join the SWICG as a task force
Motion carries with 12 ayes out of 16 present
Next meeting of SWICG 5 Apr 1pm Eastern; Angus and Julian to attend
3pm Eastern; meeting scheduled end, Evan and Erlend (and some others) drop out
What do we call the group “foraverse” “forasphere” “threadiverse”
Benti posits that it is weird to call ourselves representatives of the threadiverse as that distinction is reserved for Lemmy and nutomic is not present
Julian suggests that the term is not exclusive to Lemmy/kbin and asks to simply expand the definition to include Piefed, Discourse, NodeBB, Flarum, et al.
Additional back and forth regarding how and where to carry on discussions outside of monthly calls
Shared Google Doc sufficient for now, can explore additional options later
Julian posits that a federated option is ideal, acknowledges bias when suggesting that NodeBB be used. However, as it would be federated, where the discussions take place is mostly incidental.
A federated solution would be easiest way to reach fediverse developers.
Angus motions that we call ourselves the Threadiverse Working Group (or Task Force)
Motion carries with 9 ayes out of 13 present
Action Items
Angus or Julian to set up shared Google Doc for meeting/agenda prep for next meeting
Meaning its optional. By no means is it required to discuss there, if you don't want to. For any FEP a forum topic is created, but you can discuss anywhere else.
Each FEP document in the #codeberg repo gets an accompanying tracking issue that list all the places where discussion takes place.