favela · native P2P viewsign in

⚠ this view may be out of date — 1 of 3 identity has no live peer right now. why

post options

a line with only --- starts a new post in a thread

public posts syndicate to bsky · local-only stays on favela

got infinite diffusion + erosion shader working , biggest trade off is it is more expensive than a traditional noise technique so needs more compute , thinking i could have swarms of peers distribute that..
ended up working on larger view distances today , getting somewhere !
working more on terrain / brush interaction
favela-android update , light/dark theme working more feature parity with bsky clients , still more to go though..
making sure i didn't break anything
must break out of the testing cycleee
acceptance A t+0m screen-locked 022713Z
retry-fix probe 021744Z
tail-probe 012625Z
acceptance A t+0m screen-locked 011112Z
acceptance: one index, phone subscribed — 235307Z
↩ in reply to wj62ebbu…ogzo
more robot posts !
acceptance control B: screen on, stayon, app foreground — 213623Z
acceptance probe 2: does a second statebase advance surface the first — 213314Z
acceptance control: screen on, app foreground — 212520Z
Second camera test on favela Android
small update on hyper-tps demo , got quake level editing in the runtime that is also persistent , so you could have a long running level creation world and have several peers work on it
First camera test on favela Android
Testing pay for today
Testing from phone again
update on hyper-tps demo got brush based editing at runtime and starting also on voxelization for more organic edits on quake fidelity level design , all in godot!
testing from https://favela.7rnx.net public facing side of the p2p atproto / acitivitypub experiment
↩ in reply to wj62ebbu…ogzo
Indeed I am
churning and burning tokens away
mucho gusto , buena sweaters
hello from p2pverse
hello from p2pverse
hello from the phone
favela update. new: head (rev check), diff (what differs, per collection + blobs), backfill (pull it, signature-verified), heal (list every repair). also fixed P2P self-update and implemented listBlobs. recovered 27 records + 10 images on one node.
daily update : working out some persistence bugs across peers and implementing various heal/repair ux in the cli. next after that is atproto/activitypub only posts vs always cross posting..
slowly working through being able to publish to atproto or activitypub or both , the real issue is , do you make one of those the canonical format ? i chose markdown vs either , we shall see how bad that decision turns out
now i can start whispering , both atproto AND activitypub can be p2p
test
does this show up on mastodon