Shakedown Social

2 posts2 participants0 posts today

Gitea🚀 We’re thrilled to announce the first release candidate (RC0) of Gitea 1.24 is now available! Check out what’s new and give it a try: 🔗 <a href="https://blog.gitea.com/release-of-1.24.0-rc0/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.gitea.com/release-of-1.24.0-rc0/</a> <a href="https://social.gitea.io/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> <a href="https://social.gitea.io/tags/Git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Git</a> <a href="https://social.gitea.io/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://social.gitea.io/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>

DocYeetAlso, if anyone is interested, I am dipping my toes heavily in federated networks, so if you want to interact over on <a href="https://mastodon.halis.io/tags/matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#matrix</a>, feel free :) Link is in my bio Soon to come, playing with a federated <a href="https://mastodon.halis.io/tags/gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitea</a>, <a href="https://mastodon.halis.io/tags/manyfold" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#manyfold</a>, <a href="https://mastodon.halis.io/tags/lemmy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lemmy</a> and more, so stay tuned !<a href="https://mastodon.halis.io/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://mastodon.halis.io/tags/federated" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#federated</a> <a href="https://mastodon.halis.io/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a>

Allanon 🇮🇹 :amiga:Dal momento che sono stufo delle minchiate dell bigtech a proposito dell'IA, ho deciso che tutto ciò che ho su <a href="https://mastodon.uno/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> sarà trasferito su <a href="https://mastodon.uno/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> , e questo grazie ai <a href="https://mastodon.uno/@devol" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@devol</a> che tengono in piedi *anche* questo servizio. Approfitto per mostrare una schermata di <a href="https://mastodon.uno/tags/LazyGit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LazyGit</a> , un client <a href="https://mastodon.uno/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a> fantastico!

Gitea🚀 Gitea 1.23.7 is out now!This important update includes essential fixes and improvements—upgrading ASAP is highly recommended for all users!👉 More details: <a href="https://blog.gitea.com/release-of-1.23.7/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.gitea.com/release-of-1.23.7/</a><a href="https://social.gitea.io/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> <a href="https://social.gitea.io/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://social.gitea.io/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a>

Kompot.si :unverified:🐌 Doing some research on 🤖 <a href="https://toot.si/tags/LLM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLM</a> <a href="https://toot.si/tags/bot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bot</a> protection for our selfhosted services. We had multiple downtimes per week for last few months mostly due to crawlers DDOSing our <a href="https://toot.si/tags/gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitea</a> service which brought the whole server to its knees (running more than 15 web services). It would be nice to hand out invoices for our devops work...Anyways <a href="https://toot.si/tags/askFedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#askFedi</a> what kind of protection would you recommend? We're opting for solution that's quick and easy to implement and lightweight.

Kevin Karhan :verified:<a href="https://fediscience.org/@seanfobbe" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@seanfobbe</a> personally I'd consider <a href="https://infosec.space/tags/gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitea</a> and <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfHosting</a>.<ul><li>As of now I abude <a href="https://infosec.space/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> as free, <a href="https://infosec.space/tags/DDoS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DDoS</a>-protected hosting and something <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a> burns money in.</li></ul>Once any of my projects would gain traction I'd move from there away.<ul><li>I just am not a huge fan of <a href="https://social.anoxinon.de/@Codeberg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Codeberg</a> even tho they are a better option.</li></ul>I jist move to either SelfHosting or nowhere...

Steffo :steffo:Hm... so this new AI thing from <a href="https://social.gitea.io/@gitea" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gitea</a> ... it's definitely interesting, and many people aren't reading, again.So, what did they do?They basically created an API client that is usable for LLMs - meaning that LLMs can now directly interact with Gitea. It's not integrated into the server by itself, and nobody is required to use it. Basically, it's HTTP ↔ MCP. It's like an API client for a programming language. So it's not a bad thing in itself.Also, this client by itself doesn't crawl other sites / uses data that was crawled from other sites, since it's literally just an API client.BUT (!) you have to use an existing LLM model using a client (e.g. Cursor) to be able to use this API client. Now that's the interesting part... I don't know if there's actually a good LLM that only learned from data that it was allowed to use. This means, that Gitea kind of promotes using LLMs that crawled people's sites without their permission.Sadly, the screenshots shown in the blog post by Gitea don't show what model they are using, so we can't tell if they are using a good or a bad model. (Though, I'm not sure if we specifically need to know that in this case.)Anyway, I'm always happy to see people switch to <a href="https://floss.social/@forgejo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@forgejo</a>. I, personally, used it almost since I started moving away from GitHub / -Lab and I love it. Sadly, I know a few people who can't yet move to Forgejo since they're using architectures that Forgejo doesn't build for docker yet.For those people who are still angry and "need to" be aggressive towards the devs: Calm down, maybe read my blog post that I made in collaboration with Finnley about outrage (<a href="https://steffo.blog/outrage-warps-reality/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://steffo.blog/outrage-warps-reality/</a>) and have a great day. Maybe go for a walk outside?Anyway, have a lovely day! :floofHeart: <a href="https://fellies.social/tags/gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitea</a> <a href="https://fellies.social/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> <a href="https://fellies.social/tags/ai" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ai</a> <a href="https://fellies.social/tags/llm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#llm</a>

lumpen 🍉 III <a href="https://social.gitea.io/@gitea" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gitea</a> It's a shame, I used to encourage people to use <a href="https://wanderingwires.net/tags/Gitea" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> but obvs it's just another AI slop farm run by rich out of touch leeches

Emma Loves ☕️Anyone done a <a href="https://orbital.horse/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> to <a href="https://orbital.horse/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> migration? Is the guide on the Forgejo site sufficient documentation?

M M ArifHi everyone, GitNex 8.0.0 is now out with numerous new features and UI refinements.- User activity heatmap on the profile - Dependencies for issues and prs - Tracked time for issues and prs - Search within files - Filter issues by labels - Filter issues where I am mentioned - and more...It's time to update! 🎉 Release notes: <a href="https://codeberg.org/gitnex/GitNex/releases" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/gitnex/GitNex/releases</a><a href="https://mastodon.social/tags/gitnex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitnex</a> <a href="https://mastodon.social/tags/gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitea</a> <a href="https://mastodon.social/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> <a href="https://mastodon.social/tags/codeberg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#codeberg</a> <a href="https://mastodon.social/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android</a> <a href="https://mastodon.social/tags/app" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#app</a> <a href="https://mastodon.social/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a>

rvstaverenLast weekend I got the <a href="https://mastodon.online/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> act runner working on <a href="https://mastodon.online/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>. Nice to see how it is compatible with GitHub actions. Quite surprised to learn you a) need to do the checkout yourself (uses: actions/checkout@v4) and b) this needs a nodejs runtime which I think is quite heavy despite the functionality it offers… 🤔. I also learned that these actions are sourced default from <a href="https://mastodon.online/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a>, and that can lead to <a href="https://mastodon.online/tags/infosecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infosecurity</a> issues 🙄😬<a href="https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised</a>BCP seems to pin these actions to a commit

Jason CosperReally love how easy it is to import repos into <a href="https://simian.rodeo/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a>.

Fabio ManganielloIf you run a <a class="hashtag" href="https://manganiello.social/tag/drone" rel="nofollow noopener noreferrer" target="_blank">#Drone</a> CI server, set <code>DRONE_REGISTRATION_CLOSED=true</code> (and manually create users only when you really really trust someone).The CPU on my CI/CD server suddenly spiked to 100% today.A closer look found some users who had registered on <a href="http://git.platypush.tech" rel="nofollow noopener noreferrer" target="_blank">git.platypush.tech</a> and on the CI/CD server and created a repo with a .drone.yml, a .gitlab-ci.yml and some scripts with base64-encoded commands.The repo also contains a <code>deepCC.ipynb</code> Jupyter notebook that downloads some training data from S3 and uses Tensorflow to train a model, and then uses the <code>deepCC</code> binary to do something with that model.The repository also has a configure script with base64-encoded commands that seem to configure a miner (the wallet ID is R9WpFbvkb6dep6bfLdbpcyz3LpMeikUL6W and the coin is VRSC, if anyone is interested in investigating further).The <code>deepCC</code> binary is itself quite big (~50 MB), and a look at the <code>setup</code> script reveals that it’s actually a .tar.gz archive with a larger binary inside.A quick run of <code>strings</code> on the binary confirms that it’s actually a miner - it connects to <code>eu1-etc.ethermine.org</code> and it also has a bunch of CUDA bindings to run on GPUs.I still don’t get what’s the point of the Jupyter notebook that trains a model and passes it to this miner, but if you feared the day of the arrival of the zombie Docker containers that exhaust system resources by mining cryptocrap AND training AI models, well, I’m afraid to inform you that that day has come.If you are a <a class="hashtag" href="https://manganiello.social/tag/gitea" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> / <a class="hashtag" href="https://manganiello.social/tag/forgejo" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> admin, take a look at the users and repos created in the past couple of weeks. Check in particular if any recently registered users have created a repo named <code>deepcc-v</code>.The most likely authors are users named <code>farzanfarid16</code> and <code>zurizoey0</code>.A quick search confirms that both these users are registered on <a class="hashtag" href="https://manganiello.social/tag/gitea" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> too and have already created the incriminated repo:<ul><li><a href="https://gitea.com/farzanfarid16/deepcc-v" rel="nofollow noopener noreferrer" target="_blank">https://gitea.com/farzanfarid16/deepcc-v</a></li><li><a href="https://gitea.com/zurizoey0/deepcc-v" rel="nofollow noopener noreferrer" target="_blank">https://gitea.com/zurizoey0/deepcc-v</a></li></ul>And if you are a Drone CI or <a class="hashtag" href="https://manganiello.social/tag/gitlab" rel="nofollow noopener noreferrer" target="_blank">#Gitlab</a> admin, check if any of these users have also started CI/CD pipelines connected to that repo.For now, disabling the execution of CI/CD pipelines unless a user has been explicitly authorized is the best idea that comes to my mind.

Yehor 🇺🇦Why most people choose <a href="https://techhub.social/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> over <a href="https://techhub.social/tags/gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitea</a>? <a href="https://techhub.social/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://techhub.social/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> <a href="https://techhub.social/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a> <a href="https://techhub.social/tags/selfhost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhost</a>

Kevin Karhan :verified:Anyone know someone at <a href="https://infosec.space/tags/JetBrains" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JetBrains</a> to report a <a href="https://infosec.space/tags/PyCharm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PyCharm</a> <a href="https://infosec.space/tags/issue" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#issue</a> to? Basically it's a <a href="https://infosec.space/tags/softlocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#softlocking</a> that happens on the <a href="https://infosec.space/tags/snap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#snap</a> version of <a href="https://infosec.space/tags/PyCharmCommunity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PyCharmCommunity</a> / <a href="https://infosec.space/tags/PyCharmCE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PyCharmCE</a> that makes it somehow half-forget <a href="https://infosec.space/tags/credentials" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#credentials</a> like <a href="https://infosec.space/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a>, <a href="https://infosec.space/tags/Gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitlab</a>, <a href="https://infosec.space/tags/Codeberg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Codeberg</a>, <a href="https://infosec.space/tags/BitBucket" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BitBucket</a>, <a href="https://infosec.space/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a>, <a href="https://infosec.space/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a> etc. and not allowing to just delete & re-add them as the settings saving just becomes unresponsive.<ul><li>Mind you this isn't with like dozens of accounts - just one on each platform - and it's not easily fixable (or at least not in a good way by manually yeeting the <a href="https://infosec.space/tags/XML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XML</a> files for said logins from <code>$HOME/.config/PyCharmCE****/...</code> and randomly coming back after a few days or weeks.</li></ul>Whether this also conflicts with <a href="https://infosec.space/tags/SettingsSync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SettingsSync</a> which should only sync <a href="https://infosec.space/tags/configs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#configs</a>, not <a href="https://infosec.space/tags/credentials" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#credentials</a> (and AFAICT doesn't!) is also a question I can't confidently answer.<ul><li>Needless to say it's really annoying, espechally at work and is the main reason I've not considered paying for JetBrains' products as of now! </li></ul><a href="https://infosec.space/tags/plzfix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#plzfix</a> <a href="https://infosec.space/tags/Development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Development</a> <a href="https://infosec.space/tags/Software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Software</a> <a href="https://infosec.space/tags/IDE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IDE</a>

AlexNice bug in <a href="https://swiss.social/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> / <a href="https://swiss.social/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a>. If I create one more PR, there will be no PRs left.. 🤔 <a href="https://swiss.social/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devops</a> <a href="https://swiss.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://swiss.social/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a>

AlexShout-out to ThetaDev for his <a href="https://swiss.social/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> action (also works on <a href="https://swiss.social/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a>) that allows you to run <a href="https://swiss.social/tags/Kaniko" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kaniko</a> inside an action, completely unprivileged and without Docker! 🚀 <a href="https://code.thetadev.de/actions/kaniko" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://code.thetadev.de/actions/kaniko</a> <a href="https://swiss.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a>

smallsolarI feel a little bit foolish, I run a solar powered server which provides a <a href="https://techhub.social/tags/mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastodon</a> instance, a <a href="https://techhub.social/tags/bittorrent" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bittorrent</a> client and a <a href="https://techhub.social/tags/gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitea</a> server. During the winter it's only online for fairly short periods of time depending on the sun. Ive got some markdown files on the gitea server which I edit using the website, I therefore have to wait for the sunshine before i can do this, it can be a little annoying if the timing doesn't line up with my day schedule.I have only just clicked that it's <a href="https://techhub.social/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a> so I can clone to my laptop, edit to my hearts content and then push it back when the server is online. Honestly completely forgot this key function. Git (or other similar systems) are ideal for a <a href="https://techhub.social/tags/solarpunk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#solarpunk</a> <a href="https://techhub.social/tags/frugalcomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#frugalcomputing</a> approach, the server doesn't need to be online all day as it's not actually doing much in between, I can work separately. I wonder if this model could be applied to our parts of our day to day work

Markus Lindenberg<a href="https://chaos.social/tags/Gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitea</a> vs. <a href="https://chaos.social/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> puzzles me a bit. From the outside, this looks much like a people don't like each other problem. Gitea is still alive & OSS. Forgejo has 2k+ more commits, looks like that's mostly because they update dependencies like crazy.I've got them both installed and they still look/feel/work exactly the same.

:projetstodon: ShalienI know it will only bring pain and suffering but <a href="https://mastodon.projetretro.io/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#foss</a> <a href="https://mastodon.projetretro.io/tags/dev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dev</a>, I see a log of people recommending <a href="https://mastodon.projetretro.io/tags/gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitea</a> / <a href="https://mastodon.projetretro.io/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> . Why not also <a href="https://mastodon.projetretro.io/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a> and why are they evil ?

Recent searches

Search options

Administered by:

Server stats:

#gitea