Content
@
0 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
Farcaster provides a well-defined namespace, which (thanks to global state) it is very easy to resolve. For example, the following paths are clearly defined, once we know that we are using the Farcaster namespace. - vrypan/pfp - vrypan/url - vrypan/cast/0x.... - vrypan/location (soon :-) How can we expose this namespace to the rest of the world? A great example is furl.pro that bridges the fc namespace to http. Can we create a standard? Can we build some type of infrastructure (thinking a farcaster DNS for example, or an ENS, or maybe something else) others protocols/apps can use? Share ideas!
3 replies
2 recasts
14 reactions
MetaEnd🎩
@metaend.eth
I'll give this a try today. I guess fleek as ipfs host should work
1 reply
0 recast
2 reactions
fuego
@fuegoblanco.eth
Most definitely does :)
2 replies
0 recast
1 reaction
MetaEnd🎩
@metaend.eth
how does it work exactly? I've added ipfs://<hash> (index.html) to my recaster profile, but https://metaend.eth.furl.pro gives me a 404
1 reply
0 recast
0 reaction
fuego
@fuegoblanco.eth
Try just using the IPNS url without a prefix or suffix.
2 replies
0 recast
0 reaction
MetaEnd🎩
@metaend.eth
Only used with ipfs hash, it's blank now I have a feeling that it's a fleek ipfs issue. With the fleek domain it works
1 reply
0 recast
0 reaction
fuego
@fuegoblanco.eth
I believe they are migrating from fleek.co to fleek.xyz within the day. I’m not sure if that would be the cause, though. What kind of site is it? Just a static page, or are you using a framework?
1 reply
0 recast
0 reaction
fuego
@fuegoblanco.eth
Disregard my previous cast 😂
0 reply
0 recast
0 reaction
