Hacker Newsnew | past | comments | ask | show | jobs | submit | kurisufag's commentslogin

> This is not a sentence in English.

> I'll be here at day.

i hate to heckle, but... :)


Heckling deserved :)

I'll be here all day, using flow typing on my phone :)


fwiw i believe strongly that there would not still be a nitter without graf's work on it.

in the space of working on cool shit, he's good people. see: moldbug and urbit, for a similar case.


oh, totally. I was hoping to avoid people going "i wonder what poast is", but Graf said they've been backlinked before and it's no big deal; but i can't remove my earlier comment.

So i guess i misread!


pharmabro went to prison for sec fraud, not the daraprim hike


Well, sort of. Matt Levine noted at the time that penalties for fraud are usually based on damages. Shkreli's fraud had no damages (and his legal team, obviously, emphasized this), but people hated him, so he was sentenced based on unusual factors.

That's the justice system for you.


i added a minutely scrot cronjob about a year ago and haven't used it once. remembering "that website i was on last week" is apparently not a real problem I was having


or with ipa-esque authentication schemes and shared mounts


>create a place truly free of AI for those who do not want to interact with it

the bar, probably -- by the time they cook up AI robot broads i'll probably be thinking of them as human anyway.


As I said, training developments have been stagnant for at least two or three years.

Stop the bullshit. I am talking about a real place free of AI and also free of memetards.


the USB-C legislation was pretty clearly directed at Apple alone


No, it wasn't. The usb forum could have decided to use a lightning compatible standard, but there were problems with it.

Besides, apple are one of the decision makers in the usb c standard, the legislation mandated a standard, but not a specific one, just the same one for all, and this forum which includes apple decided to go with usb c https://www.usb.org/members


...and now we get stupid overly complex and fragile connectors on things like laptops instead of simple and robust barrel plugs.


I think you mean: 700 different permutations of barrel plug diameter, sex and voltage?


There has been maybe two dozen different barrel plugs widely used over the last two decades, and "12V" and "20V" were already a de-facto standard for laptops with 2S and 3S batteries respectively (there was some artificial segmentation like 18.5V, 19V, 19.5V, 20V, etc. but they are all within tolerance range). I have not seen a male laptop; they are always female, being the "receiver" of the power.

Search for "laptop" here: https://en.wikipedia.org/wiki/Coaxial_power_connector#Listin...


Two dozen different plugs over the last two decades means that we're averaging 1.2 different barrel plugs per year.


That leaves out all the "what is a computer?" devices that had all sort of plugs that wouldn't be barrel: tablets, chromebooks, raspberry pi, e-readers etc.

Same for all the smaller dedicated devices (audio recorders, camera, controllers etc.)

Those didn't go the barrel plug route in the first place to allow for charging through the same port, and would have been a loophole if barrel was mandated. USB-C was honestly the only option that made sense IMHO.


tablets, chromebooks

Most of those used either USB or a barrel plug depending on their size.

raspberry pi, e-readers

USB.

Same for all the smaller dedicated devices (audio recorders, camera, controllers etc.)

Many of those use smaller barrel plugs, appropriate for their lower voltage.

The main problem with USB-C is the tiny fragile connector (search for images of "bent USB-C"), and the fact that it's a standard that tries to be what should really be a bunch of separate standards. It's hard to get a barrel plug wrong. It's too easy to get USB-C wrong, and cause damaged devices:

https://news.ycombinator.com/item?id=33713713


nope. post here from 9/11 2001, no warning [0]. it's fine if they added a check recently to flag backdated posts, but there's no telling how many incorrectly-timed things went up before they added that ([0] is from about a year ago, fwiw). the whole early history of the platform is questionable, and it's just shoddy protocol design.

[0] https://bsky.app/profile/lul4.bsky.social/post/3kgaesbxs7f25

(if you work for bsky please don't add a flag to that, it's my favorite party trick)


Looking at the JSON data in dev tools, it looks like there are separate `createdAt` and `indexedAt` fields, the latter of which was probably a later addition. For your—likely pre-migration—post, both are set to 9/11. On more recent posts, they're separate dates.


That post does indeed predate bluesky tracking index times, I remember seeing it before they announced that change. I believe it was motivated by other migration services becoming popular. Forward-dating was fixed even earlier, I think, since it might allow people to "pin" their posts to the top of reverse-chronological feeds.

Some of my favourite backdated posts are from the years 1776 and 1.


More specifically the reason we didn’t have an index time for that post was an architectural migration which lost our prior witness times. That was pretty early on. At this point we’d take pains to preserve those timestamps, and I’m fairly sure we will need to publish them for other folks to use at some point


bleh. i don't mind in principle having robots do art and writing for us, but their chronic inability to be properly cynical stains everything they produce. it's all "big bang theory" flavored, for lack of a better phrase.


The obvious solution is to create a robot capable of feeling pain and dread.


Perhaps those are an essential ingredient for a full consciousness or experience of what we've agreed by consensus to call reality, but the parental part of me holds on desperately to the hope that if we create anew, those we create might have a better experience with vague gesture at everything than us. :)


...give it terribly painful diodes down its left side.


You beat me to it!


ham optimizes for the wrong thing, imo. look at ft8: perfect for making contacts at low power with stations far, far away, but really only tuned to the particular task of making contacts.

you can package some text alongside, but fundamentally all amateur operators are looking for is a SYN / ACK with callsigns.


There's also JS8call which is a modified version of FT8 meant for actual communication. IIRC you can do some neat things with it, like relaying a message through another user if you don't have a direct path to the recipient.


Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: