Re: GNUnet 0.26.x release and active peers?

The bigger problem is that every link to NEWS and (git) ChangeLog in
our release announcement(s) are now broken...

I also would have not put those links in there if there was a paywall.
I think that would convey a bad image.

So we have two issues: Deal with the old broken links properly and
decide what to put into announcements in the future.

I guess for the future we can simply not link anything anymore to git
web... (we could provide commands to look at the git log I guess...).
But breaking the old links is not ideal.
We could instead point the web git.gnunet.org to a static page on
www.gnunet.org that explains that we do not provide it (anymore) and
link to cgit-paywalldemo.gnunet.org in the future.

FWIW I restartet the bootstrap peer and was able to connect.

BR

Am Freitag, dem 19.12.2025 um 07:52 +0100 schrieb Christian Grothoff:
> Yeah, Anubis didn't work, I can only assume we had a botnet working
> for=20
> the AIs solving PoWs, that'd also explain the diversity of IP
> addresses.
>=20
> Anyway, my current solution was to change the DNS name to git-www and
> to=20
> start work on Paivana to put a GNU Taler-based paywall in front of
> the=20
> Git-Web in the future, hopefully ready before the Bots discover the
> new=20
> domain name...
>=20
> Basic auth was very unpopular, so let's see if Paivana will be
> better.=20
> But first I have to find the time to implement it...
>=20
> Cheers!
>=20
> Christian
>=20
> On 12/17/25 2:44 PM, Martin Schanzenbach wrote:
> > Hi,
> >=20
> > due to sustained bot attacks against git.gnunet.org we had to
> > temporarily "disable" cgit.
> > @grothoff: maybe we try the login method again? Obviously Anubis
> > did
> > not work I guess?
> >=20
> > Regarding the peer: I will look into it. Maybe the bootstrap peer
> > is
> > down. I was/am a bit preoccupied recently ;)
> >=20
> > BR
> > Martin