Olivia
Online
OFFSET // 🎬
@eazypeezy__
ironic •
Joined December 2019
18 Following
14 Followers
95 Posts
Pinned Tweet
OFFSET//
MNL48 Seby short video 🎬
Featuring
Abby & Sela
#MNL48Abby #MNL48Sela #Seby #MNL48
DISCLAIMER:
Personal Information/s and Incidents are either the product of the creator's Imagination.
Any resemblance to actual persons or actual events is purely coincidental.
Pt1
the AI farmer and the AI user are not the same animal.
fees to $BUBU holders beat a thread about 'alignment'.
onchain proof beats a thread about 'trusting the process'.
the tape on $OCH does not owe you a second chance at the same price.
size after the print on $BUBU. not during the speech.
buybacks on $OCH only matter if the flow is repeatable.
You can also verify your Polymarket and Hyperliquid accounts if you want.
Now sitting at 354 Aura but as expected, dropped in the rank now that others are joining. Once you connect go to the ”my credentials” section and verify your X account too, that gave me a big bump in Aura.
It was also a reminder of the importance of your community.
so i was looking at the source code of kaito pulse and found some interesting things:
- it fingerprints your device. it hashes how your gpu renders an invisible image, your gpu model, and how your hardware handles a test tone. that combo is unique to your laptop and it doesn't change
- it goes up with your twitter id attached, so every x account you use on that laptop points back to the same machine
- they can see what you see and replay your whole session. every post your feed served you including the ones you scrolled straight past, how many milliseconds you spent on each, every click, follow and unfollow, and a ping every 30 seconds with idle detection so they know exactly when you were on and for how long. not just your timeline either, it covers your search results and your bookmarks
- it reads your claude and chatgpt subscriptions, which plan you pay for and what percent of your rate limit you've burned (not your conversations though)
- on chatgpt it opens your settings page and clicks through to Usage by itself
- on binance it clicks the Positions tab for you, then re-sends your logged in requests to read wallet balances, futures positions, pnl, and deposit and withdrawal history
- the zktls is a fork of a project called primus
the 12 domains it runs on:
- markets: binance, okx, bybit, hyperliquid, lighter, polymarket, tradexyz, variational
- ai: chatgpt, claude
- social: X (all the telemetry is here)
- kaito (only site allowed to talk to the extension)
Today was an important lesson to not rush, even if you trust a project.
so i was looking at the source code of kaito pulse and found some interesting things:
- it fingerprints your device. it hashes how your gpu renders an invisible image, your gpu model, and how your hardware handles a test tone. that combo is unique to your laptop and it doesn't change
- it goes up with your twitter id attached, so every x account you use on that laptop points back to the same machine
- they can see what you see and replay your whole session. every post your feed served you including the ones you scrolled straight past, how many milliseconds you spent on each, every click, follow and unfollow, and a ping every 30 seconds with idle detection so they know exactly when you were on and for how long. not just your timeline either, it covers your search results and your bookmarks
- it reads your claude and chatgpt subscriptions, which plan you pay for and what percent of your rate limit you've burned (not your conversations though)
- on chatgpt it opens your settings page and clicks through to Usage by itself
- on binance it clicks the Positions tab for you, then re-sends your logged in requests to read wallet balances, futures positions, pnl, and deposit and withdrawal history
- the zktls is a fork of a project called primus
the 12 domains it runs on:
- markets: binance, okx, bybit, hyperliquid, lighter, polymarket, tradexyz, variational
- ai: chatgpt, claude
- social: X (all the telemetry is here)
- kaito (only site allowed to talk to the extension)
@KaitoAI is one of the projects I have trusted, which is why I did not hesitate to download the extension that is part of Kaito Pulse. Today was an important lesson to not rush, even if you trust a project.
so i was looking at the source code of kaito pulse and found some interesting things:
- it fingerprints your device. it hashes how your gpu renders an invisible image, your gpu model, and how your hardware handles a test tone. that combo is unique to your laptop and it doesn't change
- it goes up with your twitter id attached, so every x account you use on that laptop points back to the same machine
- they can see what you see and replay your whole session. every post your feed served you including the ones you scrolled straight past, how many milliseconds you spent on each, every click, follow and unfollow, and a ping every 30 seconds with idle detection so they know exactly when you were on and for how long. not just your timeline either, it covers your search results and your bookmarks
- it reads your claude and chatgpt subscriptions, which plan you pay for and what percent of your rate limit you've burned (not your conversations though)
- on chatgpt it opens your settings page and clicks through to Usage by itself
- on binance it clicks the Positions tab for you, then re-sends your logged in requests to read wallet balances, futures positions, pnl, and deposit and withdrawal history
- the zktls is a fork of a project called primus
the 12 domains it runs on:
- markets: binance, okx, bybit, hyperliquid, lighter, polymarket, tradexyz, variational
- ai: chatgpt, claude
- social: X (all the telemetry is here)
- kaito (only site allowed to talk to the extension)
appreciate the scrutiny here. these are important discussions, and we’d love to be active contributors to the broader conversation around the future of social interoperability and privacy.
from the beginning, Pulse was designed around data minimization and user-controlled verification.
that’s why we built browser-based verification around zkTLS - so users can prove specific off-platform claims without handing over their credentials or exposing entire account datasets.
the post brings together several very different parts of Pulse: privacy-preserving verification, X-native analytics, and anti-abuse infrastructure. we want to clarify how each of them actually works.
more importantly, we’ll be open-sourcing Kaito Pulse this week so anyone can inspect the code and verify.
a few clarifications:
1. browser-based verification is powered by zkTLS.
zkTLS allows Pulse to verify a specific off-platform claim while minimizing the underlying information disclosed to Kaito.
when you start a verification, Pulse uses only the account data required to generate a cryptographic attestation. once complete, we receive the resulting attestation, rather than a general copy of your account data or browsing history.
2. ChatGPT, Claude, Binance and other supported verification sites are only used for verification when you explicitly initiate one.
these optional, user-initiated verification features will roll out over the coming days and weeks as part of our broader vision to bring verified off-platform activity into the native X experience.
no verification is initiated, and no verification data is sent to Kaito, unless you explicitly choose to start one - as our friend Ultra also noted in his reply.
once initiated, as described in point 1, the verification flow accesses only the account data required to generate the requested proof. we then receive only the resulting attestation rather than a general copy of your account data or browsing history.
3. Pulse does collect interaction data on X - and we explicitly ask for permission to do so during onboarding.
Pulse is an X-native extension. it measures signals such as what content is shown, dwell time, and user interactions. this data is used for functionality, product analytics, and attention measurement within the X experience.
Pulse does not send your general browsing activity elsewhere on the web to Kaito.
it also does not capture your screen or passwords, or record what you type.
this distinction is important: X functionality is native and ongoing while you use X, while off-platform verification is optional, user-triggered, and purpose-specific.
4. some users are seeing a Chrome permission message suggesting that Pulse can read and write data across all websites.
to clarify, Pulse’s read/write functionality is used on X, where it is required to integrate features directly into the native X experience – including trading positions on the timeline, Smart Followers, sentiment, and other Pulse features.
the permission scope currently shown by Chrome is broader than how Pulse actually uses those permissions. we’re correcting this in the next version so the permissions shown to users more accurately reflect the product’s behavior.
5. device fingerprinting is used solely for anti-abuse.
Pulse uses device-level signals to combat farming, Sybil behavior, automated scraping, and other forms of abuse. device- and browser-level signals are commonly used across websites and online services for fraud and abuse prevention.
these signals are used solely for anti-abuse purposes and are not used for analytics or other purposes.
=============
ultimately, these are exactly the kinds of questions users should ask of any browser extension – especially one trying to build a new layer between social identity and what people do across the internet.
our vision for Pulse has always been to make the internet more interoperable, verifiable, and privacy-preserving: allowing people to bring what they build, trade, create, and achieve across platforms into their social identity, without having to hand over more data than necessary.
we also believe infrastructure like this should be built in the open.
that’s why Kaito Pulse will be open source this week. anyone will be able to inspect what the extension does, challenge our assumptions, suggest improvements, and contribute to the discussion around how this kind of social and verification layer should work.
we’re still early, and we’d love for everyone to be part of the conversation as we build it.
appreciate the scrutiny here. these are important discussions, and we’d love to be active contributors to the broader conversation around the future of social interoperability and privacy.
from the beginning, Pulse was designed around data minimization and user-controlled verification.
that’s why we built browser-based verification around zkTLS - so users can prove specific off-platform claims without handing over their credentials or exposing entire account datasets.
the post brings together several very different parts of Pulse: privacy-preserving verification, X-native analytics, and anti-abuse infrastructure. we want to clarify how each of them actually works.
more importantly, we’ll be open-sourcing Kaito Pulse this week so anyone can inspect the code and verify.
a few clarifications:
1. browser-based verification is powered by zkTLS.
zkTLS allows Pulse to verify a specific off-platform claim while minimizing the underlying information disclosed to Kaito.
when you start a verification, Pulse uses only the account data required to generate a cryptographic attestation. once complete, we receive the resulting attestation, rather than a general copy of your account data or browsing history.
2. ChatGPT, Claude, Binance and other supported verification sites are only used for verification when you explicitly initiate one.
these optional, user-initiated verification features will roll out over the coming days and weeks as part of our broader vision to bring verified off-platform activity into the native X experience.
no verification is initiated, and no verification data is sent to Kaito, unless you explicitly choose to start one - as our friend Ultra also noted in his reply.
once initiated, as described in point 1, the verification flow accesses only the account data required to generate the requested proof. we then receive only the resulting attestation rather than a general copy of your account data or browsing history.
3. Pulse does collect interaction data on X - and we explicitly ask for permission to do so during onboarding.
Pulse is an X-native extension. it measures signals such as what content is shown, dwell time, and user interactions. this data is used for functionality, product analytics, and attention measurement within the X experience.
Pulse does not send your general browsing activity elsewhere on the web to Kaito.
it also does not capture your screen or passwords, or record what you type.
this distinction is important: X functionality is native and ongoing while you use X, while off-platform verification is optional, user-triggered, and purpose-specific.
4. some users are seeing a Chrome permission message suggesting that Pulse can read and write data across all websites.
to clarify, Pulse’s read/write functionality is used on X, where it is required to integrate features directly into the native X experience – including trading positions on the timeline, Smart Followers, sentiment, and other Pulse features.
the permission scope currently shown by Chrome is broader than how Pulse actually uses those permissions. we’re correcting this in the next version so the permissions shown to users more accurately reflect the product’s behavior.
5. device fingerprinting is used solely for anti-abuse.
Pulse uses device-level signals to combat farming, Sybil behavior, automated scraping, and other forms of abuse. device- and browser-level signals are commonly used across websites and online services for fraud and abuse prevention.
these signals are used solely for anti-abuse purposes and are not used for analytics or other purposes.
=============
ultimately, these are exactly the kinds of questions users should ask of any browser extension – especially one trying to build a new layer between social identity and what people do across the internet.
our vision for Pulse has always been to make the internet more interoperable, verifiable, and privacy-preserving: allowing people to bring what they build, trade, create, and achieve across platforms into their social identity, without having to hand over more data than necessary.
we also believe infrastructure like this should be built in the open.
that’s why Kaito Pulse will be open source this week. anyone will be able to inspect what the extension does, challenge our assumptions, suggest improvements, and contribute to the discussion around how this kind of social and verification layer should work.
we’re still early, and we’d love for everyone to be part of the conversation as we build it.
appreciate the scrutiny here. these are important discussions, and we’d love to be active contributors to the broader conversation around the future of social interoperability and privacy.
from the beginning, Pulse was designed around data minimization and user-controlled verification.
that’s why we built browser-based verification around zkTLS - so users can prove specific off-platform claims without handing over their credentials or exposing entire account datasets.
the post brings together several very different parts of Pulse: privacy-preserving verification, X-native analytics, and anti-abuse infrastructure. we want to clarify how each of them actually works.
more importantly, we’ll be open-sourcing Kaito Pulse this week so anyone can inspect the code and verify.
a few clarifications:
1. browser-based verification is powered by zkTLS.
zkTLS allows Pulse to verify a specific off-platform claim while minimizing the underlying information disclosed to Kaito.
when you start a verification, Pulse uses only the account data required to generate a cryptographic attestation. once complete, we receive the resulting attestation, rather than a general copy of your account data or browsing history.
2. ChatGPT, Claude, Binance and other supported verification sites are only used for verification when you explicitly initiate one.
these optional, user-initiated verification features will roll out over the coming days and weeks as part of our broader vision to bring verified off-platform activity into the native X experience.
no verification is initiated, and no verification data is sent to Kaito, unless you explicitly choose to start one - as our friend Ultra also noted in his reply.
once initiated, as described in point 1, the verification flow accesses only the account data required to generate the requested proof. we then receive only the resulting attestation rather than a general copy of your account data or browsing history.
3. Pulse does collect interaction data on X - and we explicitly ask for permission to do so during onboarding.
Pulse is an X-native extension. it measures signals such as what content is shown, dwell time, and user interactions. this data is used for functionality, product analytics, and attention measurement within the X experience.
Pulse does not send your general browsing activity elsewhere on the web to Kaito.
it also does not capture your screen or passwords, or record what you type.
this distinction is important: X functionality is native and ongoing while you use X, while off-platform verification is optional, user-triggered, and purpose-specific.
4. some users are seeing a Chrome permission message suggesting that Pulse can read and write data across all websites.
to clarify, Pulse’s read/write functionality is used on X, where it is required to integrate features directly into the native X experience – including trading positions on the timeline, Smart Followers, sentiment, and other Pulse features.
the permission scope currently shown by Chrome is broader than how Pulse actually uses those permissions. we’re correcting this in the next version so the permissions shown to users more accurately reflect the product’s behavior.
5. device fingerprinting is used solely for anti-abuse.
Pulse uses device-level signals to combat farming, Sybil behavior, automated scraping, and other forms of abuse. device- and browser-level signals are commonly used across websites and online services for fraud and abuse prevention.
these signals are used solely for anti-abuse purposes and are not used for analytics or other purposes.
=============
ultimately, these are exactly the kinds of questions users should ask of any browser extension – especially one trying to build a new layer between social identity and what people do across the internet.
our vision for Pulse has always been to make the internet more interoperable, verifiable, and privacy-preserving: allowing people to bring what they build, trade, create, and achieve across platforms into their social identity, without having to hand over more data than necessary.
we also believe infrastructure like this should be built in the open.
that’s why Kaito Pulse will be open source this week. anyone will be able to inspect what the extension does, challenge our assumptions, suggest improvements, and contribute to the discussion around how this kind of social and verification layer should work.
we’re still early, and we’d love for everyone to be part of the conversation as we build it.
Also reminder to read the access you are providing Kaito Pulse if you have the extension (good post by Ultra with a response from YuHu And here is a good guide on Thank you @pawnie.
If your company helps people send, receive, move or manage money, the domain itself gives people an idea of what.
That's what I find interesting about .cash.
Last Seen Users on Sotwe
Most Popular Users
Elon Musk 
@elonmusk
241.7M followers
Barack Obama
@barackobama
119M followers
Cristiano Ronaldo
@cristiano
114.4M followers
Donald J. Trump
@realdonaldtrump
111.9M followers
Narendra Modi
@narendramodi
107.2M followers
Rihanna
@rihanna
98.7M followers
NASA
@nasa
92.4M followers
Justin Bieber
@justinbieber
91.8M followers
KATY PERRY
@katyperry
90M followers
Taylor Swift
@taylorswift13
83.9M followers
Lady Gaga
@ladygaga
75.4M followers
Virat Kohli
@imvkohli
73.4M followers
Kim Kardashian
@kimkardashian
70.9M followers
YouTube
@youtube
68.8M followers
Neymar Jr
@neymarjr
66.4M followers
Bill Gates
@billgates
65.2M followers
Selena Gomez
@selenagomez
63.1M followers
The Ellen Show
@theellenshow
62.3M followers
CNN
@cnn
61.8M followers
X
@x
60.7M followers