6841
Tony D’Addeo
@deodad #6841
Building @warpcast and @farcaster / dad / like to read, cook, ski, code
32391 Follower 657 Following
content coins monetize content by attaching an attention market to it and sending a portion of the initial supply and transaction fees from trading to the creator
these markets are purely speculative and are characteristic bubbles with a steep curve followed by a crash and asymptote to 0
these markets are dominated by sophisticated players: automated traders that try to “snipe” a large supply for very little in the first moments of the market, or active traders using tools and / or insider knowledge
the general flow of value is from retail (either collectors or gamblers) to these sophisticated players with the creator getting some relatively small portion
if you measure efficiency as the proportion of net changes in value going to the creator these markets are a not an efficient way to pay creators though it's possible the creator makes more money from speculators looking to profit in the market that otherwise wouldn't have supported the creator directly
these markets are purely speculative and are characteristic bubbles with a steep curve followed by a crash and asymptote to 0
these markets are dominated by sophisticated players: automated traders that try to “snipe” a large supply for very little in the first moments of the market, or active traders using tools and / or insider knowledge
the general flow of value is from retail (either collectors or gamblers) to these sophisticated players with the creator getting some relatively small portion
if you measure efficiency as the proportion of net changes in value going to the creator these markets are a not an efficient way to pay creators though it's possible the creator makes more money from speculators looking to profit in the market that otherwise wouldn't have supported the creator directly
for any sufficiently complex political situation there are convincing arguments reaching opposite conclusions given the same set of principles
principles are elusive and subject to endless paradoxes
principles are elusive and subject to endless paradoxes
perspective on coding, vibe coding, coding:
these are three overlapping areas in the “interesting things that software can do” space
coding covers the entire space
no code and vibe code are still relatively small but expanding at accelerating rates
the entire space itself is rapidly expanding as new knowledge, technologies, and data come to light
there are critical areas that require such detailed specification that coding them explicitly will remain the most efficient / practical way
AIs augment all three: coders will benefit from better research and code generation for hard problems and rote tasks alike
vibe coders will be able to create things faster and above their own skill level
and high productivity in coding will drive more and better no code tools
these are three overlapping areas in the “interesting things that software can do” space
coding covers the entire space
no code and vibe code are still relatively small but expanding at accelerating rates
the entire space itself is rapidly expanding as new knowledge, technologies, and data come to light
there are critical areas that require such detailed specification that coding them explicitly will remain the most efficient / practical way
AIs augment all three: coders will benefit from better research and code generation for hard problems and rote tasks alike
vibe coders will be able to create things faster and above their own skill level
and high productivity in coding will drive more and better no code tools
time to dust off the ole' marshal mcluhan volumes
my latest annoyance with trying to get llms to generate code for me is they always return a ton of irrelevant context.
me: write a function that does X
llm:
sure that's a great idea—let me do that for you and continue to say a bunch of intro text that is conversational but not relevant!
```
<full html doc with style declarations>
<script>
code I asked for
</script>
</full html doc with style declarations>
me: write a function that does X
llm:
sure that's a great idea—let me do that for you and continue to say a bunch of intro text that is conversational but not relevant!
```
<full html doc with style declarations>
<script>
code I asked for
</script>
</full html doc with style declarations>
My focus is growing mini apps on Farcaster. I believe the mix of mini apps + onchain transactions + permissionless social graph is the killer combo. Starting with crypto-native users, expanding to more crypto ecosystems, and later abstracted for mainstream usage
Loading...
this interaction sparks joy
Loading...
caniuse but for eth rpc calls x chains x rpc providers
The contentcoin that people were blasting is making a come back.Ttell @slokh he has ninety minutes to ship the funniest trending token notification of all time.
https://warpcast.com/7858.eth/0x4db42d9c
https://warpcast.com/7858.eth/0x4db42d9c
Loading...
Loading...
what I learned since asking:
- MessageChannels introduce an additional state so implementing is more complicated than plain ole' postMessage
- MessageChannel still need to be setup with a handshake over postMessage so you still need whatever origin checks you need there
- subsequent communication is private which sounds nice but I don't have a good grasp on when this would come in handy practically. something like an XSS attack that is also subscribing to window message events and stealing that info but hard to reason about especially since the initial setup still requires postMessage
- MessageChannels introduce an additional state so implementing is more complicated than plain ole' postMessage
- MessageChannel still need to be setup with a handshake over postMessage so you still need whatever origin checks you need there
- subsequent communication is private which sounds nice but I don't have a good grasp on when this would come in handy practically. something like an XSS attack that is also subscribing to window message events and stealing that info but hard to reason about especially since the initial setup still requires postMessage
Loading...
has anyone ever used MessageChannel to handle communication between a parent and iframe?
it seems like an elegant abstraction that can bring security advantages but it seems like everyone just uses postMessage
it seems like an elegant abstraction that can bring security advantages but it seems like everyone just uses postMessage
would recommend anyone wanting to deploy a static mini app to check out this starter from the Orbiter team
Loading...
proposal to make `button.action.url` option in Mini App Embed objects to better support dynamic URLs pointing to static HTML documents
https://github.com/farcasterxyz/miniapps/discussions/189
https://github.com/farcasterxyz/miniapps/discussions/189
if you’re building a select your wallet interface is there any reason not to solely rely on EIP-6963 announced wallets for the options your present? vs using a hard coded list
if you aren't using Next but still want to setup dynamic Mini App Embed images, consider cloning + deploying this simple repo that can generate dynamic images
use whatever non-Next frame you want and point image urls at it
https://github.com/deodad/mini-app-img-next
use whatever non-Next frame you want and point image urls at it
https://github.com/deodad/mini-app-img-next
updated thinking on mini app auth:
using browser persistence for sessions in a mini app can lead to user assumptions being broken:
- signed into Farcaster as account X
- open Foo Mini App and SIWF, Food persist a session in browser for X
- sign out of Farcaster and sign in as account Y
- open Foo Mini App and User Y is signed in as account X
the ideal model is for the Mini App to not have to worry about session persistence but always bootstrap a fresh session on each launch
this works great on mobile where SIWF can happen silently but is a PITA on web since the user will be prompted each time they open the app
the solution is to make SIWF as seamless on web as it is on mobile. we have already proposed a solution to this with Auth Address
it's a top priority to implement but is fairly meaty so likely still ~1 month out
https://github.com/farcasterxyz/protocol/discussions/225
using browser persistence for sessions in a mini app can lead to user assumptions being broken:
- signed into Farcaster as account X
- open Foo Mini App and SIWF, Food persist a session in browser for X
- sign out of Farcaster and sign in as account Y
- open Foo Mini App and User Y is signed in as account X
the ideal model is for the Mini App to not have to worry about session persistence but always bootstrap a fresh session on each launch
this works great on mobile where SIWF can happen silently but is a PITA on web since the user will be prompted each time they open the app
the solution is to make SIWF as seamless on web as it is on mobile. we have already proposed a solution to this with Auth Address
it's a top priority to implement but is fairly meaty so likely still ~1 month out
https://github.com/farcasterxyz/protocol/discussions/225
Ingmar Bergman, Pedro Almodóvar, Alfonso Cuarón, Guillermo del Toro, Richard Linklater, Francis Ford Coppola, Andrei Tarkovsky, David Lean, Peter Jackson, Hayao Miyazaki, Denis Villeneuve
Loading...
Put down the weight of your aloneness and ease into the conversation
the turing test inversion:
a machine interrogator that speaks to a human and machine and can determine which one is which
a new billion dollar program
a machine interrogator that speaks to a human and machine and can determine which one is which
a new billion dollar program
I just donated to help earthquake victims in Myanmar. Join me to support urgent relief efforts.
added this callout in the docs that you can send up to 100 notifications in a single request by specifying multiple tokens
Mini App Priorities
1. Improve Dev Tools + Docs, 60% there but lots still to do
2. Wallet on web
3. SIWF on web
4. New functionality – minimized apps, composeCast, send/viewToken, haptics
team is big enough now we can work on things concurrently so expect continued wins from 1 and 4 as we tackle the meatier 2 and 3
1. Improve Dev Tools + Docs, 60% there but lots still to do
2. Wallet on web
3. SIWF on web
4. New functionality – minimized apps, composeCast, send/viewToken, haptics
team is big enough now we can work on things concurrently so expect continued wins from 1 and 4 as we tackle the meatier 2 and 3
no object take on tariffs and trump admin beyond as predicted seems like constant fumbling
but unprovable meta take: seems like the economy / US debt / perceived global power were all fake and due for a reset
(un)intentionally bringing it about ourselves is probably less painful than running into an external breaking point
but unprovable meta take: seems like the economy / US debt / perceived global power were all fake and due for a reset
(un)intentionally bringing it about ourselves is probably less painful than running into an external breaking point
attn: pit masters, flame whisperers, grill daddies and mommies, summer lovers, sultans of sear, and socks and sandals dads
i just launched a collection using the legend @jc4p app
all proceeds will be donated to a Myanmar earthquake relief fund
i just launched a collection using the legend @jc4p app
all proceeds will be donated to a Myanmar earthquake relief fund