I was wondering the same. I suspect it has to do with the initial hack needing it since it relies on the general sibling selector (~) which selects all following siblings but no preceding siblings, so it is important to catch the very first element and all its following siblings:
li:nth-last-child(n + 5),
li:nth-last-child(n + 5) ~ li
I don’t think :has has such limitation and I think a simple :has(:nth-child(5)) would yield the same results as :has(:nth-last-child(n + 5)). :nth-last-child(n + 5) will select the first element among five or more siblings, and :nth-child(5) will simply select the fifth element if it exists. I see no reason to write the former over the latter when you’re just wrapping it inside a :has.
Great initiative! I was wondering if you could kindly provide me with a comparison of how this initiative compares with Langchain? Additionally, I have observed that there are numerous libraries available along with GPT, however, none of them seem to be production-ready and seem to be intended only for hobbyists. Would you kindly elaborate on your plan to address this issue? Thank you very much!
groups is weird, the media have the index encrypted but the contents use a shared app key.
commercial accounts are also odd. it's encrypted with the business and whatsapp keys, so employees from both can read the messages.
then here there's the api issues. you are not using a full client, but sending your access token plus the plain text message for it to be encrypted on their servers.
even worse, in this example it's not even you using the api, but you are using twillo's api, who then uses metabook's api for whatsbook. so it's plain text all the way across those.
