HN user

dnsbty

215 karma
Posts6
Comments18
View on HN

While this seems like a great move for agents, your key challenge will be fighting spammers trying to use it. On top of that, you're sending over P2P routes instead of A2P routes which is against the carriers' terms of service and will likely lead to numbers getting blocked.

It's a little different because they're building for iMessage instead of just SMS, but you might look at the comments on this launch: https://news.ycombinator.com/item?id=48267829

I think something will need to change here to give agents access to systems, but this doesn't really work with the way telecoms are currently set up.

This is one area I expect LLMs to really shine. I've tried a few static analysis tools for security, but it feels like the cookie cutter checks aren't that effective for catching anything but the most basic vulnerabilities. Having context on the actual purpose of the code seems like a great way to provide better scans without needing to a researcher for a deeper pentest.

I just started a scan on an open source project I was looking at, but I would love to see you add Elixir to the list of supported languages so that I can use this for my team's codebase!

I've been using Codebuff for the last few weeks, and it's been really nice for working in my Elixir repo. And as someone who uses Neovim in the terminal instead of VS Code, it's nice to actually be able to have it live in the tmux split beside Neovim instead of having to switch to a different editor.

I have noticed some small oddities, like every now and then it will remove the existing contents of a module when adding a new function, but between a quick glance over the changes using the diff command and our standard CI suite, it's always pretty easy to catch and fix.

This is an awesome guide, but with mix dialyzer taking that long I'm curious: are you caching your PLTs? And if so, why not?

I've worked on some pretty huge Elixir apps, and I've seen the dialyzer take that long on the first run, but once the PLTs are cached it usually takes only a minute or two even in GH Actions

I’m a little late to the conversation, but I’m using the Elixir version of TypeID[0] in my project. While the repo linked to above doesn’t provide any guidance on storing the TypeIDs, the Elixir version does this really well. You store the prefix in the your schema (model) code, but the underlying database column is simply a UUIDv7.

So when you call the new function, it will generate a UUIDv7, base32 encode it, and then prepend the prefix. Then at the database layer it will translate that to a UUIDv7 for storing and translate back to the string version when loading.

[0] https://github.com/sloanelybutsurely/typeid-elixir

Spent two months in Barcelona over the last year, and I second the recommendation. The mascarpone croissant is excellent, but I would actually recommend the raspberry jam croissant even more highly. I haven’t had a thing from Pastisseria Hofmann that I didn’t like.

With Erlang releases (compiled code with the Erlang runtime included) you can do hot code swapping to change the code while it’s still running.

And iirc I believe LiveView will have all the state necessary client-side to be able to reconstruct the session when reconnecting the socket. I’m not near my development machine to make sure on that one though.

I agree with most of this except for the bit about any of the first locations being in Comcast territory. I'm a Google Fiber subscriber in Provo, UT. Before Google got here I was on Comcast.

Our cap was 50 Mbit which wasn't bad, but then when Google came in, Comcast upped that plan to 250 Mbit with no hardware upgrades or anything for the same price which was really nice.

The main thing I noticed though is that reliability with Google is a lot higher. My Comcast connection would go down for an hour or two about once a week, but my fiber connection seems to always be fine.

As far as cities bending over backwards, Provo definitely did that. We had put in a citywide fiber network using a $40 million bond and then ended up selling it to Google for $1. It was definitely the best move considering the company that had been operating it before defaulted on their payments, but Provo will still be paying for the network for 12 years.

This is awesome news. Even though most of the APIs are really well documented, AirPair would be very useful for getting help with fixing those little bugs with integration that can take hours to figure out. I would have loved something like this when I was working on a project with Twitter's API a couple months ago.

I like to just follow people whose tweets I actually want to read to begin with. Before following anyone I check their last few days worth of tweeting to make sure they don't post junk and that I will be interested in what they have to say. Twitter is not meant to be a friendship or connection manager like Facebook or LinkedIn so much as it is a way to get concise info delivered quickly. Obviously it can be a great networking tool, but by getting others to follow you by sharing good content, not by following junk tweeters in the hope that they'll follow you back. If you're too afraid to unfollow those whose tweets are junk you're not using Twitter correctly.

Edit: That being said, I feel like a client that would let people sift through tweets more efficiently could be great for those who don't agree with me and end up following 10k+ people, and that approach definitely isn't uncommon.