Daniel (damoos)

Daniel

figuring out how things work.

11 Followers

Recent casts

how can I use herocast with a pre-existing farcaster identity? (e.g. SIWF).

  • 1 reply
  • 0 recasts
  • 0 reactions

why is everyone calling their fc client xxx-cast? opencast, supercast, herocast, …?🤔

  • 3 replies
  • 0 recasts
  • 2 reactions

My two cents regarding Hubs / Incentives and Storage Fee. Hubs: As @dwr already mentioned the only reasons two run hubs are if you're building any hub-consuming service (like a custom client, a analytics platform, ...) or for the sake of decentralization. Companies are also not rewarded to run email servers, but rather generate income through the services they build on top of it (e.g. outlook, gmail, yahoo, you name it). I expect >95% of currently active mainnet hubs to shut down within the next months (this is a good sign imho). Storage: Farcaster can only be run as a permissioned system where messages are limited to whitelisted addresses or through a pay-to-use model. Right now storage fees are on the pay-to-use side limiting the data that's stored, but not what's transmitted (e.g. rate of messages). I highly believe this needs a change but the only solution I see is a pay-per-message model which is not optimal.

  • 1 reply
  • 0 recasts
  • 0 reactions

Top casts

why is everyone calling their fc client xxx-cast? opencast, supercast, herocast, …?🤔

  • 3 replies
  • 0 recasts
  • 2 reactions

I'm worried that Signers are not automatically expiring at some point. This is a common practice in web2 (for API keys / tokens) and I believe Farcaster would greatly benefit form this as well (using a Farcaster epoch based timestamp). any thoughts on this @stephancill @samuellhuber.eth ?

  • 0 replies
  • 0 recasts
  • 1 reaction

just spun up a hub in docker but my logs are filled with message below. (it also seems to be stuck at 12% :/) I assume this is not normal? 2024-06-21 11:07:16 {"message":" █████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 12% | Getting snapshot | 408/3300 | ETA: 75h20m","timestamp":"2024-06-21T09:07:16.371Z","type":"err","process_id":0,"app_name":"hubble"} 2024-06-21 11:07:16 {"message":"\n","timestamp":"2024-06-21T09:07:16.371Z","type":"err","process_id":0,"app_name":"hubble"}

  • 1 reply
  • 0 recasts
  • 1 reaction

merci beaucoup, Harris! 😄 Yeah at some point it continued syncing and eventually was finished, so I guess that "error" is not really relevant for the sync process. Appreciate the late response! (it's a docker-based node on localhost).

  • 1 reply
  • 0 recasts
  • 0 reactions

Onchain profile

Ethereum addresses