I see that actually as a solution, a watch list is only as good as the data it contains, we need to pollute the watch lists so they are no longer useful anymore, so everybody should do it, if everybody does it, a watch list of 100% of the people is useless, you can't search for specific matches since it's full of everybody and anybody
so actually, pushing this past critical mass and towards overload seems to be the best solution, if you can pollute the list with bogus data, then you get bonus points;)
additionally, a free information and open bittorrent system which would copy and duplicate everything added to the system, with nobody interested in any particular part of the data, but just data mule-ing it around the internet infinitely with bandwidth caps to protect those with limited capacity would create enough bogus data to make any investigation pointless and enough copies to stop people from preventing the informations dissemination, I think this is the direction we're heading...
Exactly, he was detained and had less rights than people who were arrested, doesn't that strike you as odd, how can rights be taken away from you, isn't that the whole point of them being rights, that the exist regardless of any particular situation.
So now the cops can detail you and remove rights that you have but not arrest you and therefore have no burden of proof required in order for that person to have as much protection.
That's fucked up right there.....It's just a tool of intimidation, not of justice and it seems to be getting used in ACTUAL intimidation instead of the pursuit of justice too.....awesome!!
you know, we have this thing called the internet in spain, what it lets you do, is make copies of data online, so you don't have to physically transport data through checkpoints
who would actually do this any other way? I mean, it's so easy to dump stuff online encrypted and pick it up at the other side and there is nothing to physically catch middle.....that and copy it to a dozen other physical locations, just in case.
well, just ask Sarah Palin to keep a close eye on them, just over there and you'll have plenty of time to know if those dammed ruskies are up to no darn good.....
PROTIP: you were never the land of the free, nor the land of the brave
Re:They shot themselves in the foot
on
The Last GUADEC?
·
· Score: 1
I'm not interested in constructive responses, since it was those very constructive responses that led us down this path in the first place, to a world where we accomplish a tiny fraction of our potential and if thats the case, fuck constructive responses.
if my responses make you think about jumping off the bandwagon, then well, since you contributed nothing in the first place, you surely won't be missed when you're gone, right?
Re:They shot themselves in the foot
on
The Last GUADEC?
·
· Score: 1
ok, so basically a language nobody gives a flying fuck about......ok, just wanted to clear that up....
Re:They shot themselves in the foot
on
The Last GUADEC?
·
· Score: 1
developers don't "create" bugs, we don't sit down and say, hey, lets create a bug! and then go about making one, most of the time, we believe our code doesn't have bugs, cause if we thought it had bugs, we'd write it a different way, or we'd know about the bug in the first place and it'd be in our list of things to fix, normally those things are fixed quickly because we knew it was there, but things we don't know about, well, how do you expect us to find it? I didn't find it whilst I was writing the code and I'm the brain doing the typing, if I can't find it then, what do you think the chance of me finding out afterwards will be?
other people are very good at finding bugs in my code, if they exist, because they have a different mindset and think about things differently than I do, they think of a circumstance I didn't think of, great, you found the bug! but I didnt know it was there.....
so I think it's kind of normal that other people will find bugs in your code that you didn't know existed, so it makes perfect sense to reward those people to find them, paying ME to find them is going to not pay off in a big way, cause if I knew how to find bugs in my own code, I would have done it already and fixed it.
the point of programming an cryptological algorithm is that the code executes an encryption algorithm, not that the source code IS the encryption algorithm......;)
When I change the dom structure of my website and the according javascript, you'll be required to change your javascript too in order to work with that new structure, when I change the result of a webservice, or call a new webservice or split into two webservice that was previous one, you'll be required to record your customised version of that too.
so basically, no, your fantasy idea is just that, fantasy, nobody in their right mind would do it, it would constantly force you to work for nothing with practically zero payback and if you did this on multiple websites, you'd quite literally be committing yourself to hundreds of hours of unnecessary work just so you can masturbate over the fact that you have the source code.
you like that idea? then you sir are welcome to it, but I as a web site developer will provide you ZERO HOURS of customer support when it breaks and I will redirect every person who asks me about this topic to your inbox and you can deal with them.
I think due to perls nature, it skews people in the direction of writing unreadable code, easier than other languages, so even though it's not perls fault, people learn bad habits, combine them with shortcuts, sidestep techniques, workarounds and ways to reduce the code length and before you know it, you're the only one which can understand the code.
thats my experience from reading other peoples perl code. the language is so flexible, it allows you enough rope to hang you with...
of course, you should avoid writing code which is not obvious, but sometimes this is impossible, so comments are useful.
something I've been doing, is writing code notes about thoughts i've had in relation to the code which generates the thought, so I can write things like// NOTE: this function looks easy, but internally it's doing too much work, I need to break it into chunks
then over time, they can accumulate, get deleted, add more and become a sort of meta-layer allowing people to understand things I've thought in relation to the code written, it's working out quite well so far....would be better if I didnt need to do it, but well, whatever....
exactly, it's a non-physical entity.....
hahahhahahaha, well done sir!
I see that actually as a solution, a watch list is only as good as the data it contains, we need to pollute the watch lists so they are no longer useful anymore, so everybody should do it, if everybody does it, a watch list of 100% of the people is useless, you can't search for specific matches since it's full of everybody and anybody
so actually, pushing this past critical mass and towards overload seems to be the best solution, if you can pollute the list with bogus data, then you get bonus points ;)
additionally, a free information and open bittorrent system which would copy and duplicate everything added to the system, with nobody interested in any particular part of the data, but just data mule-ing it around the internet infinitely with bandwidth caps to protect those with limited capacity would create enough bogus data to make any investigation pointless and enough copies to stop people from preventing the informations dissemination, I think this is the direction we're heading...
yes, I have great teeth as well, thanks!
BTW: it's fluoridation, just sayin'
one word: bittorrent
nice homophobia you've got there, pity you didn't use your real account name like a decent human so we could know which scum said it :/
cause it seems that over time, they are becoming the same thing :(
Exactly, he was detained and had less rights than people who were arrested, doesn't that strike you as odd, how can rights be taken away from you, isn't that the whole point of them being rights, that the exist regardless of any particular situation.
So now the cops can detail you and remove rights that you have but not arrest you and therefore have no burden of proof required in order for that person to have as much protection.
That's fucked up right there.....It's just a tool of intimidation, not of justice and it seems to be getting used in ACTUAL intimidation instead of the pursuit of justice too.....awesome!!
you know, we have this thing called the internet in spain, what it lets you do, is make copies of data online, so you don't have to physically transport data through checkpoints
who would actually do this any other way? I mean, it's so easy to dump stuff online encrypted and pick it up at the other side and there is nothing to physically catch middle.....that and copy it to a dozen other physical locations, just in case.
only because they never got it to compile....
*hands up* !! I'll go quietly!!
well, just ask Sarah Palin to keep a close eye on them, just over there and you'll have plenty of time to know if those dammed ruskies are up to no darn good.....
PROTIP: you were never the land of the free, nor the land of the brave
I'm not interested in constructive responses, since it was those very constructive responses that led us down this path in the first place, to a world where we accomplish a tiny fraction of our potential and if thats the case, fuck constructive responses.
if my responses make you think about jumping off the bandwagon, then well, since you contributed nothing in the first place, you surely won't be missed when you're gone, right?
ok, so basically a language nobody gives a flying fuck about......ok, just wanted to clear that up....
and that favourite language is??
hahahahahahha, well done sir!
You sure showed him didn't you!!
developers don't "create" bugs, we don't sit down and say, hey, lets create a bug! and then go about making one, most of the time, we believe our code doesn't have bugs, cause if we thought it had bugs, we'd write it a different way, or we'd know about the bug in the first place and it'd be in our list of things to fix, normally those things are fixed quickly because we knew it was there, but things we don't know about, well, how do you expect us to find it? I didn't find it whilst I was writing the code and I'm the brain doing the typing, if I can't find it then, what do you think the chance of me finding out afterwards will be?
other people are very good at finding bugs in my code, if they exist, because they have a different mindset and think about things differently than I do, they think of a circumstance I didn't think of, great, you found the bug! but I didnt know it was there.....
so I think it's kind of normal that other people will find bugs in your code that you didn't know existed, so it makes perfect sense to reward those people to find them, paying ME to find them is going to not pay off in a big way, cause if I knew how to find bugs in my own code, I would have done it already and fixed it.
wrong, marriage existed long before the christians started to use it.......
> (has Dilbert thought you nothing?).
I suppose he doesn't think about many people except himself, thats why he doesnt teach anymore :)
the point of programming an cryptological algorithm is that the code executes an encryption algorithm, not that the source code IS the encryption algorithm...... ;)
What an awful idea......
When I change the dom structure of my website and the according javascript, you'll be required to change your javascript too in order to work with that new structure, when I change the result of a webservice, or call a new webservice or split into two webservice that was previous one, you'll be required to record your customised version of that too.
so basically, no, your fantasy idea is just that, fantasy, nobody in their right mind would do it, it would constantly force you to work for nothing with practically zero payback and if you did this on multiple websites, you'd quite literally be committing yourself to hundreds of hours of unnecessary work just so you can masturbate over the fact that you have the source code.
you like that idea? then you sir are welcome to it, but I as a web site developer will provide you ZERO HOURS of customer support when it breaks and I will redirect every person who asks me about this topic to your inbox and you can deal with them.
I think due to perls nature, it skews people in the direction of writing unreadable code, easier than other languages, so even though it's not perls fault, people learn bad habits, combine them with shortcuts, sidestep techniques, workarounds and ways to reduce the code length and before you know it, you're the only one which can understand the code.
thats my experience from reading other peoples perl code. the language is so flexible, it allows you enough rope to hang you with...
of course, you should avoid writing code which is not obvious, but sometimes this is impossible, so comments are useful.
something I've been doing, is writing code notes about thoughts i've had in relation to the code which generates the thought, so I can write things like // NOTE: this function looks easy, but internally it's doing too much work, I need to break it into chunks
then over time, they can accumulate, get deleted, add more and become a sort of meta-layer allowing people to understand things I've thought in relation to the code written, it's working out quite well so far....would be better if I didnt need to do it, but well, whatever....