iroddis

Methylphenidate is a stimulant medication [0]. Maybe you meant something else, like atomoxetine?

[0] https://en.wikipedia.org/wiki/Methylphenidate?wprov=sfti1#

Your API only provides the ticker as the identifier, which makes me think either you have survivorship bias or aren’t tracking things appropriately. Tickers are delisted and recycled all the time. Do you provide a more industry-standard or custom reference ID as an option?

I think just a dash.

There aren't many songs about tech work, and it's crazy that this one, that stills feel current, was released in 1979.

Thank you for posting, I’ve been eyeing using TreeSitter to make some toy languages, and this looks like a great example to learn from.

The error.rs error type definitions and the pub(crate) directives were both new to me. It’s crazy to me just how much rust continues to evolve well after the 1.0 release. Error handling in particular seems to be a point of confusion; I’ve seen (and bookmarked) many posts on HN about it. The thiserror crate was new to me, and seems really nice.

I’ve tried a few of these, but most of them seem to be following the trend of folding other shell functionality into one tool. Searching for contents (find + grep -H, or ripgrep), filtering (grep), sorting (ls does it natively, or you can use sort, sort -h for sorting human readable sizes), the list goes on and on.

I guess this is a mini lament that many of these tools are moving away from the Unix philosophy of do one thing well, and make it easy to chain.

And a last very small lament that BeOS didn’t succeed, and their filesystem-as-a-database approach didn’t become more standard.

I'm not GP, but I also dislike Slack's lack of user focus and generally interrupt-driven workflow. Campsite sounds really great, and I may well be interested even at the $16/mo price point, but the website does a poor job of telling me much about the product aside from how great "posts" are. The big screenshot on the front page looks a lot like just a Slack clone.

The premise of better long-form discussion was intriguing enough that I went looking on YouTube for a review or demo of Campsite. No luck, I just got endless results for camping apps, even after many iterations on search terms.

Maybe you could post some videos or links on your page about how Campsite matches Slack features, and then how it exceeds them? There are so many issues with Slack, from blurry screen sharing to lack of syntax highlighting w/o snippets to the channel list mysteriously resorting itself constant, I would love something that could replace it that also made remote-first collaboration better.

I’m still holding out hope that Telo Trucks will ship in a reasonable timeframe.

There are so many nuances here, but perhaps you could maintain two coalescing structures: what's free and what's used, complements one one another. Adding to one means removing from the other. One might give you a more constrained search space than the other.

An ordered structure feels like the way to go, here, since you said "nearest gaps". Once you know the time you'll get locality in your search. You could also run the search in both directions on two threads.

Can you give any more details about the range queries? e.g. are you interested in finding any gap of at least duration X, or the number of bookings in a date range?

Put another way, are you more interested in what's been consumed, or what's free?

You mentioned that the intervals are disjoint, but are they adjacent? I've had success with maintaining a "coalescing interval set" structure, where adjacent intervals are merged into a single interval. It's very, very efficient for lookups, and not terrible for insertion / removal of intervals. At the very least it might work as a view for your read-heavy processes.

You mentioned shop scheduling below as well. If your intervals represent booked time, you could also insert 'unavailable' time into the coalesced set, so that, when fully booked, the interval set is reduced to a single interval.

It’s hard to address this submission as it is so hyperbolic that it’s difficult to pick it apart. It has a strong second amendment vibe, where the choice is between self-regulation or a future armed stand-off with the government. This is a false dichotomy.

There are already other, non-regulatory, systems in place to deal with issues like this. Market forces and law suits spring to mind immediately.

I'll be honest, I was waiting for Orion RC 128 to get released, since that's when the multi-container feature was supposed to land (according to [1]). I just updated Orion RC, and the profile management is pretty nice, but seems to be missing some things: (1) assigning full or partial URLs to always open in a specific profile, and (2) profile assignment on a per-tab basis, rather than per-window.

Other than that, the browser is pretty amazing. Blazingly fast, support for both Firefox and Chrome extensions, and lots of customization. There's a lot to love about it, and as soon as the two features above land I'll likely be switching to it as my primary driver (on MacOS)

[1] https://orionfeedback.org/d/43-something-like-firefox-multi-...

I also pay for Orion, but can’t use it much until the multi-container support is working well. Right now Firefox is the only browser that does this right.

Upvoting you in the hopes that more people in this thread will put their money where their stated principles are and help support a privacy focused browser with clear funding sources so that Orion doesn’t go the way of Opera.

I wish Slack would focus on end-user experience rather than extra org-level features. It’s like being offered a meal when you complain of being tired. Sure, it’s great, but I’d rather have what I ask for.

How about code highlighting in markdown-style triple-backtick blocks instead of requiring snippets? Or the ability to have a separate window per workspace in the native app? Or maybe marking thread responses that echo to the channel marked as read when I see them in the channel, rather than requiring an explicit click into the Threads section? Or a huddle video feed that isn’t blurry at 4K so I can actually read the text getting shared?

I do like Slack, but some of these missing features just feel like missed table-stakes, and their focus seems elsewhere.

I think it’s a bit remiss to not include all of the downsides of this approach. sudo allows control over which groups can exercise which commands, what args those commands accept, subshell spawns, etc, etc, etc.

This approach loses a lot of this fine-grained control, and also relies on trusted keys, which are harder to manage than editing a sudoers file.

To see all the amazing things that sudo can do, I’d really recommend the Sudo Mastery book.

The annotation tools are really, really good. The colour palette seems well thought out to easily highlight important parts of screenshots. It’s been very helpful when collaborating with people, annotating graphs and logs on the fly.

Lots of good apps here, but I haven’t seen Shottr, yet. Amazing screenshotting tool, I use it all the time.

Fmail2 app for a more native fastmail client is also very nice.

I don’t use Adobe, but this feels like it’s missing some context around when / how the private data is accessed. Is it for AI? To satisfy law enforcement requests? For compression or some technical need?

To make the most charitable case for Adobe, this could just be clarifying that there is no encryption at rest.

It’s not clear if “may” means that the user is giving them permission when they agree to the T&C, or if there are other circumstances where they “may” be required to access the data.

Uncharitable cases would be for AI training, life-ruining tech like automated scanning for illegal content that gets automatically forwarded to authorities, etc.

I read your linked article, and I’m so sorry for what you went through and what you continue to live with. Two members of my immediate family were diagnosed with cancer within a month of each other. One didn’t make it as a result of just how punishing the adjuvant treatments were. She succumbed to an infection and couldn’t fight it off.

Being in the treatment rooms for both people made surgery, chemo, and radiation all feel like blunt instruments that crushed the patients. Even 3 months post treatment, my surviving family member suffers from the effects of the treatments, and likely will for up to a year we’ve been told.

I hope you get some relief and hope for your situation. Your writing is exceptional.

A large codebase would require many pictures. Maybe it's possible if you took a video and figured out a way to optimally scroll the data so as to reconstitute the codebase via AI / OCR, but that's a lot more work than most people are willing to put into it.

The goal isn't to stop all possible avenues of IP extraction, just to make the barrier a bit higher than git clone / git push.

Modern software? Not many. Excalidraw and Shottr (screenshots) are so easy and intuitive, I really appreciate them.

Historically: BeOS, WebOS from Palm, and any BBS software ever. The joy of hearing people call in never faded, even as the world moved on.

I have never used it, but I often see Lazarus mentioned on HN as a multi-platform solution. The downside is that it is Delphi / Pascal, but perhaps the lure of cross-platform native apps would make it worth the investment?

Thank you for posting this. Async vs sync is a tough design decision, and the ecosystem of crates in async gets further partitioned by the runtime. Tokio seems to be the leader, but making the async runtime a second-class consideration has just made the refactor risk much higher.

I like async, and think it makes a lot of sense in many use cases, but it also feels like a poisoned pill, where it’s all or nothing.

LORD was so much fun. I also ran a BBS, first on Wildcat (RIP graphics were amazing), then on RoboFX. Bought all of the above by saving up $2/week allowance.

RoboFX was insane. It was this little-known host that offered a full windowing system using a client that fit on a single disk. It had movable windows, image viewing, messaging, forums, downloads, the works. Truly incredible for the time, but it was released just at the end of the BBS era. Along with BeOS and WebOS, some of the saddest technologies that never caught on.

Thanks for the memories!

In this case it sounds like just a bit longer than is necessary to make ends meet.

FUSE is used to present a file system interface of something that isn’t a file system. E.g. present an LDAP directory as a file system.

Writing FUSE drivers is pretty frustrating, though, and not well supported by all OSs.

My takeaway is that this project discards FUSE in favour of making an NFS server that can be easily extended to do the same thing: present non-file system systems as mountable nfs remote file systems.

It’s a neat idea, and does avoid any extra kernel drivers, etc. A safer abstraction at the cost of adding a network stack and NFS’s sometimes wonky effects (especially with hard mounts).

I love this idea so much. It’s a shame that it would all get lost when passing through a recruiter or when needing to re-enter all the info on applications.

To save others from searching, RLHF [1] is Reinforcement Learning from Human Feedback

[1] https://en.wikipedia.org/wiki/Reinforcement_learning_from_hu...

This really reminds me of FidoNet mail [1] back in the good old days of BBS. What’s old is new again; now with 100% more json!

[1] https://en.wikipedia.org/wiki/FidoNet?wprov=sfti1