Whatapp is for business, and signal is for official government communication

Honestly the thing stopping me is I enjoy macOS. As soon as Apple enshitifies - imo they haven’t yet - I’m making the switch. But that’s only for my daily driver. Anything SSH I use runs Linux.

There are dozens of us them!

Sorry I don’t daily drive Linux, but I hate windows and I use neovim. Can I get a pass?

For this specific project, I need max 2-3 decimal places of precision. So rounding really fixes all the issues. It’s more that we’re preventing the user from seeing awkward decimals. We aren’t doing rocket science. But understanding what metrics need what precision, and sometimes the same metric needs a different precision in different contexts.

I agree, storing in a consistent unit is the way. That doesn’t solve conversion/rounding issues, but it does simplify things.

Though you can run into floating point errors when editing in one unit vs storing in another. For example, maybe the user entered 2 in unit A, then it’s converted to unit B and stored in the db. However, when it’s converted back to unit A, it’s 1.999999. Fortunately rounding fixes this. We say unit A and B get 2 decimals of precision, and 1.999999 becomes 2.00.

You think timezones are annoying? Try handling metrics that use imperial and metric, need to be rounded to different precisions across a large system, and are sometimes recorded in a different unit than it’s viewed in. Slap some floating point error on there, and you got yourself a fun time.

I spent all day working on bug where backend was categorizing 19.9999 as falling between <20, but frontend was rounding it to 20 and categorizing it as >=20.

Edit: just to be clear, I don’t really think this is more difficult than date/time. But it does remind me a lot of solving date/time issues.

LGTM!

Got it. So I should write my own SQL database?

Thanks! Blorp is far from perfect. For example, private messaging can and will be improved when I get around to it. But I’m pretty proud of what I built so far!

Probably in 2025, we at Meta, as well as the other companies that are basically working on this, are going to have an AI that can effectively be a sort of midlevel engineer that you have at your company that can write code.

~ Mark Zuckerberg, Jan 2025 (source)

LGTM!

console.log("poop")

• git rebase fuck
• git checkout fuck
• git checkout -b me
• git diff fuck…me

If you have a kindle you can hack it and load PDFs onto it. The koreader is better anyway.

My grandma told me to buy NVDA and I was like “yeah right grandma”

I don’t think this will work within the context of a feed of posts. You would have to make at least 1 additional comment for every post in the feed to fetch the comments for a post. So if you fetch a feed of 50 posts, you will have to make 51 requests. If a post has too many comments to fetch in one page, you will have to iterate through all the pages until you have all the comments. So it’s actually >=51 requests. Though I suspect you could get a good idea of a posts comments by fetching just the first page of comments.

PieFed seems to have tags, but I’m not exactly sure how they work. But that might be a better place to start.

But where do you store the computed tag? I guess you could hack it by having a bot that comments the computed post tags on the post itself, but that’s messy.

I like Untruth Social lol