@fiatjaf
Relays (4)
- wss://inbox.relays.land/ – read
- wss://pyramid.fiatjaf.com/ – write
- wss://relay.westernbtc.com/ – write
- wss://pyramid.fiatjaf.com/inbox – read
Recent Notes
Yes, everything is in that ./data folder.
The mmmm.lock file should get removed automatically when the server stops, but it might hang there if it crashed or other mysterious circumstances. You can just delete it (as long as you're sure you're not going to run two instances of pyramid at the same time with the same database).
The mmmm.lock file should get removed automatically when the server stops, but it might hang there if it crashed or other mysterious circumstances. You can just delete it (as long as you're sure you're not going to run two instances of pyramid at the same time with the same database).
What is "raw blossom"?
If you done the installation using the easy method then you probably don't have to do anything, SFTP should just work.
Otherwise I think you must ensure you're listening on 0.0.0.0, I'm not sure.
If you done the installation using the easy method then you probably don't have to do anything, SFTP should just work.
Otherwise I think you must ensure you're listening on 0.0.0.0, I'm not sure.
Pretty good solution indeed.
By the way, this is something Radicle probably can't do without overcomplicating everything with encryption, but on Nostr it can be easily done on the relay side. I have that flow on https://pyramid.fiatjaf.com/moderated/ (disabled on that instance). It's not integrated with the git/grasp server yet, but will be.
By the way, this is something Radicle probably can't do without overcomplicating everything with encryption, but on Nostr it can be easily done on the relay side. I have that flow on https://pyramid.fiatjaf.com/moderated/ (disabled on that instance). It's not integrated with the git/grasp server yet, but will be.
Or maybe I don't understand what exactly you mean by "moderation tools". You said it can't be just the ability to ban a specific person, so what could it be?
What comes to my mind is something like:
- allow friends-of-friends of maintainers to send issues/patches/etc;
- if you're not in the friend-of-friend whitelist you have to pass some arbitrary criteria like, I don't know, paying some satoshis, burning your CPU a little, passing a captcha or doing a phone KYC with some trusted server (all bad solutions, but what can I do);
- allow blocking specific people that pass the criteria above.
What comes to my mind is something like:
- allow friends-of-friends of maintainers to send issues/patches/etc;
- if you're not in the friend-of-friend whitelist you have to pass some arbitrary criteria like, I don't know, paying some satoshis, burning your CPU a little, passing a captcha or doing a phone KYC with some trusted server (all bad solutions, but what can I do);
- allow blocking specific people that pass the criteria above.
Doesn't letting anyone submit an issue by just filling a captcha negate all the moderation stuff?
All I see is a moving purple dot. I think it is trying to hypnotize me.
ahahah, how was your experience?
This stuff happens by default on GitHub (and similar places) because GitHub (and similar places) gives everybody the illusion that every user is equally legitimate once they've passed the initial phone KYC sign up process.
In Nostr there is no entity to say who is a valid user and who isn't, so in the long run everybody is forced to use some kind of filter, otherwise they will drown in spam.
I believe the best simple method for such filtering, when browsing an unknown place like a thread on someone else's profile (or git repository), is to only fetch stuff (replies, reactions, proposed patches etc) from the relays announced by the profile/repository you're browsing.
Assuming software is made to use that filtering method the default, then it becomes trivial for the repository owners to control whose comments get to show up to an unwary passerby.
In Nostr there is no entity to say who is a valid user and who isn't, so in the long run everybody is forced to use some kind of filter, otherwise they will drown in spam.
I believe the best simple method for such filtering, when browsing an unknown place like a thread on someone else's profile (or git repository), is to only fetch stuff (replies, reactions, proposed patches etc) from the relays announced by the profile/repository you're browsing.
Assuming software is made to use that filtering method the default, then it becomes trivial for the repository owners to control whose comments get to show up to an unwary passerby.
Has anyone tried to run Radicle? Am I the only incapable person who can't even clone their main source repository using their own product following the tutorial?
What is that one?