madospace
Show HN: Uptime Monitoring for Your Mac
Show HN: Log what you ship in your voice
A single-binary CLI that crawls your repos, summarizes the work in your own voice with the AI of your choice, and stores it where you own the data.
Spam filters are the consent layer. That's embarrassing
Ask HN: How are you securing your NPM dependencies?
There are few obvious things like adding min-release-age, ignore-scripts and save-exact. What other practice we can follow to ensure we are minimizing the damage, especially with chained dependencies.
Show HN: RedactScreen – Share your screen, not secrets
RedactScreen creates a virtual screen that hides your sensitive apps (Slack, Mail, Messages) from everyone else on the call. Your screen, minus the parts that aren't their business.
Show HN: FixMyNPM, CLI to fix your insecure npm config
https://github.com/madhugb/FixMyNPM
With recent issues with npm configuration issues it's essential that we have a tool like this to fix basic issues
Bridging the Gap Between Slack and Email Users
I am open sourcing all of my ideas
As far as I think, it is straight forward. But I also agree when you work in a complicated hierarchy, you probably need these systems.
That is right. I will update the proposal thanks!
Thanks a lot for the suggestion. I love what IndieWeb is doing.
Let me try to explain: A task is not just a text, it has context and history, and meta data. Unfortunately people use email for this which creates 100s of messages in a thread. Instead, if you keep single entity and keep updating it like you would do in any task management system, it will create better meta data and less headache to manage.
yes! sorry i misunderstood. and now we have solution to both recurring and recursive!
> The same `Parent-Id` solution as subtasks should also work here. Yes, it will - but does it complicate the architecture ?
Recursive tasks works exactly like recursive calendar events.
I have not thought about Sub-Projects, any suggestions?
User-Group - That is interesting, I think it should not change the behaviour based on the Type of email, which is difficult to determine.
When a user leaves do the same thing as email - either purge them all or re assign it to someone else.
For example - Project management involving multiple Organization. - Freelancers to work closely with the team - Open source Project development
This is not limited to interoperability, cross domain / organization collaboration tool. It is almost like asking what sort of e-mail tools can be built on top of email protocol.
You are right about the commercially viable aspect. But if I wanted to make it commercially viable I would not have made it open.
I think something like this WILL be the `interoperate` set of data that you are talking about.
Global Task Exchange Protocol
So the idea here is not to match "Everything". Choose your field of interest (Movies, Hobbies, Sports, Politics, Art, Travel, etc etc). Here I assume that people don't talk about only Football (for instance) when they are on a date with someone. However I agree that people may not (now that I think of it) talk about everything in public, but it is not impossible to co-relate persona based on past history of interactions.
If We allow only 64 male and 64 female at first they all have no choice but to see all others ( even there the profiles are nearer to you, if they are a good match )
Apply HN: Grid – let the AI choose your date
A Grid is an infinite matrix of people. Users connect their social profiles and the Grid will analyze activities and co-relate them with people who have similar activities.Everyone in adjacent grid are people with similar activities on social networks and you can choose and ping them for a date or whatever. You cannot ping a person outside 8 x 8 of your grid. But you can ask recommendation or...