I read vol1. Didnt know about vol2
It sounds like this is a posix-sockets layer capability. On the other hand, each open socket requires a open file handle, so it can be constrained in limits.conf
Here is what gpt4 says:
"In TCP/IP networking, a connection is uniquely identified by a tuple consisting of the source IP address, source port, destination IP address, and destination port. While the port number is a 16-bit number, limiting the number of ports to 65,536 per IP address, the distinction between connections is made based on the combination of these four elements, not just the port number."
I'm not sure if thats how websockets works, by assigning a tcp port to each connection but then again its been over 30 years since I read my favorite 800 page volume on TCP/IP from the library.
I don't think there is a limit. So up to 64k or whatever the OS supports. This is the config struct for the library:
https://docs.rs/tungstenite/0.21.0/tungstenite/protocol/struct.WebSocketConfig.html
So I guess you can't set a limit?
I was thinking more along the line of the maximum number of open connections/simultaneous clients which would be spawned by your wait/listen thread and either you would have a maximum number of threads or a maximum number of tracked connections if they are controlled by the main port/socket listening thread.
I don't read rust and havent worked with wrbsockets in C or cpp, (only in python) and havent investigated high volume websockets service architecture. My main language is C and cpp.
In any case, your main program would have a way of knowing how many sockets its serving I would imagine. Of course, if it rejects connections from unauthenticated clients, this is a moot point. If it is designed to serve up public outboxes from authenticated users, theoretically ten posters, each with 1000 active followers, could balloon to 10k open sockets. Multiply that by 10 or 100, and connection handling architecture can get to be a problem if there are 1M threads.
I'm doing allot of counting angels on the head of a pin here. Is there a separate thread allocated to each websocket? Does your pre-banning scheme avoid ddos, or intentional websocket/process overloads?
In my use-case, its highly unlikely to be a real concern.
How many concurrent websockets does it support? Is there a limit that can be set, lets say by a RAM or CPU metric?
1. The markets attempt to price in the halvening (now)
2. BTC enters halvening at or near all time highs.
3. Some miner businesses, about 20% operating near margin, lose their pants from the reduced reward.
4. Loss of a few mining companies starts FUD and all mining companies lose funding, causing an avalanche around "bitcoin tech"
5. Exchanges like coinbase lose their inflated P/E, and the bottom falls out of COIN and MSTR
6. Poorly performing companies holding massive amounts of crypto lose talent and cyber security competancy collapses from fleeing employees
7. Coinbase is social-hacked, possibly from state sponsored blackhats, and the ETFs lose their bags to theft. The ETFs are shut down.
8. Bitcoin becomes perceived as something that can never be secured for the purpose of financial markets and FUD ensues
9. The bottom falls out of the BTC markets and it goes on a year-long firesale
10. People like Michael Saylor continue to hold bags and double or triple their holdings.
11. The US government passes legislation allowing a new dedicated cryptosecurity agency to surveil and prosecute global crypto theives
12. The cryptosecurity agency (conveniently) recovers the BTC stolen from coinbase
13. The financial markets see this as the equivalent of the FDIC for crypto and the ETFs are reopened.
14. Within 6 months BTC pumps to $1M
Strfry is too plain jane for me, requires too much programming to do anything meaningful. Looking for more plug and play personal relay solution that can be expanded for friends and family. From your description, its probably more appropriate. Do you have a fail2ban filter sample for use with chrous, for example from unauthenticated clients?
I'm feeling like I should switch to nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c's relay at this point
How do i fix it on apache2?
Relays are being taken down by a zero-day
#bitcoin or bust. Don’t gamble in shitcoins 💩 https://video.nostr.build/dd70c1c424905a2d7ef2c9d963304255609108a1747b187825027ce7b1e4e700.mp4
Ouch
Here's an important to #reframe for #parenting. Rather than looking at misbehavior as disobedience, think of it as a failure to resist temptation.
What is his definition of "open source devs"? Do you mean he said that the ETF shouldn't be writing checks to bitcoin devs?
The Tom Woods Show: Ep. 2473 Javier #Milei Update: How He's Doing Against the Bad Guys
Episode webpage: https://podtrac.com/pts/redirect.mp3/traffic.libsyn.com/secure/tomwoodsshow/woods_2024_04_03.mp3
That was my first impression of him
Its the L337 hour.
May the eclipse begin
The CIA is trying to poison you. Wordle is a psyop
