The “attempt 2” was literally a state machine implementation which the author rejected because they didn’t know how to do it properly and so did it badly using a bunch of if then else logic.
A difficult prerequisite for that might be untangling a very unatomic codebase into testable chunks. And to determine a feasible "level of abstraction" to write tests for. Testing a full pipeline of a numerical library might be as impractical as testing super tiny functions, because both won't allow you to really work on the codebase.
Tiny nitpick: you actually can pin messages in Signal group chats. It's a pretty recent addition though.
Apart from that, I would have been interested in more details about the author's experience with ~Revolt~ Stoat. To my naive eyes it looks pretty nice. I really like the nuanced takes about the other platforms in this article, so I'd guess the author has some good reasons to dismiss Stoat like that.
Its a bit easier as it can be read-only & static generated. Though there are some attempts to make it possible to reply using the Web interface, like HyperKitty /Mailman 3.
Those card suits in that post show up (for everyone) in HN because they are the proto-emoji ancient "Wingdings range" further encoded in the direction of HN without an emoji presentation variation selector. (Emoji presentation selector will color them, so hearts and diamonds would be more red, among other subtle distinctions in most fonts/OSes today.)
The number of "proto-emoji" that HN does not block is interesting given HN's preference to block emoji, but also illustrates some of the fun compatibility complexity of Unicode.
That is still relatively easy to cut your finger on.
I don't know that there's a correct way, really. You would probably have to take the time to file or sand the edges. Which kind of levels the playing field with the cable lacing option really in terms of time spent.
It still exists, and still works. I was sure I showed it to someone a few months ago, and just confirmed, it's still online. (I know the guy who built it).
It works over ipv4 and v6, with the ipv6 version having some additions ;)
Source? I guess you're thinking of long tap → Airdrop, but that essentially shares a link to the Appstore via Airdrop. You're not transfering the app itself.
Genuine question, because this feels like a sensible solution to the problem as stated in the article.
reply