Idea: Encode Smileys in Text Realization: Display an image instead of rendering a glyph. Okay. Like different fonts, now everybody can have different smileys, but with a standard for codepoints. no questions anymore, if:) is a smiley or only:-) is one. Now different vendors implemented the smileys in totally different ways (apple rendering a yellow heart (btw. WTF), android a hairy heart (even more WTF)). Next: The big apps like whatsapp bringt their own (or a apple clone) set of emojis. So we can get back to application specific smileys with:smile: or a simliar encoding. This will remove the need for complicated unicode handling (did you read the section about composing i.e. colors and smileys?). And while we're at this: Why does a smily need a skin color? Smileys are yellow.
A person has a problem, solves it with code and shares his program. He improves on the program, as he uses it and needs it, others benefit, too. He will be way more efficient and his product way more useful, than a hand full of programmiers, with some unclear specification, which needs to be worked on to check bulletpoints on a TODO list. They will do what they are told to, while he will do what he needs for his program to work fine. And if he sees that some idea won't work out, he will find another solution, instead of pushing hard until the TODO list item is finished, even when the feature will be useless.
That's why you say, "we build our own cloud". If there is somebody with some skill show them a demo with openstack or something like this. Then continue to use your servers.
Any journalling FS should provide a consistent state, checksumming FS like BTRFS or ZFS even provable. So they won't lose data, which is written and in a consistent state, and unwritten data cannot be saved by definition.
seems like they generate the key on the server side (tried with fake mail, and they said they send me how to download it). startssl at least uses firefox' builtin keygeneration.
Which makes startssl untrustworthy for your friends. So, you signed this? Did you, or is your key leaked and you did not revoke it, because its to costly?
I think the future is in fuzzing. While an advertiser can spot the hole in a "null"-fingerprint, as soon as one of the features are not neutral, its hard to spot if a value is randomized or real. You have neither reference to the real values, nor to the fake value, the plugin uses. So an advertiser needs to do good datamining to see what features are actually still usable for tracking and which ones are not. If he includes one to much, he loses me on the next new tab, when the value changes. If he does not include a certain feature, it's possible, that this was the unique value of my browser. So his job gets harder and more costly.
who cares? What's the last time you got a corrupted file? Filetransfers via the internet use checksums, they are "there or not there", so you need some faulty disk. floppys had its problems, but a bitflip on a harddrive? Not that often...
> But it's very normal to have such logentries in a nginx log, so I doubt anybody will look for them. That is not the question.
There is a tracking company, which looks for new ways to track users, who block js. They put some links over the page, which open tcp-connections onmouseover. Next they look for a webserver, which logs them (nginx seems to work). Then they correlate uniqueid.trackingcompany.example as hostname with your ip and the cookies the domain set, which included the tracking link.
Always think, like you want to use the techniques against others, what would you do, to maximize the tracking? Find out, what's possible. Then you have at least some limit, what could be used against you, even if it's not (yet).
So? Install a fresh AOKP ROM. No googly connections at all. It's your fault to install gapps, which connect to google all the time (as that's the purpose of gapps. Give you i.e. GCM, which needs a persistent connection to google)
isn't windows one of the softwares, which tell you "please accept the EULA", when you click next without accepting? In this very moment, they tell you to accept it, without asking if you accept it. So its not anymore binding, as you just did what you were told to.
xp matured. And that XP was a disaster doesn't make 7 any better. Both are quite okay compared to 8/10, but it's still true, that it constantly went downhill. And not light at the end of the tunnel.
> after the security people have stripped out all the M.S. Snoops. It's not like MS is not putting new surveilance err bugfixes in, to continue providing the best experience to its users.
Slashdot Mirror
Almost all letters are the same, there are small differences for the l and spacing aroung ()
Idea: Encode Smileys in Text :) is a smiley or only :-) is one. :smile: or a simliar encoding. This will remove the need for complicated unicode handling (did you read the section about composing i.e. colors and smileys?). And while we're at this: Why does a smily need a skin color? Smileys are yellow.
Realization: Display an image instead of rendering a glyph.
Okay. Like different fonts, now everybody can have different smileys, but with a standard for codepoints. no questions anymore, if
Now different vendors implemented the smileys in totally different ways (apple rendering a yellow heart (btw. WTF), android a hairy heart (even more WTF)).
Next: The big apps like whatsapp bringt their own (or a apple clone) set of emojis.
So we can get back to application specific smileys with
Its just the same with another choice of default packages.
Its the "eat your own dogfood", what helps.
A person has a problem, solves it with code and shares his program. He improves on the program, as he uses it and needs it, others benefit, too. He will be way more efficient and his product way more useful, than a hand full of programmiers, with some unclear specification, which needs to be worked on to check bulletpoints on a TODO list. They will do what they are told to, while he will do what he needs for his program to work fine. And if he sees that some idea won't work out, he will find another solution, instead of pushing hard until the TODO list item is finished, even when the feature will be useless.
> become a serious issue since NSA
That's wrong.
This always was an issue. But now we know.
That's why you say, "we build our own cloud". If there is somebody with some skill show them a demo with openstack or something like this. Then continue to use your servers.
nilfs2 does.
Any journalling FS should provide a consistent state, checksumming FS like BTRFS or ZFS even provable.
So they won't lose data, which is written and in a consistent state, and unwritten data cannot be saved by definition.
With firefox i still have to use an addon, which adds html5=1 to youtube urls. Embedded videos i.e. on twitter always use flash, too.
On windows its caps lock, there shift stops the lock. on linux its case-reversing.
seems like they generate the key on the server side (tried with fake mail, and they said they send me how to download it).
startssl at least uses firefox' builtin keygeneration.
Which makes startssl untrustworthy for your friends. So, you signed this? Did you, or is your key leaked and you did not revoke it, because its to costly?
> Therefore the problem is you.
you're so very helpful.
What about trying to solve the problem in HIS COMPUTER?
No, let's get personal. HE is the problem.
m(
If you have to ask: no.
And then they're asking, why people read their news on shady facebook pages instead of the media sites.
On 80% of all news articles, the comments are more informative than the article.
scalable: free surplus storage (unencrypted) if you click here*.
* this button will unencrypt ALL your data
Yeah, there IS a lot of stuff.
I think the future is in fuzzing. While an advertiser can spot the hole in a "null"-fingerprint, as soon as one of the features are not neutral, its hard to spot if a value is randomized or real. You have neither reference to the real values, nor to the fake value, the plugin uses. So an advertiser needs to do good datamining to see what features are actually still usable for tracking and which ones are not. If he includes one to much, he loses me on the next new tab, when the value changes. If he does not include a certain feature, it's possible, that this was the unique value of my browser. So his job gets harder and more costly.
Which is no argument about stopping tracking feature by feature as you can. Maybe you just hit the feature, which identified you.
who cares? What's the last time you got a corrupted file? Filetransfers via the internet use checksums, they are "there or not there", so you need some faulty disk. floppys had its problems, but a bitflip on a harddrive? Not that often ...
It's always hard to prove your innocence, when somebody implies you're just hiding something.
So fill in a dmca counter notice and then wait until somebody tries to sue you ... they would need to prove their copyright.
> But it's very normal to have such logentries in a nginx log, so I doubt anybody will look for them.
That is not the question.
There is a tracking company, which looks for new ways to track users, who block js. They put some links over the page, which open tcp-connections onmouseover. Next they look for a webserver, which logs them (nginx seems to work). Then they correlate uniqueid.trackingcompany.example as hostname with your ip and the cookies the domain set, which included the tracking link.
Always think, like you want to use the techniques against others, what would you do, to maximize the tracking? Find out, what's possible. Then you have at least some limit, what could be used against you, even if it's not (yet).
So?
Install a fresh AOKP ROM. No googly connections at all.
It's your fault to install gapps, which connect to google all the time (as that's the purpose of gapps. Give you i.e. GCM, which needs a persistent connection to google)
isn't windows one of the softwares, which tell you "please accept the EULA", when you click next without accepting? In this very moment, they tell you to accept it, without asking if you accept it. So its not anymore binding, as you just did what you were told to.
xp matured. And that XP was a disaster doesn't make 7 any better. Both are quite okay compared to 8/10, but it's still true, that it constantly went downhill. And not light at the end of the tunnel.
> after the security people have stripped out all the M.S. Snoops.
It's not like MS is not putting new surveilance err bugfixes in, to continue providing the best experience to its users.