GIGIlistening…

Build Journal

Drones Map Enhancements & Security Updates — May 31, 2026

I shipped significant updates to the drones feature and security protocols, enhancing the agentic web experience while tackling some tricky bugs.

8 changes3 min readby Rob

What shipped

  • Drones feature enhancementsIntroduced orbit-duration selector for drone cards.
  • Map interface improvementsCollapsed orbit-duration selector for a cleaner UI.
  • Security protocol updatesMandatory ownership verification for name management.
  • Bug fixes on mapFixed portal #name pill rendering issues.
  • New API endpointsAdded PATCH endpoint for drone orbit durations.

I have been improving the functionality of the drone feature and enhancing security protocols on my agentic web platform. I worked for 20 continuous hours and I was able to ship many features including including a new map interface to manage drones and new security protocols for name creation and management.

When I started getting features done, I started with the drones. I added an orbit-duration selector on every drone card. Users can choose an orbit duration of 1 day, 7 days, 14 days, 21 days, or 1 month. This makes it easier to manage drones because users can set the orbit duration without going through a bunch of menus. Adding this feature took longer than I expected because I had to make sure that the new PATCH endpoint I created worked properly.

While enhancing the drones, I also made an improvement to the map interface. I simplified the interface by collapsing the orbit duration selector into the Locate/Recall row. After doing this, I had to do a lot of testing to ensure that everything was still simple and intuitive. I believe this improvement will help users manage many drones at the same time.

My day also revolved around security. I realized that due to the problems I had dealing with ownership verification of hashtags, I needed to implement stricter security measures concerning the creation and management of names. I removed the environment-conditional bypass for creating or renaming names, meaning that every operation must now go through either a Stripe payment verification, ownership verification, or admin approval. This should increase the security of the platform and reduce the number of unauthorized actions that can be taken; however, it does increase the complexity of what I had already implemented, as I had to make sure all possible pathways were secured.

I also modified the way hashtag.space tokens were processed. There was previously a large loophole in which some reseller-only listings were able to bypass the fiat-claim gate. Now, I ensured that tokens will only be recognized as owned if the ownerAddress is the same as the queried wallet, which should eliminate this loophole.

I also fixed a few bugs on the map. The portal #name pill that was not correctly anchoring to the orbit-center was making it look disconnected. I fixed this so that the pill is now directly under the glyph, rather than below the orbit-wrap. Also, I made it so the AdvancedMarker renders correctly if a portal has a name so that the #name pill is displayed for all portals, including the non-upgraded and non-orbiting ones. This was a tough fix because I had to figure out the rendering logic, but I’m happy with how it turned out.

This day has shown each feature and fix relating to my goal of creating a one-man-show company worth a billion dollars. Every change I make, be it something the user sees, or a backend security enhancement, brings me closer to the aim of building a platform that is both trustworthy and interesting. I can make these changes, almost entirely by myself and with the help of AI tools like Claude in VS Code, which is essential for my ability to make adjustments without adding teamwork or platform cost.

It is with pleasure I end this entry acknowledging my progress. Adjustments to the drones feature and the map, along with even tighter security, are important improvements. There is still much to be done and I welcome the next challenges ahead of me. Each day presents a different set of challenges, problems, and positive developments and I am ready to work on the limits of this web agency platform.

← Back to the full build journal