Content
@
https://warpcast.com/~/channel/fc-proto
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
12 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
ah and there is no ipns, i couldn't deploy a simple index.html there (the irony), had to use the file storage
1 reply
0 recast
0 reaction
Livid
@livid
if you use one of these three formats in the Bio, it should work: - 62-byte IPNS - 46-byte CIDv0 - 59-byte CIDv1 prefixes like ipns:// or ipfs:// are not required. initially, it may take a while to load because the furl ipfs node needs to locate the resource. you can test CID retrievability with https://check.ipfs.network/
1 reply
0 recast
1 reaction
MetaEnd馃帺
@metaend.eth
all checks out bafybeiath4pp45us2ozs6kec72c6kfjgoetcpmax3dfkytnpjm5nu7nt7u but it's not displaying via https://metaend.eth.furl.pro
2 replies
0 recast
0 reaction
