🔥1
🔥2
❤2
🔥3
❤5
❤2👍2🔥1🎉1
👍1
Telethon's repository will soon move from GitHub to Codeberg
I intend to do so before the end of this month. But if you have concerns, raise them now and I will try to answer.
All other repositories under both the Lonami user and LonamiWebs organization have already been moved and archived, with any issues and PRs they had closed with a comment directing to their new home (with exceptions for repositories that were archived and deprecated projects.)
Because these projects are not as popular as Telethon, I have decided to not copy over any issues or pull requests. I have a local copy of them that I intend to keep private in case I need to reference them after the GitHub repositories are taken down. I don't intend to repost this data online, with the hope of reducing the likeliness the original authors would take issue with it. Issues and PRs that were still valid on the now-archived repositories should be reopened in their new home.
I am currently undecided on whether all of Telethon's issues and pull requests should be ported over on the migration. I am currently leaning towards no, so that authors retain full ownership of their original comments. Because a proper migration would mean the comments would be reposted in a manner they can't control. But I may be persuaded on this.
I intend to keep the GitHub archives readonly for some time. Probably at least a month for my less-known projects, and significantly longer (or indefinitely) for those I consider important enough. I also intend to keep my GitHub account active, because unfortunately, most open source projects live there, and raising issues or submitting changes requires an account.
As for why Codeberg and not other Git forges or even self-hosting: this was one of the ones I had heard the most, and I align with their current views. Should it occur that things don't work out, I'll now have experience moving between forges.
I'm growing tired of GitHub and the direction it's going. While I don't have to deal with its interface as much for my open source work (responding to issues and reviewing changes occasionally), I strongly dislike how it's shoving LLM in every place it can. And I have strong moral concerns, shared by many others, on the current generation of LLMs, how they are trained, and how they are used. You don't need to look far to find the damage they are causing and how many are trying to defend against it (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, …)
I frankly should have done this way sooner. People have been writing that Free Software Needs Free Tools for longer than a decade. There are others who can better put into words How Github monopoly is destroying the open source ecosystem than I can.
The best time to migrate is in the past. The second best time is now. I hope this inspires others to also Give Up GitHub!
I intend to do so before the end of this month. But if you have concerns, raise them now and I will try to answer.
All other repositories under both the Lonami user and LonamiWebs organization have already been moved and archived, with any issues and PRs they had closed with a comment directing to their new home (with exceptions for repositories that were archived and deprecated projects.)
Because these projects are not as popular as Telethon, I have decided to not copy over any issues or pull requests. I have a local copy of them that I intend to keep private in case I need to reference them after the GitHub repositories are taken down. I don't intend to repost this data online, with the hope of reducing the likeliness the original authors would take issue with it. Issues and PRs that were still valid on the now-archived repositories should be reopened in their new home.
I am currently undecided on whether all of Telethon's issues and pull requests should be ported over on the migration. I am currently leaning towards no, so that authors retain full ownership of their original comments. Because a proper migration would mean the comments would be reposted in a manner they can't control. But I may be persuaded on this.
I intend to keep the GitHub archives readonly for some time. Probably at least a month for my less-known projects, and significantly longer (or indefinitely) for those I consider important enough. I also intend to keep my GitHub account active, because unfortunately, most open source projects live there, and raising issues or submitting changes requires an account.
As for why Codeberg and not other Git forges or even self-hosting: this was one of the ones I had heard the most, and I align with their current views. Should it occur that things don't work out, I'll now have experience moving between forges.
I'm growing tired of GitHub and the direction it's going. While I don't have to deal with its interface as much for my open source work (responding to issues and reviewing changes occasionally), I strongly dislike how it's shoving LLM in every place it can. And I have strong moral concerns, shared by many others, on the current generation of LLMs, how they are trained, and how they are used. You don't need to look far to find the damage they are causing and how many are trying to defend against it (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, …)
I frankly should have done this way sooner. People have been writing that Free Software Needs Free Tools for longer than a decade. There are others who can better put into words How Github monopoly is destroying the open source ecosystem than I can.
The best time to migrate is in the past. The second best time is now. I hope this inspires others to also Give Up GitHub!
Codeberg.org
Codeberg is a non-profit community-led organization that aims to help free and open source projects prosper by giving them a safe and friendly home.
👍18😐12❤9👎8🎉4
Telethon Updates pinned «Telethon's repository will soon move from GitHub to Codeberg I intend to do so before the end of this month. But if you have concerns, raise them now and I will try to answer. All other repositories under both the Lonami user and LonamiWebs organization…»
❤2
All remaining previously-open issues and PRs have been closed with a short comment directing to the repository's new home.
The project now lives, and will continue to receive updates, in https://codeberg.org/Lonami/Telethon
Still pending is:
• looking into moving the API reference site (https://tl.telethon.dev) and sister site to view layer differences (https://diff.telethon.dev) elsewhere,
• cutting a new release with updated project links to PyPi,
• updating the bot to look at Codeberg to post about new commits here
As the post didn't receive that much attention, nobody really proposed to migrate issues or PRs, so it will start from a clean slate.
The GitHub project will remain as read-only for at least a year (…unless something catastrophic happens to GitHub, but that would be outside my control), and my current feeling is it would stay that way indefinitely (whether the history-until-now stays after a year is an open question).
Thanks to those that have been supportive, and sorry for the hassle this might cause.
The project now lives, and will continue to receive updates, in https://codeberg.org/Lonami/Telethon
Still pending is:
• looking into moving the API reference site (https://tl.telethon.dev) and sister site to view layer differences (https://diff.telethon.dev) elsewhere,
• cutting a new release with updated project links to PyPi,
• updating the bot to look at Codeberg to post about new commits here
As the post didn't receive that much attention, nobody really proposed to migrate issues or PRs, so it will start from a clean slate.
The GitHub project will remain as read-only for at least a year (…unless something catastrophic happens to GitHub, but that would be outside my control), and my current feeling is it would stay that way indefinitely (whether the history-until-now stays after a year is an open question).
Thanks to those that have been supportive, and sorry for the hassle this might cause.
Codeberg.org
Telethon
Pure Python 3 MTProto API Telegram client library, for bots too!
👎21❤16🎉9👍5😁1
👍1
❤4🔥2🎉1
Codeberg's atom feed does not seem to include the author (only the committer, which is always me), so unfortunately that part will no longer be included in the automatic messages about commits posted here.
The response also does not appear to include an ETag or Last-Modified header, so the polling frequency has also been reduced.
The response also does not appear to include an ETag or Last-Modified header, so the polling frequency has also been reduced.
😐5❤1