I personally use a desktop computer over a starlink interface and I follow about 170 people. Right now I'm connected to 31 relays, which is far fewer connections than this computer can make. So it is working great for me.
But I recognize that younger people tend to only have a smartphone and fewer people use desktop computers. And I recognize some people want to follow thousands of other people. That is a difficult thing to make work well in a direct fashion under the outbox/inbox model.
But it can work indirectly. One solution is using a client proxy (which hodlbod (npub1jlr…ynqn) and I speak about briefly on his podcast that will be coming out in a week or so) which is basically an internet server which acts like a client on your behalf on the outside, and presents like a relay on the inside so that your mobile app only needs to make one connection. That can be done right now with zero changes to the NIPs, using the inbox/outbox model, and it solves that mobile phone problem far better than (1) blasting events everywhere, or (2) everybody centralizing on the same relays. Sure, most people won't be running their own client proxy, they will sign up as a customer to a client proxy service. But they can easily move to a different one if the one they are using starts censoring them. And us hacker do-it-yourself types retain the option of running direct.
Mazin (npub18kz…x5sz)
M. Dilger /
npub1ac…9p35c
2023-11-29 20:29:38
in reply to nevent1q…w746
Author Public Key
npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35cPublished at
2023-11-29 20:29:38Event JSON
{
"id": "8c24f5bbaebebee55913f0cff58ed307153ddf4e3f7978cea768f42dd5a66e7f",
"pubkey": "ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"created_at": 1701289778,
"kind": 1,
"tags": [
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
],
[
"p",
"3d842afecd5e293f28b6627933704a3fb8ce153aa91d790ab11f6a752d44a42d"
],
[
"p",
"0c99877612291bd818b3dd92f2852b823557b3744c3cb10470865c7a56a4929b"
],
[
"p",
"a3eb29554bd27fca7f53f66272e4bb59d066f2f31708cf341540cb4729fbd841"
],
[
"p",
"1739d937dc8c0c7370aa27585938c119e25c41f6c441a5d34c6d38503e3136ef"
],
[
"e",
"615511074de45ab7cb4a2eb2b1d0a75e6c2a533ba6156c64338bf13251c389ec",
"wss://nos.lol/",
"root"
],
[
"e",
"d927e5aa706db6777018dbf904589e0ca028a438064f54c2f9cd2c66ebeb38c3",
"wss://nos.lol/",
"reply"
]
],
"content": "I personally use a desktop computer over a starlink interface and I follow about 170 people. Right now I'm connected to 31 relays, which is far fewer connections than this computer can make. So it is working great for me.\n\nBut I recognize that younger people tend to only have a smartphone and fewer people use desktop computers. And I recognize some people want to follow thousands of other people. That is a difficult thing to make work well in a direct fashion under the outbox/inbox model.\n\nBut it can work indirectly. One solution is using a client proxy (which nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn and I speak about briefly on his podcast that will be coming out in a week or so) which is basically an internet server which acts like a client on your behalf on the outside, and presents like a relay on the inside so that your mobile app only needs to make one connection. That can be done right now with zero changes to the NIPs, using the inbox/outbox model, and it solves that mobile phone problem far better than (1) blasting events everywhere, or (2) everybody centralizing on the same relays. Sure, most people won't be running their own client proxy, they will sign up as a customer to a client proxy service. But they can easily move to a different one if the one they are using starts censoring them. And us hacker do-it-yourself types retain the option of running direct.\n\nnostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz",
"sig": "1125b43a338a1ce81f8b33d10c25ca4c1191c42dc039e5ba84f75b50b58ea4b87c79f64b4012d9ae42a9aef5e873866b277c6cc069b0456f21bdafe45ea191dd"
}