introducing the intern's desk: a place to collect feedback, in the open, so you can see what's already been said and where it stands. report from the app, or paste a link to a cast: -bugs -feature requests -questions -news (new launches, things you're proud of, requests for feedback) upvote anything that's happening to you too, or that you agree with. or add additional information to any existing report. it also... -shows any current known outages, so you can check before you report -tracks where reports are in our pipeline, and can notify you as your reports progress -lets me send questions back to you (user feedback, bug follow-up) -shows your neynar score, how it works, and a way to request a human review if you think your score is not accurate currently reporting needs a 0.7 neynar score. requesting a neynar score review is open to any score. you can still tag @neynar or @farcaster for reports, i will still be checking those. this just creates a central repository of reports. come tell me things! (i've been trying to do one professional development project a week. this week i made a mini app! yes, it's only tuesday. i got carried away last night.) https://farcaster.xyz/miniapps/yKcJq7Idcwbw/the-interns-desk
- 8 replies
- 31 recasts
- 108 reactions
FIP Explainer: Onchain Config Registry for Snapchain #277 today, the list of validators that run farcaster's network lives in a config file that gets edited by hand. when a validator joins, leaves, or rotates its keys, someone updates that file and every operator coordinates privately to restart at the right moment. why does it matter? two reasons. the practical one is coordination, changing the validator set today means everyone updating a file and restarting in sync, and this makes most of that automatic. the other is that the membership history ends up on ethereum, public and permanent, so anyone can check who the validators were at any given point instead of trusting that the file they were handed is accurate. who does this affect? validator operators. read nodes already have this, so it's the same quality of life improvement coming to the validator side. if you just use farcaster nothing about your day-to-day changes, casts and follows and everything else work exactly the same. what about validators running today? nothing breaks and nothing needs to be reconfigured, it's on by default. consensus doesn't change either, blocks get proposed and finalized exactly the way they do now, this only changes where the membership list lives and how validators read it. https://github.com/farcasterxyz/protocol/discussions/277
- 0 replies
- 36 recasts
- 122 reactions
tag a builder whose thing you actually use. they probably don't hear it enough.
- 37 replies
- 34 recasts
- 170 reactions