mschwar99

From what I remember poking around at Hansa that's not true. Each vendor / user had a public key associated with their account. All text communication through the website was supposed to be with GPG encrypted text secured by private keys unavailable to website.

So law enforcement has lots of encrypted text along with some clear text from users not informed enough to follow any kind of opsec.

The 5th covers several rights of a person accused of a crime. In this context they are referring to the amendment's protection against self incrimination: "nor shall be compelled in any criminal case to be a witness against himself."

A person has the right to decline to answer questions if they believe that their answers could be used against them as evidence of a criminal act. This particular proceeding is civil rather than criminal so its outcome can't result in any criminal convictions. However, if he were later to be charged with a crime and tried in a criminal court any testimony he gave in this civil action could be used against him as evidence in the criminal trial.

Yesterday had some impact, but these bills are still very much on track to become law. All the post mortems today aren't communicating that very well.

The closure vote in the Senate on the 24th needs at least 41 no votes to prevent the bill from moving into markup. While more senators have announced opposition or doubt, current headcounts put "no" votes on closure only in the single digits.

Unlike subcommittee hearings, the markup hearings are closed door and allow the Senate to draft a final version of the bill without public scrutiny or testimony from tech leaders. If this legislation follows suite with other controversial legislation, the bill that emerges will have enough back room deals attached to let both the latecomer opposition and the White House to declare the bill a healthy compromise irregardless of the facts.

People need to be on the phone to their senators. Urge them to vote no on closure so that the inevitable compromise bill can be debated in public with input of experts.

I think its a good idea and will give it a try next time I need to spin up a theme.

Ignore the negativity in these comments. This is a great example of scratching your own itch and being generous enough to place it on Github. Who cares if the bulk of WordPress users won't grok it? That's no reason not to build it. Thanks for sharing.

Its really great of you guys to offer this service on your own dime - thank you. Its also very shrewd marketing, and I hope it pays off for you.

Besides entertainment value doesn't all of this back and forth reduce down to the age old "use the right tool for the job in front of you"?

Node.js as it currently stands isn't the best solution for applications that will involve CPU intensive tasks. Perhaps at the outset of a project you don't know when and where those types of tasks will pop up so basing an entire architecture on it might be risky.

However, it seems to me that regardless of the above, there are tasks Node excels at and it would be silly to dismiss it as a technical solution all together. I'm building browser based games with it and love working with Node. The bulk of the logic is in the client and Node serves as the glue that allows people to play games together from different clients. Nothing I have read gives me pause about this implementation.

Often times they are stuck using insecure browsers because some archaic piece of in house software depends on obsolete features only present in dated versions of browsers. They choose to skip updates because they don't want to spend the cash rebuilding the timekeeping system to work with anything other than IE <= 7.

I'm not seeing anything in the thread that verifies the title of this submission. Am I missing something?

It looks to be people discussing the iOS episodes and patent trolls in general.

Edit - Yup my fault, I zeroed in on the responses.