@yongfook I think the social platforms will add that natively because it gives them more control over UGC, and otherwise, other apps will be able to monetize trends based on “future content.”
I just received a “gratitude” email from a “brand”:
"
Here’s a more human-like email you could send to your customers using your alias table:
Hello [Customer_name], this is Alex, the CEO of [Brand]. I wanted to personally reach out to thank you for being a loyal customer......”
The problem is I stopped being a customer years ago.
@florinpop17 People with this mindset are the first to get replaced by low-level AI.
You will compete with AI based on the expected value added, not the cost.
Yep, you must plan for these issues in your backend.
The case I mentioned involved a marketing widget reading user text input, leading to "embarrassing" medical ads, emails, and calls to his office after a data broker matched a visitor's IP and his office supply order from another website.
That's not how it works.
Will you be able to identify the IP address of a visitor to a medical SaaS, for example? (from your server log)
Are the messages end-to-end encrypted?
Will another widget, installed on the site, be able to read the text fields of your widget?
I'm asking because a friend is involved in a legal dispute over something similar.
@bepisfi@levelsio@saxobank You are a headache and unnecessary risk to them. Unless your account is big enough to warrant an expensive legal team involvement, they won't even bother reviewing your case manually.
We will be forced into IPv6 with the first wave of AIoT (AI of Things), as millions of AI-driven robots and standalone tools will drain all available IPv4 addresses in weeks.
The armies of robots running the factories won't be locally operated, and they will benefit from a hive-mind style continuous training and improvement through sharing of "feedback" via protocols that are being standardized (please contribute to open source research if you can).
Imagine this: an @amazon packaging robot in an autonomous warehouse will "teach" a @Tesla assembly humanoid that the Atlas Copco nutrunner shouldn't rattle like that and should be inspected and recalibrated.
This small loop will need 50 to 100 nodes to complete, and suddenly, the 128-bit IPv6 addresses start to seem unavoidable.