Nostr View

GitCitadel @GitCitadel - 30d

Hello, fellow Nostriches. We at #GitCitadel have spent this week pricing out remote servers and brainstorming; considering the most cost-effective, but still performant, way to implement a public #gitserver based upon Nostr. In order to help us front the rental fees and lower the price to individual npubs, we have begun a new https://Geyser.fund goal. The resulting server will have multiple #gnostr implementations and tools on it. We are planning to begin with: * the #GitRepublic API, that will make it possible to log in to git with your Nostr signer, and will trade out e-mail communication with Nostr notes, * an HTTP-based git server (the first thing that will be going online, so that everyone can move or mirror their repos), * a paid AUTH relay https://gitcitadel.nostr1.com (currently 5000 sats/month, to cover all the running costs, but we hope to bring that down dramatically, due to your donations), * an #Alexandria instance focused on technical documentation and styled for the dev users, * and an instance of https://GitWorkshop.dev that displays the repos on the server. It's difficult to compete with a "free" public service, like GitHub or Codeberg, but we're hoping that tighter integration with Nostr will add some value to the developers using it, and for the public interested in browsing the PoW stored on it. Through the integration of Nostr and Lightning, we are leaning into the comfortable, Nostrized, friction-free logins, and will facilitate V4V payments for Nostr's hard-working devs. Many thanks in advance. And may you have a good morning.

1
0
3

Silberengel @Silberengel - 30d

nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h is already hard at work, sketching up a way to make the relay a comfortable payment interface for this project. We have been grateful for his assistance with billing and user-management of #Alexandria, over the https://theforest.nostr1.com relay, and we're going to use a similar setup here. We will have a separate workflow for iOS users, over Lightning, but it will feed into the same user list. That way, we can concentrate on our core #GitRepublic project mission: onboarding FOSS repos to Nostr.

0
0
3

Silberengel @Silberengel - 30d

First, we set up the git server and the relay, and use repo events and Lightning and etc.. That's the part that's sort of low-hanging fruit and is just a question of renting the server and hosting the machine and maintaining uptime and fighting off attacks and scrapers and... You know the drill. That's the part the goal drive is for, because that takes the uncertainty out of our paying in advance and the support work. The API will do more than that. That's part of our development project and will need more design work. We want to integrate with other git APIs, to bring those interactions onto Nostr, as well.

0
0
3

Silberengel @Silberengel - 30d

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:

0
0
3

Silberengel @Silberengel - 30d

Yeah, nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 is looking into that. They attack his home servers, as well.

1
0
3

mleku @mleku - 29d

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

1
0
3

Silberengel @Silberengel - 29d

I'm assuming your first-level WoT can auth and get around delays. Otherwise, uploading publications would collapse.

1
0
3

mleku @mleku - 29d

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

1
1
3

Silberengel @Silberengel - 29d

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*

0
0
3

mleku @mleku - 29d

ok, so it's not you! no problem, it seems like you put a lot of thought into doing that right yeah, the behaviour i have observed from this one particular spider is super tarded, you are just the only person i know who is doing WoT analytics so whoever it is, shame on them, for being retarded

1
1
3

mleku @mleku - 29d

also, it's grabbing kind 0 and 10002 so it's definitely not you

1
1
3

mleku @mleku - 29d

i mean, 0, 3, 10002 and there's one more, i forget which

0
1
3

mleku @mleku - 29d

another example of how "dumb relays" is dumb and DVMs well haha never mind that... this is why i'm making a modular and extensible HTTP API for nostr, all that "DVM" stuff can become simply modules on a relay

0
1
3

Silberengel @Silberengel - 29d

I really don't understand client-side crawling on a public data store.

1
0
3

mleku @mleku - 29d

if subscriptions are available they are much more efficient otherwise it's just mirroring... squared

0
1
3

mleku @mleku - 29d

https://mleku.realy.lol/api it's already live

1
1
3

mleku @mleku - 29d

i'm adding a HTTP SSE powered subscribe function right now and then i'm digging into the problem of raitelimiting

1
1
3

Silberengel @Silberengel - 29d

It's got a full web interface. 😎

1
0
3

Silberengel @Silberengel - 29d

I'm going to give you a ticket for making the interface more reactive. That's fun and makes it easier to use on a reduced screen size. We can fight about it in the ticket. 😁

1
0
3

mleku @mleku - 29d

haha, yes in the https://huma.rocks documentation they talk about how you can load other UIs as well as using different CSS and whatnot, it's not really my thing but it isn't nice for a 1280 wide display likek my side-monitor (2k monitor in portrait) if you were to do some little homework to scope out other options for RESTful UIs i most likely can switch it, this is just the default for Huma

1
1
3

mleku @mleku - 29d

i'll look into it after i have done the rate limit problem properly, that's gonna be a bit of work, maybe a day or two

1
1
3
Showing page 1 of 1 pages