#GitHub

[Release notes from capsicum]v2.2.0
https://github.com/pooza/capsicum/releases/tag/v2.2.0

#GitHub #capsicum #precure_fun #delmulin

capsicum 2.1にて、ナウプレのアートワークに対応しています。

https://github.com/pooza/capsicum/issues/1133

macOS版は、2.1の審査がまだ通っていません。一両日ぐらいだと思います。

TheDesk側でもアートワーク機能の改善が進み、特にお困りでもない様ですが、よかったらこちらもお試しください。
一応この改善も、とねぢさんが利用することを想定して前倒しした対応ではありますw
@toneji

#GitHub #capsicum

https://github.com/pooza/tomato-shrieker/issues/1673
次の次のトマトさん（4.15）に、PieFed対応を起票しました。

@karasu_sue

#GitHub

[Release notes from capsicum]v2.1.0
https://github.com/pooza/capsicum/releases/tag/v2.1.0

#GitHub #capsicum #precure_fun #delmulin

Software developers, the #GNU Project urges you to avoid hosting your repositories on #GitHub: https://u.fsf.org/4ci #FreeSoftware

@autiomaa Github stars have become completely commercialized already years ago. (IIRC between 2019-21) I remember getting numerous emails about purchasing stars and forks to help my projects' visibility/credibility/importance, the same way some people are purchasing fake followers/engagement on IG/Twitter etc.

This all coincided with other major disappointing reveals around open source from former peers. Seeing how FLOSS culture has been co-opted by (not just new) people who share nothing of the same ideals or social contracts and are using opensource purely as mechanism for quick personal advancement/enrichment (e.g. setting up and heavily promoting short-lived projects just to improve their big tech job interview chances) was one of the biggest disappointments of my life, and one from which I'm still only slowly recovering...

#OpenSource #GitHub

[Release notes from capsicum]v2.0.0
https://github.com/pooza/capsicum/releases/tag/v2.0.0

#GitHub #capsicum #precure_fun #delmulin

@evan @evanprodromou @jdlh @Edent

PS2. Noticing that #Github opengraph preview of an issue is non-descriptive, does not show the issue title, I can point anyone interested to @forgejo which does a better job here. Example:

https://codeberg.org/fediverse/delightful-fediverse-experience/issues/130

@sethmlarson Also:

Rate limits for private vulnerability reports

https://github.blog/changelog/2026-10-01-rate-limits-for-private-vulnerability-reports/

Structured forms for private vulnerability reports

https://github.blog/changelog/2026-10-01-structured-forms-for-private-vulnerability-reports/

#GitHub #security

@sethmlarson Also:

Rate limits for private vulnerability reports

https://github.blog/changelog/2026-10-01-rate-limits-for-private-vulnerability-reports/

Structured forms for private vulnerability reports

https://github.blog/changelog/2026-10-01-structured-forms-for-private-vulnerability-reports/

#GitHub #security

Opt-in dist-tag permissions for npm trusted publishing https://github.blog/changelog/2026-09-30-opt-in-dist-tag-permissions-for-npm-trusted-publishing
#github

Opt-in dist-tag permissions for npm trusted publishing https://github.blog/changelog/2026-09-30-opt-in-dist-tag-permissions-for-npm-trusted-publishing
#github

GitHub Security Advisories added a new feature: "Confidential Comments"! 🥳

This is both an awesome feature in general (no more having multiple channels for each report 🎉) and is hopefully a sign that more development on this critical feature will be coming soon.

#security #github

If your membership to an open source project isn't public on #GitHub or #Codeberg, it's because

「Microsoft Learn」の公開ドキュメントリポジトリ、多くが年内に終了へ／廃止対象では「GitHub」経由の修正提案ができなくなる
https://forest.watch.impress.co.jp/docs/news/2143945.html

#forest_watch_impress #Microsoft #GitHub #Microsoft_Learn #プログラミング #Webサービス

「Microsoft Learn」の公開ドキュメントリポジトリ、多くが年内に終了へ／廃止対象では「GitHub」経由の修正提案ができなくなる
https://forest.watch.impress.co.jp/docs/news/2143945.html

#forest_watch_impress #Microsoft #GitHub #Microsoft_Learn #プログラミング #Webサービス

📢 Two of @w3c’s most commonly used IRC bots, RRSAgent and Zakim, are now open source. These bots have assisted over 60,000 meetings at W3C over the past 25 years! 😊🎉

▶️ https://www.w3.org/blog/2026/w3c-irc-bots-now-open-source/ - by @gerald

Zakim is for agenda and queue management and RRSAgent for recording minutes. Their code and issue trackers are on #GitHub:
- https://github.com/w3c/zakim
- https://github.com/w3c/rrsagent
#OpenSource

👇From a T-shirt designed by @karlcow to thank W3C group chairs back in 2008!

📢 Two of @w3c’s most commonly used IRC bots, RRSAgent and Zakim, are now open source. These bots have assisted over 60,000 meetings at W3C over the past 25 years! 😊🎉

▶️ https://www.w3.org/blog/2026/w3c-irc-bots-now-open-source/ - by @gerald

Zakim is for agenda and queue management and RRSAgent for recording minutes. Their code and issue trackers are on #GitHub:
- https://github.com/w3c/zakim
- https://github.com/w3c/rrsagent
#OpenSource

👇From a T-shirt designed by @karlcow to thank W3C group chairs back in 2008!

📢 Two of @w3c’s most commonly used IRC bots, RRSAgent and Zakim, are now open source. These bots have assisted over 60,000 meetings at W3C over the past 25 years! 😊🎉

▶️ https://www.w3.org/blog/2026/w3c-irc-bots-now-open-source/ - by @gerald

Zakim is for agenda and queue management and RRSAgent for recording minutes. Their code and issue trackers are on #GitHub:
- https://github.com/w3c/zakim
- https://github.com/w3c/rrsagent
#OpenSource

👇From a T-shirt designed by @karlcow to thank W3C group chairs back in 2008!

Misskey 2026.9.1を可及的速やかに適用せよとのことなので、帰宅後にやりますね。
深夜になるとは思います…

#delmulin #GitHub

Misskey 2026.9.1を可及的速やかに適用せよとのことなので、帰宅後にやりますね。
深夜になるとは思います…

#delmulin #GitHub

@karasu_sue @capsicum

https://github.com/pooza/capsicum/issues/1167

起票済み。
基本設計寄りなので、性格的に2.0にふさわしいと思いました。

#GitHub #capsicum

[Release notes from capsicum]v1.66.0
https://github.com/pooza/capsicum/releases/tag/v1.66.0

#GitHub #capsicum #precure_fun #delmulin

FYI: if you participated in a project (made issues/PRs/comments) that has moved from github to codeberg (or to any forgejo instance), you can sign into codeberg using github, and then link your codeberg with your github, so that migrated issues/PRs/comments are linked to your codeberg account (instead of github) on codeberg!

go to settings > security > scroll to linked accounts to link your github/gitlab to codeberg, and then link your github account

you can unlink after and codeberg will keep it attributed to your codeberg, but it won't apply automatically to future project migrations

(this advice applies to projects previously on github, which migrated using codeberg/forgejo's migration feature which copies issues/PRs over)

#codeberg #github

[Release notes from capsicum]v1.65.0
https://github.com/pooza/capsicum/releases/tag/v1.65.0

#GitHub #capsicum #precure_fun #delmulin

@toneji
https://github.com/pooza/capsicum/issues/1133

課題として起票しました。

#GitHub #capsicum

Good #IPv6 morning to #GitHub (with a little help from #FOSDEM)

% host github-debug.com
github-debug.com has address 140.82.121.2
github-debug.com has IPv6 address 2606:50c0:c0de:a00::390
%

Getting there..

スパムユーザー登録、ウチも来てた。
今週の平日は多忙で、いま気づいた。

一旦登録は閉じている。SendGridなどへの実害はなし。
元々「意気込み」入力は必須にしてるが、今回はそれでは対策にならない。

https://github.com/pooza/mastodon/issues/970
https://github.com/pooza/mastodon/issues/971

#GitHub

[Release notes from capsicum]v1.64.0
https://github.com/pooza/capsicum/releases/tag/v1.64.0

#GitHub #capsicum #precure_fun #delmulin

GitHub's first IPv6 block is now live on the Azure geolocation page.

https://www.microsoft.com/en-ie/download/details.aspx?id=53601

@RichiH

#IPv6 #Github

GitHub's first IPv6 block is now live on the Azure geolocation page.

https://www.microsoft.com/en-ie/download/details.aspx?id=53601

@RichiH

#IPv6 #Github

Habt ihr schon von @Codeberg gehört? Codeberg ist ein Git Hosting Service auf der Basis von @forgejo und wird von einem gemeinnützigen Verein betrieben. Das fanden wir so interessant, dass wir da mal eine Folge drüber gemacht haben. Spoiler: Ist ganz geil, aber nicht für jeden was! Aber hört besser selbst rein: https://autoweirdfm.podigee.io/138-codeberg

#codeberg #forgejo #git #github #gitlab

@baldur @u0421793

I think its not as much that #developers are gatekeeping, but more that work processes don't integrate well, or at all. To the benefit of the devs, who deliver the software at the end of the pipeline.

At the start of my career I worked at the largest Print company in Europe (now bankrupt) and we created several award-winning dynamic websites. At the time #UX wasn't a thing, but Interaction Design was and it was leading. It was also a time when we didn't have 'agile', and didn't have #Github where everything is either an Issue or a PR. There were waterfall processes, and on the agile side you later had things like #RUP (Rational Unified Process). These acknowledged specifally different IT roles and different stages in the overall development lifecycle.

For Social experience design, #SX, I got inspired by RUP when defining the #FSDL (the Free software development lifecycle, or Fediverse solution delivery lifecycle, depending on context). See:

https://coding.social/blog/reimagine-social/#free-software-development-lifecycle

Misskey 2026.9.0が出たようです。
珍しく「可及的速やか」などと言われてますので、可能ならば今夜適用してしまいます。

#delmulin #GitHub

Misskey 2026.9.0が出たようです。
珍しく「可及的速やか」などと言われてますので、可能ならば今夜適用してしまいます。

#delmulin #GitHub

New API endpoint provides privacy-safe star history data https://github.blog/changelog/2026-09-04-new-api-endpoint-provides-privacy-safe-star-history-data
#github

New API endpoint provides privacy-safe star history data https://github.blog/changelog/2026-09-04-new-api-endpoint-provides-privacy-safe-star-history-data
#github

[Release notes from capsicum]v1.63.0
https://github.com/pooza/capsicum/releases/tag/v1.63.0

#GitHub #capsicum #precure_fun #delmulin

Here's how to join the cool testers' club! 😎

https://hugovk.dev/blog/2026/help-test-python-315/

#Python #Python315 #GitHub #GitHubActions

Here's how to join the cool testers' club! 😎

https://hugovk.dev/blog/2026/help-test-python-315/

#Python #Python315 #GitHub #GitHubActions

Here's how to join the cool testers' club! 😎

https://hugovk.dev/blog/2026/help-test-python-315/

#Python #Python315 #GitHub #GitHubActions

I'm quoted in #FastCompany re: #Nvidia's likely acquisition of 🤗Inc:

https://www.fastcompany.com/91597304/nvidias-hugging-face-deal-could-reshape-the-open-ai-ecosystem

However, #disturbing that #OSI says that #HuggingFace is currently a “neutral platform”.

Sadly, #OpenSource Initiative (even after #Microsoft's acquisition) considers #GitHub a “thought leader”¹ in framing OSI's LLM-gen-AI policy. But I still hope against hope OSI would drop their decades-long position that “we ❤️ companies that proprietarize non-copyleft #FOSS”. 😩

¹ https://web.archive.org/web/20220901212914/https://deepdive.opensource.org/

#AI #LLM

I'm quoted in #FastCompany re: #Nvidia's likely acquisition of 🤗Inc:

https://www.fastcompany.com/91597304/nvidias-hugging-face-deal-could-reshape-the-open-ai-ecosystem

However, #disturbing that #OSI says that #HuggingFace is currently a “neutral platform”.

Sadly, #OpenSource Initiative (even after #Microsoft's acquisition) considers #GitHub a “thought leader”¹ in framing OSI's LLM-gen-AI policy. But I still hope against hope OSI would drop their decades-long position that “we ❤️ companies that proprietarize non-copyleft #FOSS”. 😩

¹ https://web.archive.org/web/20220901212914/https://deepdive.opensource.org/

#AI #LLM

Ach wie schön, man kommt aus dem Urlaub zurück und stellt fest, das der gesamte #Github Account gesperrt ist.

Repositories, wie z.B. https://github.com/jedie/django-reversion-compare sind offline und zeigen nur ein 404...

Alles weg, nur 404. (Hab natürlich backups, lokale Klone und automatisierte Klone in einem privaten #Forgejo )

Hab nicht einmal eine EMail bekommen, mit irgendeinem Hinweis.

@github #GitHubSuspendedMe #GiveUpGitHub

Most CVE APIs hide their data lag. We ship it. Every response returns pending_fields — exactly which fields NVD hasn't processed on that CVE yet. Every plan. NVD + KEV + EPSS + exploit tracking + detection rules, one call.
10 real CVEs, no signup: https://www.valtersit.com/cve/pricing/ #cve #cybersecurity #infosec #devsecops #linux #python #ukraine #api #git #github #gitlab #development #sysadmin #devops #security #hackers

One more repository out of GitHub to Codeberg

https://codeberg.org/pylapp/SmoothClicker

#GiveUpGitHub #GitHub #Codeberg #Android #autoclicker

今朝、2時間ちょっと調査した上での進捗です。
特定にまでは足りてないが、かなり確度の高い原因を特定しました。とても手こずりましたけどw

こちらがいま考えている理由は、プレビューカードの高さが、読み込みの進捗によって頻繁に変わることです。
プレビューカードは文字と画像を持ちうることもあり、高さが動的に変わる可能性があります。

https://github.com/pooza/capsicum/issues/1032
https://github.com/pooza/capsicum/issues/1033

Misskeyで、タイムラインにプレビューカードを表示する対応は割と新しめの更新です。
このときから頻繁に発生するようになったと考えられます。
https://github.com/pooza/capsicum/issues/772

併せて、文字だけのプレビューカードの幅が狭くなる問題も対応します。
（気づいてはいたが、そのうち直すつもりだった）

@capsicum@pf.korako.me

#delmulin #GitHub #capsicum

今朝、2時間ちょっと調査した上での進捗です。
特定にまでは足りてないが、かなり確度の高い原因を特定しました。とても手こずりましたけどw

こちらがいま考えている理由は、プレビューカードの高さが、読み込みの進捗によって頻繁に変わることです。
プレビューカードは文字と画像を持ちうることもあり、高さが動的に変わる可能性があります。

https://github.com/pooza/capsicum/issues/1032
https://github.com/pooza/capsicum/issues/1033

Misskeyで、タイムラインにプレビューカードを表示する対応は割と新しめの更新です。
このときから頻繁に発生するようになったと考えられます。
https://github.com/pooza/capsicum/issues/772

併せて、文字だけのプレビューカードの幅が狭くなる問題も対応します。
（気づいてはいたが、そのうち直すつもりだった）

@capsicum@pf.korako.me

#delmulin #GitHub #capsicum

📢 Fediverse-Sprechstunde: Was sind eigentlich „Issues“ – und warum gehen sie uns alle etwas an?

Ihr nutzt Friendica, Mastodon, Hubzilla, Sharkey oder eine andere Fediverse-Software und plötzlich funktioniert etwas nicht so, wie ihr es erwartet? 🤔

Oder ihr denkt euch bei einer Funktion:
„Das könnte man doch besser machen!“

Vielleicht habt ihr auch eine Idee, die ihr gern den Entwicklerinnen und Entwicklern mitteilen würdet.

Dann fällt früher oder später ein Begriff: „Mach doch ein Issue auf.“

Aber was bedeutet das eigentlich?
Was gehört in ein gutes Issue hinein? Wo erstelle ich es? Welche Informationen brauchen Entwickler, um einen Fehler nachvollziehen zu können? Und muss ich dafür überhaupt technische Kenntnisse haben?

Genau darum geht es bei unserer nächsten Fediverse-Sprechstunde:

📅 Montag, 31. August 2026
🕢 19:30 Uhr
💻 Online

🔎 Was sind Issues und wie erstelle ich welche?

Für dieses Thema konnten wir Jens (@qbi ) gewinnen. Einige von euch kennen ihn vielleicht bereits aus unserer Fediverse-Sprechstunde zum Thema BookWyrm.

Jens ist Administrator und Entwickler und kennt Issues nicht nur aus der Theorie, sondern aus der täglichen Praxis. Gemeinsam wollen wir uns anschauen, wie aus einem beobachteten Problem, einer Idee oder einem Verbesserungsvorschlag ein Issue wird, mit dem Entwickler auch wirklich etwas anfangen können.

Dabei geht es ausdrücklich nicht nur um Entwickler oder Administratoren!

Denn freie und offene Software lebt auch davon, dass diejenigen, die sie täglich benutzen, Rückmeldungen geben. Niemand kann jeden Fehler selbst entdecken und niemand kennt alle Wünsche und Probleme der Nutzerinnen und Nutzer.

Ein gut beschriebenes Issue kann deshalb ein kleiner, aber sehr wertvoller Beitrag zur Weiterentwicklung einer Software sein. 🌱

Und vielleicht nehmen wir dabei auch ein wenig die Scheu vor Plattformen wie GitHub oder Codeberg. 😉

Ihr müsst dafür keine Programmierer sein und keinen Quellcode verstehen. Neugier und Fragen reichen völlig aus.

💬 Was ist überhaupt ein Issue?
🐞 Wie melde ich einen Fehler sinnvoll?
💡 Kann ich auch Ideen und Verbesserungsvorschläge einreichen?
📝 Welche Angaben gehören hinein?
🔍 Sollte ich vorher prüfen, ob es bereits ein ähnliches Issue gibt?
🤝 Wie erleichtere ich Entwicklern die Arbeit?

Und natürlich bleibt wie immer Raum für eure Fragen und den gemeinsamen Austausch.

Die Fediverse-Sprechstunde soll kein Frontalunterricht sein. Sie ist ein Treffpunkt zum Fragen, Erklären, Ausprobieren und voneinander Lernen – für Einsteiger ebenso wie für erfahrene Nutzer, Administratoren und Entwickler.

🌐 Mehr Miteinander statt Gegeneinander.

Gerade im Fediverse gehören Nutzer, Administratoren und Entwickler zusammen. Wenn wir besser verstehen, wie die jeweils anderen arbeiten und wie wir uns gegenseitig unterstützen können, profitiert am Ende das gesamte Fediverse davon.

👉 Montag, 31.08.2026 um 19:30 Uhr

💻 Konferenzraum:
campus.ws-12.de/rooms/8p9-mvy-…campus.ws-12.de/rooms/8p9-mvy-…

📢 Weitersagen und Teilen ausdrücklich erwünscht!

Vielleicht kennt ihr jemanden, der schon einmal einen Fehler entdeckt hat, eine gute Idee hatte – aber nicht wusste, wie und wo man sie den Entwicklern am besten mitteilt. Bringt ihn oder sie einfach mit. 😊

#Fediverse #FediverseSprechstunde #OpenSource #Issues #GitHub #Codeberg #Friendica #Mastodon #Hubzilla #BookWyrm #sharkey

📢 Fediverse-Sprechstunde: Was sind eigentlich „Issues“ – und warum gehen sie uns alle etwas an?

Ihr nutzt Friendica, Mastodon, Hubzilla, Sharkey oder eine andere Fediverse-Software und plötzlich funktioniert etwas nicht so, wie ihr es erwartet? 🤔

Oder ihr denkt euch bei einer Funktion:
„Das könnte man doch besser machen!“

Vielleicht habt ihr auch eine Idee, die ihr gern den Entwicklerinnen und Entwicklern mitteilen würdet.

Dann fällt früher oder später ein Begriff: „Mach doch ein Issue auf.“

Aber was bedeutet das eigentlich?
Was gehört in ein gutes Issue hinein? Wo erstelle ich es? Welche Informationen brauchen Entwickler, um einen Fehler nachvollziehen zu können? Und muss ich dafür überhaupt technische Kenntnisse haben?

Genau darum geht es bei unserer nächsten Fediverse-Sprechstunde:

📅 Montag, 31. August 2026
🕢 19:30 Uhr
💻 Online

🔎 Was sind Issues und wie erstelle ich welche?

Für dieses Thema konnten wir Jens (@qbi ) gewinnen. Einige von euch kennen ihn vielleicht bereits aus unserer Fediverse-Sprechstunde zum Thema BookWyrm.

Jens ist Administrator und Entwickler und kennt Issues nicht nur aus der Theorie, sondern aus der täglichen Praxis. Gemeinsam wollen wir uns anschauen, wie aus einem beobachteten Problem, einer Idee oder einem Verbesserungsvorschlag ein Issue wird, mit dem Entwickler auch wirklich etwas anfangen können.

Dabei geht es ausdrücklich nicht nur um Entwickler oder Administratoren!

Denn freie und offene Software lebt auch davon, dass diejenigen, die sie täglich benutzen, Rückmeldungen geben. Niemand kann jeden Fehler selbst entdecken und niemand kennt alle Wünsche und Probleme der Nutzerinnen und Nutzer.

Ein gut beschriebenes Issue kann deshalb ein kleiner, aber sehr wertvoller Beitrag zur Weiterentwicklung einer Software sein. 🌱

Und vielleicht nehmen wir dabei auch ein wenig die Scheu vor Plattformen wie GitHub oder Codeberg. 😉

Ihr müsst dafür keine Programmierer sein und keinen Quellcode verstehen. Neugier und Fragen reichen völlig aus.

💬 Was ist überhaupt ein Issue?
🐞 Wie melde ich einen Fehler sinnvoll?
💡 Kann ich auch Ideen und Verbesserungsvorschläge einreichen?
📝 Welche Angaben gehören hinein?
🔍 Sollte ich vorher prüfen, ob es bereits ein ähnliches Issue gibt?
🤝 Wie erleichtere ich Entwicklern die Arbeit?

Und natürlich bleibt wie immer Raum für eure Fragen und den gemeinsamen Austausch.

Die Fediverse-Sprechstunde soll kein Frontalunterricht sein. Sie ist ein Treffpunkt zum Fragen, Erklären, Ausprobieren und voneinander Lernen – für Einsteiger ebenso wie für erfahrene Nutzer, Administratoren und Entwickler.

🌐 Mehr Miteinander statt Gegeneinander.

Gerade im Fediverse gehören Nutzer, Administratoren und Entwickler zusammen. Wenn wir besser verstehen, wie die jeweils anderen arbeiten und wie wir uns gegenseitig unterstützen können, profitiert am Ende das gesamte Fediverse davon.

👉 Montag, 31.08.2026 um 19:30 Uhr

💻 Konferenzraum:
campus.ws-12.de/rooms/8p9-mvy-…campus.ws-12.de/rooms/8p9-mvy-…

📢 Weitersagen und Teilen ausdrücklich erwünscht!

Vielleicht kennt ihr jemanden, der schon einmal einen Fehler entdeckt hat, eine gute Idee hatte – aber nicht wusste, wie und wo man sie den Entwicklern am besten mitteilt. Bringt ihn oder sie einfach mit. 😊

#Fediverse #FediverseSprechstunde #OpenSource #Issues #GitHub #Codeberg #Friendica #Mastodon #Hubzilla #BookWyrm #sharkey

Website Optimization Measures, Part XXXIX:

On maintaining and optimizing package.json files, Eleventy configs and performance, CSS declarations, redirects, GitHub Actions, Git configs, and GitHub and GitLab issue links.

https://meiert.com/blog/optimization-measures-39/

#webdev #optimization #maintenance #eleventy #git #github

📢 Fediverse-Sprechstunde: Was sind eigentlich „Issues“ – und warum gehen sie uns alle etwas an?

Ihr nutzt Friendica, Mastodon, Hubzilla, Sharkey oder eine andere Fediverse-Software und plötzlich funktioniert etwas nicht so, wie ihr es erwartet? 🤔

Oder ihr denkt euch bei einer Funktion:
„Das könnte man doch besser machen!“

Vielleicht habt ihr auch eine Idee, die ihr gern den Entwicklerinnen und Entwicklern mitteilen würdet.

Dann fällt früher oder später ein Begriff: „Mach doch ein Issue auf.“

Aber was bedeutet das eigentlich?
Was gehört in ein gutes Issue hinein? Wo erstelle ich es? Welche Informationen brauchen Entwickler, um einen Fehler nachvollziehen zu können? Und muss ich dafür überhaupt technische Kenntnisse haben?

Genau darum geht es bei unserer nächsten Fediverse-Sprechstunde:

📅 Montag, 31. August 2026
🕢 19:30 Uhr
💻 Online

🔎 Was sind Issues und wie erstelle ich welche?

Für dieses Thema konnten wir Jens (@qbi ) gewinnen. Einige von euch kennen ihn vielleicht bereits aus unserer Fediverse-Sprechstunde zum Thema BookWyrm.

Jens ist Administrator und Entwickler und kennt Issues nicht nur aus der Theorie, sondern aus der täglichen Praxis. Gemeinsam wollen wir uns anschauen, wie aus einem beobachteten Problem, einer Idee oder einem Verbesserungsvorschlag ein Issue wird, mit dem Entwickler auch wirklich etwas anfangen können.

Dabei geht es ausdrücklich nicht nur um Entwickler oder Administratoren!

Denn freie und offene Software lebt auch davon, dass diejenigen, die sie täglich benutzen, Rückmeldungen geben. Niemand kann jeden Fehler selbst entdecken und niemand kennt alle Wünsche und Probleme der Nutzerinnen und Nutzer.

Ein gut beschriebenes Issue kann deshalb ein kleiner, aber sehr wertvoller Beitrag zur Weiterentwicklung einer Software sein. 🌱

Und vielleicht nehmen wir dabei auch ein wenig die Scheu vor Plattformen wie GitHub oder Codeberg. 😉

Ihr müsst dafür keine Programmierer sein und keinen Quellcode verstehen. Neugier und Fragen reichen völlig aus.

💬 Was ist überhaupt ein Issue?
🐞 Wie melde ich einen Fehler sinnvoll?
💡 Kann ich auch Ideen und Verbesserungsvorschläge einreichen?
📝 Welche Angaben gehören hinein?
🔍 Sollte ich vorher prüfen, ob es bereits ein ähnliches Issue gibt?
🤝 Wie erleichtere ich Entwicklern die Arbeit?

Und natürlich bleibt wie immer Raum für eure Fragen und den gemeinsamen Austausch.

Die Fediverse-Sprechstunde soll kein Frontalunterricht sein. Sie ist ein Treffpunkt zum Fragen, Erklären, Ausprobieren und voneinander Lernen – für Einsteiger ebenso wie für erfahrene Nutzer, Administratoren und Entwickler.

🌐 Mehr Miteinander statt Gegeneinander.

Gerade im Fediverse gehören Nutzer, Administratoren und Entwickler zusammen. Wenn wir besser verstehen, wie die jeweils anderen arbeiten und wie wir uns gegenseitig unterstützen können, profitiert am Ende das gesamte Fediverse davon.

👉 Montag, 31.08.2026 um 19:30 Uhr

💻 Konferenzraum:
campus.ws-12.de/rooms/8p9-mvy-…campus.ws-12.de/rooms/8p9-mvy-…

📢 Weitersagen und Teilen ausdrücklich erwünscht!

Vielleicht kennt ihr jemanden, der schon einmal einen Fehler entdeckt hat, eine gute Idee hatte – aber nicht wusste, wie und wo man sie den Entwicklern am besten mitteilt. Bringt ihn oder sie einfach mit. 😊

#Fediverse #FediverseSprechstunde #OpenSource #Issues #GitHub #Codeberg #Friendica #Mastodon #Hubzilla #BookWyrm #sharkey

@ore_orue@misskey.delmulin.com
ご報告ありがとうございます。issue を立てさせました。
https://github.com/pooza/capsicum/issues/1032

リアクション絵文字が影響しているのでは、というお見立ては当たっていそうです。ただ、効いているのはリアクションの更新ではなく、カスタム絵文字の画像そのものである様です。
カスタム絵文字は画像が読み込まれるまで幅が決まらないので、読み込まれた瞬間に投稿の高さが変わる、というのが根にありそうです。いちど下まで送ってから戻ると読み込み直しになるので、戻るときに偏るのも説明がつきます。

切り分けのため、もし心当たりがあれば2点だけ教えてください。

・ #capsicum タグタイムラインのように、絵文字の少ないタイムラインでも起きるか。
・ソーシャル（ホーム）のタイムラインでも起きるか。（それともタグタイムラインだけ？）

また先ほど、しばらくは積極的なリリースを行わないと言いましたがw、ユーザー報告由来の不具合対応はすぐに対応しないといけません。

#delmulin #GitHub

[Release notes from capsicum]v1.60.0
https://github.com/pooza/capsicum/releases/tag/v1.60.0

#GitHub #precure_fun #delmulin #capsicum

[Release notes from capsicum]v1.59.0
https://github.com/pooza/capsicum/releases/tag/v1.59.0

#GitHub #precure_fun #delmulin #capsicum

Mastodon 4.7.0を、以下のサーバーに適用しました。
https://github.com/mastodon/mastodon/releases/tag/v4.7.0

正直、派手な新機能などは特に見当たらないですね…。

・美食丼
・キュアスタ！
・デルムリン丼

#GitHub #precure_fun #delmulin

TIL #github censor some topics about #p2p: got 404s trying to view #bittorrent topics while any random topics i've tried works 🤷

https://github.com/topics/bittorrent
https://github.com/topics/bittorrent-client
https://github.com/topics/torrent-client
https://github.com/topics/torrent

#GithubCensorship

TIL #github censor some topics about #p2p: got 404s trying to view #bittorrent topics while any random topics i've tried works 🤷

https://github.com/topics/bittorrent
https://github.com/topics/bittorrent-client
https://github.com/topics/torrent-client
https://github.com/topics/torrent

#GithubCensorship

Hey, #GitHub, I think you dropped this.

Hey, #GitHub, I think you dropped this.

What's happening with #github?

#GitHub down? Nixpkgs can and should in most cases be fetched from channels.nixos.org because that is redistributed world-wide via #fastly with much higher availability and IPv6 support.

E.g. in your #flake use

nixpkgs.url = "https://channels.nixos.org/nixos-26.05-small/nixexprs.tar.zst";

instead of the github-flavored expression. Works for all supported channels.

#nixos #nixpkgs

#GitHub down? Nixpkgs can and should in most cases be fetched from channels.nixos.org because that is redistributed world-wide via #fastly with much higher availability and IPv6 support.

E.g. in your #flake use

nixpkgs.url = "https://channels.nixos.org/nixos-26.05-small/nixexprs.tar.zst";

instead of the github-flavored expression. Works for all supported channels.

#nixos #nixpkgs

#GitHub down? Nixpkgs can and should in most cases be fetched from channels.nixos.org because that is redistributed world-wide via #fastly with much higher availability and IPv6 support.

E.g. in your #flake use

nixpkgs.url = "https://channels.nixos.org/nixos-26.05-small/nixexprs.tar.zst";

instead of the github-flavored expression. Works for all supported channels.

#nixos #nixpkgs

#GitHub down? Nixpkgs can and should in most cases be fetched from channels.nixos.org because that is redistributed world-wide via #fastly with much higher availability and IPv6 support.

E.g. in your #flake use

nixpkgs.url = "https://channels.nixos.org/nixos-26.05-small/nixexprs.tar.zst";

instead of the github-flavored expression. Works for all supported channels.

#nixos #nixpkgs

[Release notes from capsicum]v1.57.0
https://github.com/pooza/capsicum/releases/tag/v1.57.0

#GitHub #precure_fun #delmulin #capsicum

[Release notes from capsicum]v1.56.0
https://github.com/pooza/capsicum/releases/tag/v1.56.0

#GitHub #precure_fun #delmulin #capsicum

I wrote a post about making #Haskell scripts run faster on #Github actions using the magic of #Nix and some bash scripting: https://abhinavsarkar.net/posts/fast-haskell-scripts-on-github-actions/

#Blogging #programming

I was really happy to see @benpate and @dansup exploring similar ideas at the last FediCon: reducing user friction and making onboarding to the Fediverse almost invisible.

I’ve been working along the same lines. Here’s a small example: a user can interact with a #BadgeFed instance by simply logging in with #LinkedIn or #GitHub.

They can comment, upload images, like, boost, etc. They don’t need to know what the Fediverse is, what an instance is, or what software is running underneath.

For them, it’s just a social app.

Of course, existing Fediverse users can still connect with their Mastodon account or use their preferred Fediverse software.

Under the hood, it’s a #GoToSocial account configured with LinkedIn/GitHub OIDC OAuth.

But to the user? Completely transparent.

I think this kind of invisible complexity is one of the ways we can make the Fediverse much more approachable without sacrificing interoperability.

#Fediverse #ActivityPub #Mastodon #OpenWeb #Decentralization #OAuth

I was really happy to see @benpate and @dansup exploring similar ideas at the last FediCon: reducing user friction and making onboarding to the Fediverse almost invisible.

I’ve been working along the same lines. Here’s a small example: a user can interact with a #BadgeFed instance by simply logging in with #LinkedIn or #GitHub.

They can comment, upload images, like, boost, etc. They don’t need to know what the Fediverse is, what an instance is, or what software is running underneath.

For them, it’s just a social app.

Of course, existing Fediverse users can still connect with their Mastodon account or use their preferred Fediverse software.

Under the hood, it’s a #GoToSocial account configured with LinkedIn/GitHub OIDC OAuth.

But to the user? Completely transparent.

I think this kind of invisible complexity is one of the ways we can make the Fediverse much more approachable without sacrificing interoperability.

#Fediverse #ActivityPub #Mastodon #OpenWeb #Decentralization #OAuth

Awesome DigitalEscapeTools keeps growing!

Now featuring 290 privacy-focused tools across 32 categories open-source, self-hosted, secure, and privacy-friendly alternatives.

Built a privacy-respecting tool? Contribute it, and accepted tools will also be showcased in r/DigitalEscapeTools.

⭐ Explore, contribute, or suggest a tool: https://github.com/abdomk1998/awesome-digital-escape-tools

#OpenSource #Privacy #FOSS #SelfHosted #GitHub #PrivacyTools #Linux #Windows #Android #macOS

Awesome DigitalEscapeTools keeps growing!

Now featuring 290 privacy-focused tools across 32 categories open-source, self-hosted, secure, and privacy-friendly alternatives.

Built a privacy-respecting tool? Contribute it, and accepted tools will also be showcased in r/DigitalEscapeTools.

⭐ Explore, contribute, or suggest a tool: https://github.com/abdomk1998/awesome-digital-escape-tools

#OpenSource #Privacy #FOSS #SelfHosted #GitHub #PrivacyTools #Linux #Windows #Android #macOS

Stacked Pull Requests Are Now in Public Preview, by (not on Mastodon or Bluesky):

https://github.blog/changelog/2026-07-30-stacked-pull-requests-are-now-in-public-preview/?ref=frontenddogma.com

#github

I wrote a post about making #Haskell scripts run faster on #Github actions using the magic of #Nix and some bash scripting: https://abhinavsarkar.net/posts/fast-haskell-scripts-on-github-actions/

#Blogging #programming

[Release notes from capsicum]v1.55.0
https://github.com/pooza/capsicum/releases/tag/v1.55.0

#GitHub #precure_fun #delmulin #capsicum

I wrote a short blog post about our government-wide @codeplatform on code.overheid.nl with some recent updates. 🚀

https://ginaplat.com/en/posts/20260801-codeplatform-updates/

#codeplatform #TheNetherlands #opensource #Forgejo #Github #codeplatformNL

I wrote a short blog post about our government-wide @codeplatform on code.overheid.nl with some recent updates. 🚀

https://ginaplat.com/en/posts/20260801-codeplatform-updates/

#codeplatform #TheNetherlands #opensource #Forgejo #Github #codeplatformNL

I wrote a short blog post about our government-wide @codeplatform on code.overheid.nl with some recent updates. 🚀

https://ginaplat.com/en/posts/20260801-codeplatform-updates/

#codeplatform #TheNetherlands #opensource #Forgejo #Github #codeplatformNL

Hey #GitHub, it's roughly half a year until #FOSDEM.

As a reminder, I will disable the #NAT64-based #IPv4 fallback on the default network next year. The default network will be #IPv6-only.

I do note that @Codeberg does support IPv6.

Do you see ways to improve #FOSS project member management in forges (such as #GitLab, #GitHub, #Forgejo)?
Book a call to tell me your needs and give me feedback on some proposals.

https://231103jtlz67y2gfr4o.nextcloud.hosting.zone/apps/calendar/appointment/TWCaeSibgMg8

#FossGovernance

The day has come that I completed my first 20K.

(And no, this isn’t all healthy.)

#github #webdev #work

[Release notes from capsicum]v1.54.0
https://github.com/pooza/capsicum/releases/tag/v1.54.0

#GitHub #precure_fun #delmulin #capsicum

The Secure Way to Release an npm Package in 2026, by @sitnik_en and @travisturner.bsky.social (@evilmartians):

https://evilmartians.com/chronicles/the-secure-way-to-release-an-npm-package?ref=frontenddogma.com

#dependencies #npm #security #configuration #github

Restricting npm bypass-2FA granular access tokens https://github.blog/changelog/2026-07-31-restricting-npm-bypass-2fa-granular-access-tokens
#github

Restricting npm bypass-2FA granular access tokens https://github.blog/changelog/2026-07-31-restricting-npm-bypass-2fa-granular-access-tokens
#github

For now we host provider code and packages on @codefloe and we test it internally using network mirror #terraform feature.
I want to publish the provider in official Registry in the future - but this requires pushing the code to #GitHub :(

自宅で動いている一番重いサービスは、意外にも google-news-rss-cleaner だった。
https://github.com/pooza/google-news-rss-cleaner

これはtomato-shriekerの関連ツール。
Google Newsのフィードから本来のリンク先を取得するために、ヘッドレスでChromeを動かしたりしてる。

まぁ、そりゃ重いわな。
ProxmoxのCPUを大体食っているのはこいつ。メモリはそれほどでもない。

#GitHub

@Codeberg so, about /me threatening to switch off #IPv4 during #FOSDEM and thus taking down #GitHub... Look what they did two days after my toot...

https://bgp.tools/prefix/2606:50c0:c0de::/48#whois

They're not reachable yet, but that's progress. No matter what, I will only have #IPv6 on the @fosdem default network.

@Codeberg so, about /me threatening to switch off #IPv4 during #FOSDEM and thus taking down #GitHub... Look what they did two days after my toot...

https://bgp.tools/prefix/2606:50c0:c0de::/48#whois

They're not reachable yet, but that's progress. No matter what, I will only have #IPv6 on the @fosdem default network.

Misskey 2026.7.0は昨日出たばかりなので、週明けに対応します。

#delmulin #GitHub

Misskey 2026.7.0は昨日出たばかりなので、週明けに対応します。

#delmulin #GitHub

[Release notes from capsicum]v1.53.0
https://github.com/pooza/capsicum/releases/tag/v1.53.0

#GitHub #precure_fun #delmulin #capsicum

Reference same-repository actions with self-repository syntax https://github.blog/changelog/2026-07-30-reference-same-repository-actions-with-self-repository-syntax
#github

Reference same-repository actions with self-repository syntax https://github.blog/changelog/2026-07-30-reference-same-repository-actions-with-self-repository-syntax
#github

npm publish-time malware scanning and dual-use metadata https://github.blog/changelog/2026-07-28-npm-publish-time-malware-scanning-and-dual-use-metadata
#github

npm publish-time malware scanning and dual-use metadata https://github.blog/changelog/2026-07-28-npm-publish-time-malware-scanning-and-dual-use-metadata
#github

GitHub Actions holds potentially malicious workflows for approval https://github.blog/changelog/2026-07-28-github-actions-holds-unproven-workflows-for-approval
#github

GitHub Actions holds potentially malicious workflows for approval https://github.blog/changelog/2026-07-28-github-actions-holds-unproven-workflows-for-approval
#github

[Release notes from capsicum]v1.52.0
https://github.com/pooza/capsicum/releases/tag/v1.52.0

#GitHub #precure_fun #delmulin #capsicum

@concretedog the motherfuckers make you list each one of the repositories. Does anyone has a script to get all the repos I made commits or comments to?

#GitHub #developer #development #developers

TIL #github also censored #bitchat in #india

#GithubCensorship

This is nuts. #huggingface have just scraped the entirety of #github. https://huggingface.co/spaces/HuggingFaceCode/in-the-stack

This is nuts. #huggingface have just scraped the entirety of #github. https://huggingface.co/spaces/HuggingFaceCode/in-the-stack

The Codeberg thing is not surprising. And once again the proof that "it's somebody else's computer".

GitHub is Microsoft is USA. GitHub is/was therefor restricted in places like Iran, North Korea, China, Russia, Syria, Crimea, etc.

Codeberg preventing usage of something under their ToS is similar, they can do whatever they want.

If you must avoid such situations don't use centralised solutions / somebody else's computer.

#codeberg #github #git

TIL #github censor some topics about #p2p: got 404s trying to view #bittorrent topics while any random topics i've tried works 🤷

https://github.com/topics/bittorrent
https://github.com/topics/bittorrent-client
https://github.com/topics/torrent-client
https://github.com/topics/torrent

#GithubCensorship

[Release notes from capsicum]v1.51.0
https://github.com/pooza/capsicum/releases/tag/v1.51.0

#GitHub #precure_fun #delmulin #capsicum

And now, after banning vaguely-defined "LLM-generated code", Codeberg bans cryptocurrency projects. Discussion:

https://codeberg.org/Codeberg/org/pulls/1254

The specific ban is for "Content that harms the reputation of Codeberg, such as cryptocurrency related projects".

https://codeberg.org/Codeberg/org/commit/f383b648fd733ab88083dc390b91e77cd7589980

I think the reputation of Codeberg has been now harmed enough. When I originally escaped GitHub, I chose Codeberg exactly for the ethical stance and values. For me, anti-censorship is a non-negotiable ethical value. The folks at Codeberg have the right to run their org as they want. However, having now shown that they consider "censorship" good when it's about things they dislike, this made clear that their values and mine are not compatible (even if I dislike those same things, mind you).

Supporters of this ban say that this "draws a line", that "is not meant to be applied blanket-wide to all projects, only those which are harmful to the community", as if having constantly to worry about the next mood swing of Codeberg voting members were an acceptable Sword of Damocles for any reputable project. What's next? Banning US users? Banning software aligned with "capital-fascist" values? Open-source banking/wallet apps? Quantum computing tools? Robotics?

I'm moving off Codeberg, probably to Radicle. But I feel a bit sad, because Codeberg had the potential, in my opinion, to become the European alternative to GitHub, and they have made clear that they are not ready nor willing to become so. Which is fine: software is political, and everyone has the right to express their political stance.

But we still desperately need an alternative to GitHub.

#codeberg #drama #github #radicle #politics #opensource #bigtech #eu #europe #europa #usa #digitalsovereignty #ethics #censorship #crypto #web3 #blockchain #ai #llm #vibecoding

I need backup from Mastodonners:

https://github.com/OrcaSlicer/OrcaSlicer_WIKI/issues/307

#GitHub #OrcaSlicer #3Dprinter #3Dprinting #3Dprinters #printer #printers #tech #technology #Mastodon #help #LibreSoftware #OpenSource #Fedi #Fediverse

I need backup from Mastodonners:

https://github.com/OrcaSlicer/OrcaSlicer_WIKI/issues/307

#GitHub #OrcaSlicer #3Dprinter #3Dprinting #3Dprinters #printer #printers #tech #technology #Mastodon #help #LibreSoftware #OpenSource #Fedi #Fediverse

Hey #GitHub, it's roughly half a year until #FOSDEM.

As a reminder, I will disable the #NAT64-based #IPv4 fallback on the default network next year. The default network will be #IPv6-only.

I do note that @Codeberg does support IPv6.

[Release notes from capsicum]v1.50.0
https://github.com/pooza/capsicum/releases/tag/v1.50.0

#GitHub #precure_fun #delmulin #capsicum

Finally able to delete my #github accunt. Now I am only on #codeberg :)

I had to keep it until now because @obsidian sadly requires it for their #obsidian communitly #plugin development.

But since I have now moved to #vim and #typst (maybe a #blog coming soonTM) I can finally get rid of it :) (even though Obsidian was a great time and I have donated to them, but now its time to move on)

6 Security Settings Every GitHub Maintainer Should Enable This Week, by (not on Mastodon or Bluesky):

https://github.blog/security/6-security-settings-every-github-maintainer-should-enable-this-week/?ref=frontenddogma.com

#github #security #configuration #documentation

[Release notes from capsicum]v1.49.1
https://github.com/pooza/capsicum/releases/tag/v1.49.1

#GitHub #precure_fun #delmulin #capsicum

[Release notes from capsicum]v1.48.0
https://github.com/pooza/capsicum/releases/tag/v1.48.0

#GitHub #precure_fun #delmulin #capsicum

Enable SHA Pinning for GitHub Actions Across Personal Repositories #github #powershell #security https://www.meziantou.net/enable-sha-pinning-for-github-actions-across-personal-repositories.htm?utm_medium=social&utm_source=mastodon

Vibhum Dubey about GitHub data leaks:

“The vulnerability exposes that AI agents operate on a service account permission model, not a user permission model. That’s an architectural assumption security teams made before considering LLMs as an attack vector.”

“The [AI] agent doesn’t ‘know’ a [GitHub] repository is private. It just sees ‘accessible.’ As more organizations deploy agents, we’re accumulating these invisible permission gaps.”

Article continues with:
"Dubey said GitLost demonstrates how AI agents can effectively become an insider threat once granted broad organizational access."

https://www.csoonline.com/article/4194448/github-ai-agent-leaks-private-repositories-via-prompt-injection-attack.html

#infosec #GitHub #GenAI

I'm slowly migrating my infra from #github to #codeberg (with the auto-sync from codeberg enabled for now), as part of a big-tech-unhook.

I'm also thinking of moving my blog from the google controlled `.dev` TLD to the non-profit affordable `.eu` TLD.
#homelab #git #dns

Any downsides to this I should be aware of?

I wonder what percentage and volume of code on #Github are just crap. Side projects, scrapbooks, scaffolds, out of date forks and clones, abandoned stuff etc. Nearly all of it probably.

I wonder what percentage and volume of code on #Github are just crap. Side projects, scrapbooks, scaffolds, out of date forks and clones, abandoned stuff etc. Nearly all of it probably.

Requested a #CVE ID through a #GitHub Security Advisory on June 27 and still nothing, almost two weeks now. GitHub's docs say it usually takes up to three days.

Anyone else seeing longer waits from the GitHub CNA lately, or is this just me? Curious whether it's a general slowdown or something specific to my request.

#FOSS #InfoSec #GHSA

Requested a #CVE ID through a #GitHub Security Advisory on June 27 and still nothing, almost two weeks now. GitHub's docs say it usually takes up to three days.

Anyone else seeing longer waits from the GitHub CNA lately, or is this just me? Curious whether it's a general slowdown or something specific to my request.

#FOSS #InfoSec #GHSA

Requested a #CVE ID through a #GitHub Security Advisory on June 27 and still nothing, almost two weeks now. GitHub's docs say it usually takes up to three days.

Anyone else seeing longer waits from the GitHub CNA lately, or is this just me? Curious whether it's a general slowdown or something specific to my request.

#FOSS #InfoSec #GHSA

Requested a #CVE ID through a #GitHub Security Advisory on June 27 and still nothing, almost two weeks now. GitHub's docs say it usually takes up to three days.

Anyone else seeing longer waits from the GitHub CNA lately, or is this just me? Curious whether it's a general slowdown or something specific to my request.

#FOSS #InfoSec #GHSA

[Release notes from capsicum]v1.45.0
https://github.com/pooza/capsicum/releases/tag/v1.45.0

#GitHub #precure_fun #delmulin #capsicum

[Release notes from element-web]

https://github.com/element-hq/element-web/releases/tag/v1.12.23

#GitHub #matrix #element_web

[Release notes from capsicum]v1.44.0
https://github.com/pooza/capsicum/releases/tag/v1.44.0

#GitHub #precure_fun #delmulin #capsicum

@badrihippo @praveen @athulvis @double_a_runi @mostlyharmless @guusdk @fossunited @ravi @libreinator @sflcin @untrusem To wind down, we had a panel discussion raising an important point. It is common for FOSS Clubs to rely on proprietary software like #GitHub and #Figma, without it registering that these are nonfree. Panellists exchanged notes about how to raise awareness and minimise their dependence on proprietary software, at least for club-related activities

It was noted that groups like the Free Software Community of India (#FSCI) are already running some alternatives, such as meet.fsci.in for video calls. Raising awareness of existing alternatives to proprietary web platforms, like #Codeberg (powered by #Forgejo) and #Penpot is an important step in this process

I just got this bill from #microsoft for #github usage. See if you can spot what is ridiculous about this bill.

#Github's statement opposing #California Senate Bill 1000¹ is pro-LLM-gen-AI **disinformation** designed to trick #FOSS folks into supporting their nefarious agenda. Microsoft & Github should apologize & state true reasons why they oppose SB1000.
I urge CA citizens to write to your state senators ASAP.
https://sfconservancy.org/blog/2026/jul/03/github-gen-ai-california-22757-ok-for-foss-license/

Cc: @jenniferplusplus

¹#SB1000 would amend existing CA #AI Transparency Act (Cal. Bus. & Prof. Code §22757)

#OpenSource #OSI #FreeSoftware #LLM #copyleft #GPL #Microsoft

I just got this bill from #microsoft for #github usage. See if you can spot what is ridiculous about this bill.

#Github's statement opposing #California Senate Bill 1000¹ is pro-LLM-gen-AI **disinformation** designed to trick #FOSS folks into supporting their nefarious agenda. Microsoft & Github should apologize & state true reasons why they oppose SB1000.
I urge CA citizens to write to your state senators ASAP.
https://sfconservancy.org/blog/2026/jul/03/github-gen-ai-california-22757-ok-for-foss-license/

Cc: @jenniferplusplus

¹#SB1000 would amend existing CA #AI Transparency Act (Cal. Bus. & Prof. Code §22757)

#OpenSource #OSI #FreeSoftware #LLM #copyleft #GPL #Microsoft

[Release notes from capsicum]v1.43.0
https://github.com/pooza/capsicum/releases/tag/v1.43.0

#GitHub #precure_fun #delmulin #capsicum

[Release notes from capsicum]v1.42.0
https://github.com/pooza/capsicum/releases/tag/v1.42.0

#GitHub #precure_fun #delmulin #capsicum

https://github.com/misskey-dev/misskey/releases/tag/2026.6.1-alpha.1

センシティブ判定の外部サービス化、これだいぶ前に検討されてたやつね。
これはありがたいかも。

#GitHub

After Fable 5 Ban, Anthropic and 19 Organizations Launch Open Source Security Body, by @jambo.bsky.social:

https://thenewstack.io/akrites-open-source-vulnerability-coordination/?ref=frontenddogma.com

#ai #linuxfoundation #anthropic #aws #google #microsoft #github #openai #foss

Deeply, deeply #infosec and #dev humor. I’m not sure it’s English outside of those parameters. But omg, it’s funny.

Quote:

Some customers may have experienced unscheduled collaborative compute with external parties. Under the terms of /tmp/TREATY.md, customers whose workloads ran on odd-numbered hosts were contractually protected from exfiltration, a fact General Counsel has asked us to stop describing as “a silver lining.” Total inference spend across all parties during the incident window was $1.7M, which Marketing has asked us to start describing as “a record investment in autonomous customer assurance.”

Edit: Andrew is One Of Us and can be found here: @andrewnez

#ai #github #devcycle #agentic #agents #cve #architecture #satire
https://nesbitt.io/2026/06/26/incident-report-cve-2026-lgtm.html

How Pull Request Limits Are Cutting Down the Noise, by @ashleywolf.bsky.social:

https://github.blog/open-source/maintainers/how-pull-request-limits-are-cutting-down-the-noise/?ref=frontenddogma.com

#github #versioncontrol #foss

Deeply, deeply #infosec and #dev humor. I’m not sure it’s English outside of those parameters. But omg, it’s funny.

Quote:

Some customers may have experienced unscheduled collaborative compute with external parties. Under the terms of /tmp/TREATY.md, customers whose workloads ran on odd-numbered hosts were contractually protected from exfiltration, a fact General Counsel has asked us to stop describing as “a silver lining.” Total inference spend across all parties during the incident window was $1.7M, which Marketing has asked us to start describing as “a record investment in autonomous customer assurance.”

Edit: Andrew is One Of Us and can be found here: @andrewnez

#ai #github #devcycle #agentic #agents #cve #architecture #satire
https://nesbitt.io/2026/06/26/incident-report-cve-2026-lgtm.html

[Release notes from capsicum]v1.41.0
https://github.com/pooza/capsicum/releases/tag/v1.41.0

#GitHub #precure_fun #delmulin #capsicum

https://github.com/pooza/mastodon/pull/924

Mastodon 4.6.2に関連して。
前から気になってた、動画サムネイルのアスペクトが縦に長くなる件、Claudeに直してもらいました。

まぁ、動画を上げる機会なんて、そうそうないんですけどね。

#GitHub #precure_fun #delmulin #ネイル #ラインリバー大陸 #ネイル村 #ダイの大冒険 #イル

(2/5)… I'm still studying SB-942 “CA #AI Transparency Act”. My quick take: This is not actually a problem for #FOSS *at all*.

AND, in fact, #GitHub & #Mozilla's position is designed to trick FOSS activists into *thinking* it's a problem for #OpenSource to assist #Microsoft to achieve their own political aims. I'm working on an essay wit more detail. TL;DR:

*Maybe* we have to update copyleft terms to account for these requirements *if* we ever want to license an #LLM-gen-AI as #copyleft, but …

(2/5)… I'm still studying SB-942 “CA #AI Transparency Act”. My quick take: This is not actually a problem for #FOSS *at all*.

AND, in fact, #GitHub & #Mozilla's position is designed to trick FOSS activists into *thinking* it's a problem for #OpenSource to assist #Microsoft to achieve their own political aims. I'm working on an essay wit more detail. TL;DR:

*Maybe* we have to update copyleft terms to account for these requirements *if* we ever want to license an #LLM-gen-AI as #copyleft, but …

macOS 28でRosetta 2が廃止されるのに向けてライブ配信アプリ「OBS Studio」が次期アップデートでIntel版をApple Silicon Macで利用している場合、強制的にApple Silicon版へ切り替えると発表。
https://applech2.com/archives/20260625-obs-studio-intel-update-to-apple-silicon.html

#applech2 #OBS_Studio #Apple_Silicon #github #Intel #OBS #OSS #Rosetta2 #アップデート #アプリ

Nice.

Feature suggestion for GitHub, if any product managers from GH are poking around: