News for hackers. Stuff that matters.

madospace

Re:Ask HN: How are you securing your NPM dependencies? on Wednesday May 13, 2026 @02:58PM (#48125962)
Neat idea to add a scheduled audit! going to steal it.
Re:Ask HN: How are you securing your NPM dependencies? on Wednesday May 13, 2026 @12:29PM (#48124101)
Curious to know how are you going to ensure right security patches are getting updated in-time. Most of my troubles are that I have fixed version of packages that are older than a year old. Now I am scared to update anything :)
Re:Global Task Exchange Protocol on Saturday April 16, 2016 @10:08PM (#11513180)
For now TXT records will work, till it becomes a stable one, then it can be moved to either SRV or its own set of records
Re:Global Task Exchange Protocol on Saturday April 16, 2016 @02:53PM (#11511774)
User roles-permission is indeed a complicated problem to solve. But do you think this will need so much complication?

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.

Re:Global Task Exchange Protocol on Saturday April 16, 2016 @02:19PM (#11511658)
> though you can fake it with TXT records.

That is right. I will update the proposal thanks!

Thanks a lot for the suggestion. I love what IndieWeb is doing.

Re:Global Task Exchange Protocol on Saturday April 16, 2016 @02:13PM (#11511633)
Partially I agree with you. This is to get rid of the hacks people do to work across organization wall.

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.

Re:Global Task Exchange Protocol on Saturday April 16, 2016 @01:03PM (#11511308)
> I'm not sure what a recursive calendar event is. Are you reading "recurring" instead of recursive?

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 ?

Re:Global Task Exchange Protocol on Saturday April 16, 2016 @12:12PM (#11511102)
So any task with `Parent-Id` will be a sub-task. If User owns the tasks he can see the subtasks tree also. but if you own the sub task alone, for you it is like a normal task with an out of scope parent.

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.

Re:Global Task Exchange Protocol on Saturday April 16, 2016 @11:44AM (#11510985)
Good point, I will be adding them shortly.

For example - Project management involving multiple Organization. - Freelancers to work closely with the team - Open source Project development

Re:Global Task Exchange Protocol on Saturday April 16, 2016 @11:43AM (#11510974)
Actually most task management systems allow that today, through APIs, but you will need some glue to fix them together, like IFTTT or Zapier.

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.

Re:Global Task Exchange Protocol on Saturday April 16, 2016 @11:01AM (#11510820)
I wonder if this can work for task distribution. Certainly the idea of using these bytes of information to automate few things, of course yes!
Re:Global Task Exchange Protocol on Saturday April 16, 2016 @10:22AM (#11510682)
Amazing, I think if we keep identity management as a part of configuration then it will be easier for development, till one protocol becomes standard. I will try to add this as a default identity management. Thanks for the link.
Re:Global Task Exchange Protocol on Saturday April 16, 2016 @09:39AM (#11510552)
Of course. I am starting a basic implementation with asana hook.
Re:Global Task Exchange Protocol on Saturday April 16, 2016 @09:36AM (#11510538)
Totally agree. In my view, if nobody is thinking about it then nobody is implementing it.
Re:Apply HN: Grid – let the AI choose your date on Thursday April 07, 2016 @01:13AM (#11444879)
Yes that is a good point.

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 )

Re:Apply HN: Grid – let the AI choose your date on Thursday April 07, 2016 @12:34AM (#11444745)
At this moment depending on all of your social activity (location, tweets, fb updates, comments, photos etc), there are 63 (last one is you!)similar minded people. Of course you don't want to date all of them :-)

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...

( Read More... | 5 comments | 4 points | on HN )

Older »