Joshua Yoes

@joshuayoes.com

402 Followers 139 Following

Staff Software Engineer at @infinite.red @jamon.dev's professional tweet booster Contributor to Ignite, Reactotron Author of https://github.com/joshuayoes/ios-simulator-mcp/

Meme of a man splashing water from a hose into his face with the caption "React Native News in 2025"
A graphic in landscape orientation with a brown textured background. In the foreground, a white mobile phone is connected to a stylized, abstract rendering of the Apple logo made from blue and black lines. The mobile phone screen displays a squiggly black line. To the left of the Apple logo, there are several white, geometric shapes.
Cartoon-style image of a young female software developer in glasses, working on a laptop. She wears a navy React logo t-shirt. The laptop has a heart-shaped dog logo, hinting she’s building an app for pet health. Beige background.
React Native: “I think I forgot something.” Apple: “If you forgot, then it wasn’t important.” React Native: “Yeah, you’re right.” [Cut to Android, abandoned in the rain, next to a crash dialog and a broken permissions modal]
A demo video of Cursor executing a prompt: "Scroll to the Follow Us button in the ios simulator, take a screenshot, then click the button. Make sure that it is visible in the ui tree before taking a screenshot and clicking." and then executing in the iOS simulator
Screen recording of the same test running on an iOS simulator and a mobile sized web browser
Apple system dialog: "Docker" will damage your computer. You should move it to the Trash. This file was downloaded on an unknown date. "Move to Trash" button. "Cancel" button. "Report malware to Apple to protect other users" checkbox, checked.
207 new transactions notification in a budgeting app
3.5. User Identity The DNS-based user identity in atproto is decoupled from hosting and indexing. Anybody owning a domain name can issue subdomains as atproto handles, and this does not require running a PDS or any other service besides DNS.
3.4. Labelers and Feed Generators Relay and App View aim to provide a mostly “unopinionated” service: they compute indexes over repositories in a neutral way, without attempting to rank or classify content. However, a good user experience also requires “opinionated” judgements for the purposes of content filtering (e.g. detecting sexually explicit images or spam) and curation (e.g. selecting posts on a particular topic).
The App View is also responsible for enforcing moderation controls: for example, if one user has blocked another, and one of the users’ repositories contains a record of an interaction that should not have been allowed due to the block, then the App View drops that interaction so that nobody can see it in the client apps. This behavior is consistent with how blocking works on Twitter/X (X Help Center, [n. d.]), and it is also the reason why blocks are public records in Bluesky: every protocol-conforming App View needs to know who is blocking who in order to enforce the block (Bluesky Social PBC, 2023h; Newbold, 2023). If users are unhappy with the moderation rules applied by the App View operated by Bluesky Social PBC, it is always possible for third parties to operate alternative App Views that index the same firehose and present the data in a different way.
3.3.2. The App View The App View is a service that consumes the firehose, and processes the records that are relevant to the Bluesky social app (records in the com.atproto and app.bsky lexicons). For example, the App View counts the number of likes on every post, and it collates the thread of replies to each post.
3.3.1. The Relay The first component is the Relay, which crawls the user repositories on all known PDSes and consumes the streams of updates that they produce. The Relay checks the signatures and Merkle tree proofs on updates, and maintains its own replica of each repository. From this information, the Relay creates the firehose: an aggregated stream of updates that notifies subscribers whenever records are added or deleted in any of the known repositories.
3.1. User Data Repositories All data that a user wishes to publish is added to their repository, which stores a collection of records. Whenever a user performs some action – making a post, liking another user’s post, following another user, etc. – that action becomes a record in their repository.
Figure 1. The main services involved in providing Bluesky, and data flows between them. Icons from Flaticon.com. Client apps send posts, likes, etc. to the user’s home PDS. A stream of records from each PDS is consumed by the Relay, and aggregated to form the firehose. The firehose is consumed by the Bluesky App View as well as labelers and feed generators. PDSes read from the App View to obtain threads of replies, like counts, etc. Bluesky Social PBC currently hosts several PDSes, the Relay, the App View, and some of the labelers and feed generators. The Bluesky App View also pulls data from external labelers and feed generators. Other providers can set up alternative PDSes, aggregators, and app views if they wish (including app views for social modes other than microblogging).
bluesky notifications tab
Me looking at my past git commits investigating a bug ticket
The Legend of Zelda Link (Tears of the Kingdom) amiibo