Thanks. 🫂 Some users we're complaining that direct links don't work correctly, but they're definitely more convenient.
If anyone else is looking for a direct link: https://geyser.fund/project/gitcitadel/goals/478?hero=anthony
Discussion
Good luck! I can see that lots of folks are excited about this (or at least I got tagged in more than one giant thread about it). I’d certainly like to self-host GitServer in the future if it can run on a cheap VPS.
I know that to attract any sort of code contributions these days, you have to be on GitHub. A lot of devs won’t even touch GitLab or Codeberg, let alone self-hosted Git servers. Maybe Nostr can change the landscape a bit? Otherwise, even if it means mirroring my stuff to GitHub, it would be great to have Nostr-oriented infrastructure that Nostr devs can rely on.
Yeah, GitHub is the #1 way for devs to communicate, and Nostr devs aren't an exception. You basically HAVE to at least mirror something on there, or you don't exist.
They have a real strangehold on almost all development teams, on the whole planet, because they control everyone's repos and interactions. The same way Office 365 is nearly impossible to get away from, in the corporate world. Owning both of them is why Microsoft is so gigantic.
We can't compete with that level of centralization, but we're determined to offer a complete, professional, FOSS, decentralized setup, that can eventually be installed on lots of people's home or work servers. This gitserver is the Mother Server, so to say, and where we'll be beta testing everything, and will be SEO and AIO, but it should eventually just become one of many because relays mean that will all be able to look -- and interact with -- the same things from different places. Since we're such an infrastructure-focused project team, we decided that this could be our first big contribution to the effort.
Nostr wants to make git distributed again, and we support that message.
Shouldn't be too hard. 😁 Here is the competition, Nostr:
I forgot to hit send on this earlier today, but speaking of David vs. Goliath, if you haven’t done it already, make sure to tarpit Alexandria, TheForest1, GitCitadel, and anything else you’re deploying that is expected to hold a lot of data. Otherwise, scrapers will come for the goods, overload the infrastructure and cost you quite a few sats.
Yeah, nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 is looking into that. They attack his home servers, as well.
this stuff annoys the hell out of me too, i run my test #realy fairly infrequently but within minutes some bot is trying to scrape it for WoT relevant events, and i wish there was an effective thing to slow that down
i tried adding one kind of rate limiter but that didn't really work out so well, in the past what i've seen work best tends to be where the relay just stops aswering and dropping everything that comes in... probably if that included pings the other side would automatically drop
i've now added plain HTML and i think that requires something also but maybe more simple, like, if it gets a query more than once every 5 seconds for 5 such periods it steadily adds more and more delay in processing, the difference to sockets is to do it on http it has to associate with an IP address
I'm assuming your first-level WoT can auth and get around delays. Otherwise, uploading publications would collapse.
yeah, they are only reading, not writing, so all that would really be required is to slow them down
probably could split the direct followed vs follows of follows into two tiers also so that the second level of depth get less service quality
probably maybe should work on it today because this problem with scrapers is fairly annoying
it's only nostr WoT spiders at this point, i wish i could just suggest to the spider people to just open a subscription for these and catch all the new stuff live, that would be more efficient for them and less expensive for relay operators
at this point it's fairly early in the game for that stuff so maybe some education of WoT devs might help...
cc: nostr:npub176p7sup477k5738qhxx0hk2n0cty2k5je5uvalzvkvwmw4tltmeqw7vgup there is no point in doing sliding window spidering on events once you have the history, from then on just open a subscriptiion
this would be more friendly from the AI spiders if they had a way to just catch new updates, but unless dey pay me! i'm just gonna tarpit them
Yeah, I don't get the point of spidering data you can just stream. Like, they spider Nostr websites and it's like... just subscribe to the relay. *roll eyes*
Yeah right now I just have a user agent list and that does most of the work, the bots that are hitting me mostly have "~bot" in the user agent field so it's been working to stave them off for now. I have to hop in and update the list every few days it helps.
I was interested in rDNS lookups for blocking since most of the IPs i've dealt with come from rDNS bot sources like bytedance, openai and so on.
for the interim, what i'm doing (#realy is hosted also on the internal private gitcitadel onedev) you can add this to your repo in .git/config:
[remote "origin"]
url = git@github.com:mleku/realy.git
fetch = +refs/heads/*:refs/remotes/origin/*
pushurl = git@github.com:mleku/realy.git
pushurl = ssh://onedev.gitcitadel.eu:6611/auxiliary-devs/Realy-Relay
basically just put two `pushurl` lines with the two separate ones and voila
also, https://realy.lol is actually the declared import URL for my project, which redirects off my VPS and i can redirect that anywhere
what github has is mostly about discoverability, and nostr backed git hosting could flip the script, with more work done on relay search capabilities (already you can probably find them using the git nostr events being developed by gitcitadel)
GitHub is also big on Actions, and that's something we think would be interesting for premium customers.
yeah, that's CI/CD scripts... don't need to allocate huge capacity for that to start but eventually scalable providers (aka cloud) would help... but i'm not keen on giving microsoft, amazon or google our sats
Yeah, need critical mass to make a cloudservice payout. We'd probably need to rent from nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h eventually, but we're keeping him busy with relay stuff, right now.