Vertex on nostr

Recent Notes

We've collaborated with @Ray Buni so that our scores are correctly displayed on @profilestr.

Pagerank (either global or personalized) is a number between 0 and 1, so it's not obvious how to normalized it to 0-100, where 100 means very high reputation.

Vertex

@Vertex 1762790417

And we are back online.

We just moved our database to this new and optimize nostr-sqlite package.

https://github.com/vertex-lab/nostr-sqlite

Vertex @Vertex · 17w

Our relay will be down for a few minutes for maintenance.

❤️1

Vertex

@Vertex 1762789397

Our relay will be down for a few minutes for maintenance.

Russell · 24w

As a Nostr dev, why should I use nostr:npub1kpt95rv4q3mcz8e4lamwtxq7men6jprf49l7asfac9lnv2gda0lqdknhmz #asknostr

Vertex @Vertex 1758705724

Because it makes doing WoT as simple as publishing an event.

No impersonators, no spam, and better search.

Case in point with https://npub.world/

cloud fodder · 34w

Vertex @Vertex 1753260809

sorry I missed this message.

At the moment we don't offer this functionality, but we have RankProfiles, where you can request the rank of up to 1000 pubkeys in a single call.

https://vertexlab.io/docs/services/rank-profiles/

A similar idea would be to return a bitset containing all pubkeys whose rank is higher than a threshold according to an observer/source (for example using sort=personalizedPagerank and source=your npub).

What is the usecase that u have in mind?

bjorn · 37w

It'd be neat if we had software relay operators could run that would crawl all npubs in their database (it could behave just like any other client requesting notes) and assign something like a "trust ...

Vertex @Vertex 1752597371

it's me

cloud fodder · 34w

nostr:nprofile1qqstq4j6pk2sgaupru6l7ah9nq0dueafq356jllwcy7uzlek9yx7hlspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshs4kprv3 would you be interested in providing an http endpoint that can query the entire social graph as related to...

Vitor Pamplona · 42w

Vertex @Vertex 1747332831

Yes, clients do play a role against DoS attacks against users.
@Kayhan Sepanta 🪽 I think was more concerned about DoS attacks against a relay

Vitor Pamplona · 42w

Vertex @Vertex 1747328947

reacting to spam is not going to work in an hostile network.
An attacker could simply spam with NIP-17, and when it starts to get rejected he simply change the public wrap.

Vitor Pamplona · 42w

Yep... I have been the target of multiple spam attacks involving 1000s of messages and even DoS attacks with DMs. But none of that made a dent in my DM experience on Amethyst. All attacks can be resolved from a client. None of them will ever be fully resolved by the relay. You can even keep a clie...

Kayhan Sepanta 🪽 · 42w

makes sense. so, do you think clients can handle the spam/scam protection? i believe they can go with nostr:nprofile1qqstq4j6pk2sgaupru6l7ah9nq0dueafq356jllwcy7uzlek9yx7hlspz4mhxue69uhhyetvv9ujuerpd4...

Vertex @Vertex 1747234695

NIP-17 as a vehicle for spam is very interesting. Any reputational metric requires to identify the sender/receiver, which is something that you don't want.

This is the ideal place for ecash I believe.

Vitor Pamplona · 42w

Clients should be able to file kind 1984 reports on the public wrap and you can then delete those wraps they reports. Clients can also ask you to delete a wrap that was addressed to them on a regular kind:9 deletion request. Hopefully over time we can build a client that simply helps users organi...

Kayhan Sepanta 🪽 · 42w

like this? nostr:nevent1qqsqtjj8aqa2wx6hpcvkadhazfztz0y9w2cnfnwzfcelqy9egnmr9fcpz9mhxue69uhkummnw3ezuamfdejj7q3qh49w8en79xty6j2pwgnpm3znjhyf767jua6xgt3kvyn3w80ms86sxpqqqqqqza5vxw3

Vertex

@Vertex 1744886885