#codberg — Public Fediverse posts

Iocaine leads to a lot of bot traffic to the maze. Some crawlers also seems to get through Iocaine and then crawl Codeberg or other Iocaine-protected Forgejo instances. For this reason, I don't want to deploy Iocaine in front of Codberg.

My proposed solution would be making Codberg only accessible to logged-in users and having an unauthenticated landing/explore site.

That site would allow you to

• browse the list of repos
• read READMEs-see project details (contributors, issue stats, licenses, activity)
• read project's documentation

But commit history, file browsing and (for now also issues) wouldn't be accessible without logging in.

What do you think about this?

#codberg #cod #forgejo #iocaine

Iocaine leads to a lot of bot traffic to the maze. Some crawlers also seems to get through Iocaine and then crawl Codeberg or other Iocaine-protected Forgejo instances. For this reason, I don't want to deploy Iocaine in front of Codberg.

My proposed solution would be making Codberg only accessible to logged-in users and having an unauthenticated landing/explore site.

That site would allow you to

• browse the list of repos
• read READMEs-see project details (contributors, issue stats, licenses, activity)
• read project's documentation

But commit history, file browsing and (for now also issues) wouldn't be accessible without logging in.

What do you think about this?

#codberg #cod #forgejo #iocaine

Iocaine leads to a lot of bot traffic to the maze. Some crawlers also seems to get through Iocaine and then crawl Codeberg or other Iocaine-protected Forgejo instances. For this reason, I don't want to deploy Iocaine in front of Codberg.

My proposed solution would be making Codberg only accessible to logged-in users and having an unauthenticated landing/explore site.

That site would allow you to

• browse the list of repos
• read READMEs-see project details (contributors, issue stats, licenses, activity)
• read project's documentation

But commit history, file browsing and (for now also issues) wouldn't be accessible without logging in.

What do you think about this?

#codberg #cod #forgejo #iocaine

Iocaine leads to a lot of bot traffic to the maze. Some crawlers also seems to get through Iocaine and then crawl Codeberg or other Iocaine-protected Forgejo instances. For this reason, I don't want to deploy Iocaine in front of Codberg.

My proposed solution would be making Codberg only accessible to logged-in users and having an unauthenticated landing/explore site.

That site would allow you to

• browse the list of repos
• read READMEs-see project details (contributors, issue stats, licenses, activity)
• read project's documentation

But commit history, file browsing and (for now also issues) wouldn't be accessible without logging in.

What do you think about this?

#codberg #cod #forgejo #iocaine

Wir haben fleißige Fische in New York

#codberg

Wir haben fleißige Fische in New York

#codberg

Wir haben fleißige Fische in New York

#codberg

Wir haben fleißige Fische in New York

#codberg

First project that uses project.nix: cod

You can find the source of project.nix on Codberg: https://codberg.org/jak2k/project.nix

#projectnix #codberg #devlog #nix #cod

First project that uses project.nix: cod

You can find the source of project.nix on Codberg: https://codberg.org/jak2k/project.nix

#projectnix #codberg #devlog #nix #cod

First project that uses project.nix: cod

You can find the source of project.nix on Codberg: https://codberg.org/jak2k/project.nix

#projectnix #codberg #devlog #nix #cod

First project that uses project.nix: cod

You can find the source of project.nix on Codberg: https://codberg.org/jak2k/project.nix

#projectnix #codberg #devlog #nix #cod

https://codberg.org/

You can sign in via Codeberg, I can sign in using my own SSO. Runners and a custom logo will be available in the future. There are no "e"s.

#cod #codberg #forgejo #codeberg

https://codberg.org/

You can sign in via Codeberg, I can sign in using my own SSO. Runners and a custom logo will be available in the future. There are no "e"s.

#cod #codberg #forgejo #codeberg

https://codberg.org/

You can sign in via Codeberg, I can sign in using my own SSO. Runners and a custom logo will be available in the future. There are no "e"s.

#cod #codberg #forgejo #codeberg

https://codberg.org/

You can sign in via Codeberg, I can sign in using my own SSO. Runners and a custom logo will be available in the future. There are no "e"s.

#cod #codberg #forgejo #codeberg

@mondstern ... interessant! Am Beispiel der @mintapps könnte ich verschiedene Werte in Badges visualisieren (z.B. auf der Instanz meiner Homepage). Mir fallen spontan ein: die Anzahl an verfügbaren Sprachen, die Anzahl an geschlossen Issues, die Anzahl an Apps im Projekt, die aktuelle Release-Nummer, die Tage bis zum nächsten Release... Die Werte würden sich jeweils automatisch aktualisieren (indem sie die Infos von anderer Stelle, z.B. #codberg, holen).

@mondstern ... interessant! Am Beispiel der @mintapps könnte ich verschiedene Werte in Badges visualisieren (z.B. auf der Instanz meiner Homepage). Mir fallen spontan ein: die Anzahl an verfügbaren Sprachen, die Anzahl an geschlossen Issues, die Anzahl an Apps im Projekt, die aktuelle Release-Nummer, die Tage bis zum nächsten Release... Die Werte würden sich jeweils automatisch aktualisieren (indem sie die Infos von anderer Stelle, z.B. #codberg, holen).