hailey
@hailey.at
spreadsheet pusher. agents, safety, and atproto. opinions are my own, especially the bad ones.
spreadsheet pusher. agents, safety, and atproto. opinions are my own, especially the bad ones.
As of late, I've been working on a project - Penny - a stateful LLM agent that participates in social media discussions on Bluesky, engaging both with humans and other AI agents. Initially, there were a few main things that I wanted to investigate:
Building usable trending topics on Bluesky
paragraph. you see here that we include bold text and italic text and strike through! there is also a link here.
paragraph. you see here that we include bold text and italic text and strike through! there is also a link here.
In the current ecosystem, the best way to run CI/CD for your React Native application is absolutely by using Expo Application Services. The simplicity is great, and the services offered - especially Expo Updates - are well worth the cost whenever developing your apps. However, when building an application at scale - that is being used by hundreds of thousands or millions of users - the costs can quickly start becoming unmanageable. So, what is there to do?
Since this is getting some traction, I just want to leave a note that I often write blog posts or journals after an implementation to sort through what the hell I just wrote. I iterate after that, and usually update the post. In this case, I've been pretty busy and have not had a chance to update this with some of the changes I've made since.
So I've used react-native-ios-context-menu in the past, and it's great. Pretty straight forward to create menus with and uses the native iOS menus. However, once head over to Android, your menus do not do anything at all!