Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:Troll! In the dungeon! Thought you'd want to kn (Score 1) 559

As a developer currently working on a project involving an ID card reader, I think this problem *could* maybe be solved with some clever and secure electronic signature infrastructure. I don't know how it is in other countries, but here in Belgium our ID cards allow us to digitally sign documents of all sorts.
It's very much used for tax-papers, in particular, and from a technological point-of-view, I don't think it's unreasonable to build an identification infrastructure for social networks around this.
The obvious privacy issue could be addressed if the verification entity was independent and trustful, much like we see Certification Authorities (CA) for SSL. These authorities migt then be trusted to only hand out the age of an individual signing up for the account. This would, in effect, act like an age barrier.

Comment It's called efficient management. (Score 1) 509

This is something that should be handled by his superior. It's his superior's job to slap him on the wrist if he moans about code reviews and doesn't take being up to date seriously. In my experience, management that doesn't have the guts or skills for straightforward communication is one of the worst obstacles to efficiency.

Comment Re:Newbie (Score 1) 1051

Indeed, it seems weird, but understandable. I can only talk from what I know; ie. Qt development. There, it's technically possible, but often advised against for anything bigger than trivial fixes. It's common to have more than one maintainer of a given functionality for that reason. However, sometimes, a subject simply lacks the necessary manpower of knowledgeable-enough folk for efficient cross reviewing. The maintainer is given a certain amount of *trust*. Not sure about this, but I think reviewing maintainer submissions would simply create too much of an overhead in a project the size of Linux.

Slashdot Top Deals

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...