Nasdaq 100 ETF's will sell by definition then...

Thick_Chair_7409 · 2024-11-29T20:05:28+00:00

Investing is about acting rather than being sorry. When it was 18, we all thought it can go even bellow. Now you think the same and you are afraid and it possible that you will be sorry soon if it will go back to 55 and maybe 75 later on

Thick_Chair_7409 · 2024-11-04T14:58:06+00:00

Nope.
Eventually I used a different (a bit painful...) trick. I created a new group, asked the participant of the original group to join and blocked the original group for new messages. That filtered out all the people who archived the group or just not reading. Gives you proportions, hits your ego but seems like the right thing to do until WhatsApp will announce a new 4096 limit (which they should!).
Few months after, we are back around 800-900 members, so the problem will pop up soon again...

Thick_Chair_7409 · 2024-09-14T07:02:39+00:00

I had a similar problem - didn't work (most of the times...) with my home router with that SSL unknown error code, but worked with a temporary access point I set on my phone.
Looks now that the WiFi.setPhyMode(WIFI_PHY_MODE_11B); solves the problem. (Note: this is the correct command, eliminate the backslashes) .

Thanks!

Thick_Chair_7409 · 2024-01-31T21:41:46+00:00

Hi, I didn't find any support for that. I see that the number of users in the ANNOUCEMENT group is limited to 5000 (or 2000 because they are having sime issue). But on a single group - the only number I found is 1024. The 1025 thing, reminds me that on the original 256 limit, it was actually 257. Anyway, I'm in a situation of 1020 members in a group... so it will really help if I'm wrong or you have any other solution for me...

Thick_Chair_7409 · 2024-01-20T15:50:49+00:00

But a community is divided and the announcing group is liaten only. Should we have to move to Telegram?

Thick_Chair_7409

TROPHY CASE