dev iyer

@_Shark_byte So cool. I shared to some folks from the SF Planning Department!

I built an interactive map of SF Every building color coded by build year, See it’s history, stats and more This SF map, alongside the NYC one, has also been wrapped into a new ‘skyline project’ Now you can view both cities from one main landing page :D Projects 🔗 below

@YannickBuccella My mother has Malignant Mixed Müllerian Tumor. Are the cancer centers in Zurich / Europe more advanced that the US (ex MD Anderson?) Trying to find the most advanced treatment available in the world.

Oncology weekend shifts always have something unexpected in store for you. This poor patient was referred to our center with initially an unclear digestion disorder, before the CT scan revealed this massive tumor mass, which practically filled her whole belly. All the darkish grey areas in the photos is basically tumor. Biopsies revealed a nasty relapse of her melanoma, first removed in 2017 and in remission ever since. We now await the molecular diagnostics and especially the BRAF-mutation. If positive, we will combine two different targeted drugs by tablets with single immunotherapy, if negative she will start a dual immunotherapy.

@khushkhushkhush @GlissonBrad

who is the best early stage consumer VC you know?

Getting painfully obvious that frontends in the future will be 120fps diffusion models

@MartinShkreli Yooo come to the ballpark

in SF if you want to meet

@rauchg @BarryCarlyon Great response

Here's my update to the broader community about the ongoing incident investigation. I want to give you the rundown of the situation directly. A Vercel employee got compromised via the breach of an AI platform customer called Context.ai that he was using. The details are being fully investigated. Through a series of maneuvers that escalated from our colleague’s compromised Vercel Google Workspace account, the attacker got further access to Vercel environments. Vercel stores all customer environment variables fully encrypted at rest. We have numerous defense-in-depth mechanisms to protect core systems and customer data. We do have a capability however to designate environment variables as “non-sensitive”. Unfortunately, the attacker got further access through their enumeration. We believe the attacking group to be highly sophisticated and, I strongly suspect, significantly accelerated by AI. They moved with surprising velocity and in-depth understanding of Vercel. At the moment, we believe the number of customers with security impact to be quite limited. We’ve reached out with utmost priority to the ones we have concerns about. All of our focus right now is on investigation, communication to customers, enhancement of security measures, and sanitization of our environments. We’ve deployed extensive protection measures and monitoring. We’ve analyzed our supply chain, ensuring Next.js, Turbopack, and our many open source projects remain safe for our community. The recommendation for all Vercel customers is to follow the Security Bulletin closely (vercel.com/kb/bulletin/ve…). My advice to everyone is to follow the best practices of security response: secret rotation, monitoring access to your Vercel environments and linked services, and ensuring the proper use of the sensitive env variables feature. In response to this, and to aid in the improvement of all of our customers’ security postures, we’ve already rolled out new capabilities in the dashboard, including an overview page of environment variables, and a better user interface for sensitive env var creation and management. As always, I’m totally open to your feedback. We’re working with elite cybersecurity firms, industry peers, and law enforcement. We’ve reached out to Context to assist in understanding the full scale of the incident, in an effort to protect other organizations and the broader internet. I also want to thank the Google Mandiant team for their active engagement and assistance. It’s my mission to turn this attack into the most formidable security response imaginable. It’s always been a top priority for me. Vercel employs some of the most dedicated security researchers and security-minded engineers in the world. I commit to keeping you updated and rolling out extensive improvements and defenses so you, our customers and community, can have the peace of mind that Vercel always has your back.

@hthieblot Supercalifragilisticexpialidocious

pitch me your company in 1 word.

@okayzade Love it

@dev1yer yes. i have another just like that → sfguessr.com

Key to a good civic tech demo on X: 1. Make it a map visual 2. Make it open source 3. Make it fun and relevant

@isareksopuro If you’re interested in colabbing with us at @Locunity check it out and DM - we’re building the ontology layer for local government data. There’s a ton of cool data viz ideas we can work on by exposing our data which we don’t have bandwidth to work on.

@dev1yer that is high praise thank u so much

i made a map to monitor data centers all around the world tracks construction + nearby power plants + local AI legislation, and follows the politicians behind their bans (+ if they're getting paid to do so!)

@skeptrune Congrats! Excited by the roadmap🔥🔥🔥

mintlify is now valued at 500 million dollars!!! we raised a 45 million dollar series b from a16z and salesforce ventures!!! we are leading the charge on agent-first knowledge infrastructure. docs for humans are dead. by this time next year, agents are going to be 99% of all traffic to your site. some of the things we're doing to adjust to this 1. return markdown by default anytime a resource is requested with an accepts ‘prefers markdown’ header 2. skill md support (generates a skill with AI and updates it with every change, you can also set your won). further, skills are now present as resources on all MCP servers 3. MCPs generated by default for every site (a significant percentage of docs traffic comes from MCPs now, if your content doesn't have one this is a significant disadvantage) 4. AI workflows that automatically monitor your codebase for changes and keep your docs up to date not only have i been working here for 10 months, but i use a mintilfy site every time i work on any side software project. today, it's harder to find a devtool not on Mintlify than on the craziest part is, this is the worst the mintlify's product will ever be. i don't think most understand how fast we are accelerating. it's going to be a a completely different experience in a few months

If you're interested in leveraging AI agents to help govern more efficiently, DM me - some insane things in the pipeline with @Locunity

@shcallaway I took the plunge with @Locunity 🫡 it's hard work but very fulfilling. The bar for "what's good" is so low that you can deliver mind-blowing solutions in this sector at fractions of effort.

I’m not very political, but IMO some of the most important problems you could possibly be working on in 2026 are: - Improving our system of govt. - Improving our ability to pass laws - Strengthening our democracy It’s thankless work but completely essential. If I weren’t building @sazabi, I would seriously consider dedicating my life to this mission

You can do a ton of cool stuff with SF OpenData

@wolfiesch Love it! What did you use for the mapping library?

made an interactive time lapse of parking activity in SF

The Jmail documentary screening with @rtwlz was objectively a collection of the coolest people in SF

@konstiwohlwend that's wild for the amount of money in the auction pool - $100k+ for a street sign but not official street name lmao

yet only in the Terms of Service do they mention that they're not actually naming a street. they're just putting up a sign

There's nothing in the world like listening to @lambofgod while coding

Sure thing! My thoughts: 1. Railway’s product design is great. The UX is polished, approachable, and especially compelling for newer developers or teams that want to get moving fast with a GUI-first workflow. The project canvas is cool, though for my use case as a backend-heavy engineer it wasn’t a major advantage. 2. The biggest issue for me was a recurring “stale runtime” problem. My best read is that overlapping rolling deploy replicas plus coupled web/worker execution meant queued jobs could still be consumed by an older live process generation even after new code looked deployed. I spent a lot of time debugging this, including separating services, and never got to a point where I fully trusted the runtime behavior. After moving to @render, that issue disappeared, at least so far. 3. The frequency of incidents, plus the authenticated user data caching incident last week, also hurt trust for me from an infra standpoint. Overall, I think Railway is a very well-designed product with a lot going for it. However for my workload, I needed more confidence in runtime isolation and production consistency.

@dev1yer @Locunity mind if you share more about the UX that you prefer on Render? we try to aim for progressive disclosure, but sometimes the information architecture leads to stuff that's hidden up to you if you wanna share

Just switched @Locunity from Railway to @render . Immediate observations: - p95 feels materially better for our app pages/API calls - Much cleaner mental model: separate web service + background worker + cron instead of hidden in-process coupling - We’d been hitting stale-runtime/deploy ambiguity where queued jobs behaved like old code after deploys, which is now gone. Massive win IMO. - Render makes background job isolation, canaries, and debugging much more legible