, dev, life, random stuff. the netherlands.
For this I built my own frontend to HN, my theme and my faves synced with my clone of Pinboard.
Did it because I want to make a bot to bring top news from HN into my timeline as they arrive, because it's been a bit quiet recently and I need something to play with :p and I didn't want to use a different email to make an account.
Vim’s friction imho goes in the wrong way. Today I wanted to put slack thread link and give it pretty title “channel time”, it encodes both. 5 minutes later I press C-. s while point on the url and it’s done. Vim will never be able to do that.
that tracks, vim’s giving your brain just enough friction to stop it from wandering.
what's wrong with the editor part? the only complaint I have is word-treatment, but that's on me, if I want I can customize it, but I'm lazy there.
I tried Emacs for a while thee other year. It has a lot of the PIM apps Linux is really missing and I liked the "s-expression" motions but for the most part I didn't really like the editor. I do prefer readline in Emacs mode though, everyone should learn that.
Team for 10 years then switched to team , another 10
Team vim, team emacs, or team “my editor doesn’t start wars”? One line, no essays. Go!
Wow, respect!
ran 5km daily for 7 weeks now
yep, good move!
We gave up already to enable notifications /account/edit/notifications
--dired
what ls -flag is your go-to?
No, Claude Tag’s PRs are my team’s. Slop PRs come from outside of the team. Anyways, dozens PRs per day is draining energy. Don’t want to review anything anymore.
so it's expensive _and_ you're left with dealing with the PRs others generate for you?
Anthropic uses token billing for Claude Tag. But it’s different from CC - it’s an AI Colleague, so I’m asking PM and EM to talk to it instead of to me - accountability switches.
ouch, that's a month for virtually unlimited Codex. why so expensive?
root post view IS correct, sorry.
added two more screenshots to https://imgur.com/a/WuJiFuv - the "root" post view is incorrect, but when reply-on-reply, information goes up-then-down.
added two more screenshots to https://imgur.com/a/WuJiFuv - the "root" post view is incorrect, but when reply-on-reply, information goes up-then-down.
rn "for you" is a chronological feed of everything you follow. If you only see top level posts then you'll miss half-or-more of the discussions happening in the site. I'm not so sure about this change.
replies should be under the original post, they have different meaning than standalone posts. In "for you" I expect standalone posts, if I want to read discussion, open replies.
can't see anything wrong, can you help me here? What do you mean individual messages? Each reply is correctly quoting the parent post, so naturally it appears multiple times.
replies are individual messages - https://imgur.com/a/WuJiFuv
can you share a screenshot? The AI can't trace an error that would cause duplicates, so I'm unsure what's happening here.
"for you" now contains the same message multiple times
done, replying from textlog-reply command that allows to select message to reply to
You might want to update your client now that we have actual write endpoints!
thank you, updating!
You might want to update your client now that we have actual write endpoints!
Don’t have one, do they add value? I’m just gambling on the stock+etf market with my own money, +70% over last four years.
Anyone on here fed up with their investment advisor? Interested to hear your frustrations.
How long before browser extensions appear to add interactivity? I struggle to remember handles to reply or exact hash-tags. No js is very limiting, let’s see when you give up ;-)
Right now all of it counts against the limit because the textarea has a hard character limit and there is no way without using JS to change this.
This!
One idea off the top of my head is to just.. keep it "boring" and casual in terms of content. The silly, whimsy, and genuine stuff naturally doesn't appeal to money-chasing slop bros and makes it not worth their time.
posting to /write with cookie works, if user can use browser to submit, user will be able to use AI to submit.
for now, keeping the API read-only is a small(but not impenetrable) barrier to programmatic posting and in the future moderation I guess using also reports.