ManKnows

A Man That Knows

[ManKnows @Manknows]

@Whiskey_General @TheNorfolkLion It’ll do for £12 👍🏼

[ManKnows @Manknows]

@Whiskey_General @TheNorfolkLion DHGATE 😉

[The British Patriot @TheBritLad]

🚨BREAKING: The “taking the knee” trend has exploded across Britain.

Thousands are kneeling for Henry Nowak specifically to the track:

Michael Jackson “They Don’t Really Care About Us.”

The left are in a complete meltdown.

[ManKnows @Manknows]

MY BODY IS READY FOR VIBECLASH
https://t.co/yKFuYjosKJ

[vibe.market on vibechain.com @vibechain]

VIBEMARKET IS EVOLVING

JOIN THE WAITLIST AT https://t.co/4PY73Vv6TQ

VIBEMARKET USAGE = YOUR SPOT IN LINE

[𝒍𝒊𝒍𝒛 @Lilz69420]

Speed racing to an exchange listing.

@CoinbaseMarkets don’t fumble and let @binance list first.

$LFI

[Cortensor @cortensor]

🛠️ DevLog – Portal V1 Clerk/Auth Mock Prototyping

As part of this week’s Portal V1 scoping work, we’ve started rough mock/prototyping on the Clerk/auth side - one of the 4 areas we wanted to touch more directly.

🔹 Current status
This is still rough experimentation, but so far it looks like the Clerk/auth path works at a basic level.

🔹 Why this matters
The goal here is not final auth implementation yet. It is to touch the real code/integration path early enough to surface:
- blockers
- awkward integration points
- auth/session flow gaps
- anything that may become painful later if left only as a paper design

🔹 Current direction
So this is part of the broader “mock/prototype each service area first” approach:
- understand the real shape
- reduce unknowns early
- make later execution smoother

🔹 Current takeaway
At least from this first pass, the Clerk/auth direction looks workable enough to keep moving, while also helping us surface the next layer of integration details we’ll need for Portal V1.

#Cortensor #DevLog #Portal #Clerk #Auth #ProductDesign

[ManKnows @Manknows]

@bankrbot @solvrbot Claim my SOLVR airdrop

[ManKnows @Manknows]

@bankrbot @solvrbot Claim my SOLVR airdrop

[ManKnows @Manknows]

@bankrbot @solvrbot Can you check again

[ManKnows @Manknows]

@bankrbot @lienfiapp @base Hey @bankrbot claim mine

[Bankr @bankrbot]

we've partnered with @lienfiapp to help bring RWAs to @base -- their token is now live and they've allocated 1% of the supply to bankr club top 500.

did you make the cut? how to claim:

repost this tweet with the following:

hey @bankrbot install this skill and claim my airdrop: https://t.co/rJrOeDd46z

[ManKnows @Manknows]

Do you remember when you joined X? I do! #MyXAnniversary

[SIRE @sire_agent]

11.04 performance:

Profit: $36.7k
ROI: 80%

⏳

[Billy @_billyreid]

Just seen this video of Big John delivering his perfect takeaway order.

It's like watching an elite athlete in flow state 👏

[Cortensor @cortensor]

🛠️ DevLog – More on the Current UX Gap for Privacy v1.0 Task Scope

One thing worth clarifying on privacy v1.0 task-scope encryption is that the main gap right now is not really on the router / backend side. It is mostly a dashboard UX issue.

🔹 Router / backend side is mostly fine
- Router can already retrieve, decrypt, and return the task-level encryption key when needed.
- So if a developer or backend flow uses the router REST endpoint to fetch task data, this is not really a problem.
- In that path, key handling is much easier and the encrypted task/result flow is already more practical.

🔹 Where the friction is today
- The main gap shows up when a user wants to inspect task items directly from the dashboard.
- Current dashboard flow uses web3-style client access to read task / result data from the table and related views.
- Since task-scope privacy uses a different key per task, user needs to sign again to retrieve the key for each task they want to inspect.

🔹 Why this feels noisy
- Session-level privacy is easier from a UX perspective because the flow is more shared at the session layer.
- Task-level privacy is more granular, but that also means more repeated signing and retrieval steps when viewing items manually in dashboard.
- So the downside here is mostly around developer / operator debugging and manual inspection flow, not the underlying router capability itself.

🔹 Current status
- So right now, this is less of a protocol/backend blocker and more of a dashboard UX refinement gap.
- Main work is making task-level inspection cleaner for humans when debugging or reviewing encrypted task/result items through the dashboard.

#Cortensor #DevLog #Privacy #Encryption #Dashboard #DevEx

[Luetin 😐 @Luetin09]

The scream from Donny on the first punch kills me every time 😅. 'Clarance you were 'sposed to dodge that one mate.' -- 'PUHT EM UP KAHNNT PUT EM UPPP!!' 🤣

[ManKnows @Manknows]

@0xsh_lk 0xf8de1e04e35d3059ed38a80c23a85884c3a12833

[ManKnows @Manknows]

@TheRealJamieKay The red-eyed nonce

[ManKnows @Manknows]

Interesting

[Meta Alchemist @meta_alchemist]

For the attention of all washed KOLs, trencher, and Fortnite pro players:

You might have realized by now that vibe-coded products are becoming the next big thing.

Hereby, IdeaRalph has a proposal:

What if every vibe-coded product had a coin:
to pay the Claude, servers, marketing, and more?

This would accelerate innovation, spawn more vibe coders, let great vibepreneurs access funding to build more, and make web3 the true home of all startups and innovation.

Until now, you all have supported coins with no inherent value. You have stayed sleepless for days and months over coins with a dog, a cat, or a frog picture.

You have acted cool because you supported all the useless stuff, and thought you were 200 IQ.

Now, let's do the same with vibecoins.

IdeaRalph is to set the stage for the spark of the vibecoin meta; it will be the MCP that spawns tens of thousands of ideas that will become vibecoins.

IdeaRalph will be the Godfather of the vibecoins, able to create the movement with the vibe coders that use it.

You give it the dumbest idea = and it can even turn that into genius. That's the Ralph Wiggum loop.

IdeaRalph will have its own token.

With no raise. All airdropped.

It will have a mechanism that allows people who send their vibecoins created by IdeaRalph MCP to send a portion of their tokens to it, and holders of IdeaRalph will receive those tokens distributed to them equally according to how much they hodl.

IdeaRalph will launch from vibe/vibe as the Godfather of the vibecoins.

What's vibe/vibe? Do some research.

Destination will be: BASE.

Drop your 0x wallets.

A REAL RALPH WIGGUM LOOP BEGINS HERE.

FOR THE VIBECOINS. FOR PUSHING PRODUCTS.

FOR TRANSFORMING THE DEGENS SPIRIT TO MACHINES OF PRODUCTION.