Recent submissions

Comment · 5 months ago
https://surmai.app/

I'm working on a Personal / Family travel organizer. Started as tool to allow me and SO to plan a trip together. There's been steady progress over the last couple years. Focus on privacy and ability to self-host. Of course, there is a managed version if one doesn't mind me having access to their data.

Comment · 4 years ago
Comment · 5 years ago
How does this compare to Apache Shiro?
Comment · 5 years ago
Fidelity has $0.65 per contract
Comment · 5 years ago
That is how most toll systems work. You load up a balance on the card $10/$20 and it deducts every time you cross a checkpoint.

The difference between this and a micropayment platform would be the fees. In the toll system, the fees are paid once. With a micropayment platform, the fees would be per transaction.

There can be a "self hosted" version of such a platform that say each content-provider can host but I am not sure it will work out against the cost of maintaining it includes much more than just hosting (securty, auditing, refunds, taxes etc).

Comment · 5 years ago
Oof I still remember the update that disabled re-sizing of the text box and people were up in arms about it. And there was a fork of Pidgin over it.
Comment · 5 years ago
I have been using Fastmail for a few years now. Pretty happy with them.
Comment · 6 years ago
Scaling is only half of it. There is a lot more to Jira than just CRUD over a few entities. It's trying to be issue tracking and project management rolled into one. For example:

- Workflows

- Access control over fields

- Custom fields

- Release management

- 3P plugins and integrations

- API access

I am far from being a fan of Jira but they do have a rather large set of features. Every time I evaluate the hottest new issue tracking and/or project management solution, there is something lacking as compared to Jira.

Comment · 6 years ago
An automated pet door. My dog loves to go in and out of the house every five minutes and whines annoyingly if he doesn't.
Comment · 6 years ago
Comment · 6 years ago
Comment · 6 years ago
It's what I call customer experience design. You can build this in terms of user stories, UI mocks, OpenAPI spec etc depending on your customer. This makes the expectations from the API interface very clear. Of course, it may also mean that I'd have to deviate from pure REST but that's easy when you see the customer value. Then the tradeoff between fast, easy and cheap is restricted to components that don't impact the end user and can be changed later. The last thing I'd want is to change my customer's workflow because my entity relationships change.
Comment · 6 years ago
Comment · 6 years ago
The answer depends on a lot of factors e.g. where are you based? Some states in the US allow you to do whatever using your own resources and your own free time. Even though it might be legally allowed, companies' contracts generally forbid you from doing anything competitive. So:

- Are you doing this using your won resources and time?

- Are you building a potentially competing product?

- What does your contract say about it?

- Can anyone still claim IP on what you've built so far? As in it seems you worked for someone before to build it, did you get compensated for it?

Of course, IANAL, so you'd want some professional advice.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton