Quick access to frames in casts could be powerful:

@dwr.eth -> user
/dwr -> channel
$eth -> assets
+frame -> frame?

Other related idea is while $ works for tokens, there's not a great generic contract address standard. Frames paired to contract addresses as a default UI could be interesting.

How is the +frame resolved? Is there a registration process similar to channels?

If we did it we likely would do it onchain. Don’t want more Warpcast only tech debt. :)

😍😍😍 love to hear a shift away warpcast-only tech debt <3

another option is a reverse-lookup friendly-name render, but need to worry about collisions/impersonations/scams

ie. providing a frame permalink renders as +displayname

A doodler and computerer. I like permissive/permissionless open source, smart contracts, p2p systems, room-scale VR, and NixOS.

shazow.net

Currently: WhatsABI

father, husband, css golfer, ux engineer, silently defining variables as /sdv sdv.wtf

I like this! ENS supports different records, so could have a `frame` record on shazow.eth so +shazow.eth resolves to a frame whereas @shazow.eth resolves to an account. (Then I could also have +foo.shazow.eth or whatever.)

Then ideally the *.farcaster.eth would resolve to the same kinds of records.

What if the existing fname namespace was used but as subdomains?

So +uniswap.swap is

swap.uniswap.farcaster.eth under the hood

That way it's not a scramble to maintain yet another new namespace