Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Regardless, it's a good read.
This allows you to receive tweets in real-time over a persistent HTTP connection.
It's rather well hidden though, perhaps they don't want people finding out about it for whatever reason (performance?).
Indeed, it is:
1113982824 -> 0x42660768
0x42 0x66 0x07 0x68
188.8.131.52.in-addr.arpa. 86400 IN PTR lax04s01-in-f104.1e100.net.
I did not know you could do this until just now, so thanks GP!
(Also slashdot's layout mangling is awful, so please excuse the underscores)
Replying to myself, I know. I also just read TFA (!) and disabling the Java Platform plugin alone isn't enough!
All versions since Java SE 6 update 10 for Microsoft Windows are believed to be
affected by this vulnerability. Disabling the java plugin is not sufficient to
prevent exploitation, as the toolkit is installed independently.
There's a seperate plugin called something like Java Deployment Toolkit which you also need to kill.
To check if you're vulnerable, PoC is here: http://lock.cmpxchg8b.com/bb5eafbc6c6e67e11c4afc88b4e1dd22/testcase.html
In recent times firefox seems to have removed the little "[ ] Enable Java" checkbox from the Options > Content page, however I've found if you go into Tools > Add-ons > Plugins you can disable the Java(TM) Platform SE 6 Uxx plugin from there, which seems like it does the trick.
Thanks for the reply, it appears to be working!
Just as a note for others: I had to grab an updated shorewall package from debian testing because the version shipped with lenny doesn't support ipv6 properly and was blocking my packets. If ping6 tells you Operation not Permitted then that is the solution.
What are the variables SLA_INTF and INTF_ID supposed to be in your script above?
Without them it calculates my ipv6 address as: 2002:5e4b:cf23:0000::0000 (from 184.108.40.206) which doesn't look right to me.
extremely obese people were 36 percent more likely to die
It's a basement flat, actually! So there.
And I'm a student, what's your excuse?
"ArK does not embed into Dolphin or Konqueror in 4.1"
it doesn't embed into Dolphin, no, because that's not Dolphin's design goal. i don't have 4.1 nearby to test this on, but in 4.2 you can navigate directly into tarballs seamlessly in Konqueror.
i'm curious, what exactly is dolphin's design goal(s) then?
i assumed it was meant to replace the file-browsing capabilities of konqueror; indeed konqueror is now labeled specifically as "Web Browser" and Dolphin as "File Manager" in my K menu.
(Using kubuntu intrepid here, kde 4.1.3)
oh, and i can confirm that konqueror in 4.1(.3) does have the desired behaviour of seamlessly browsing archives and opening files etc. although it doesn't try to open pdfs inside itself like it did with kpdf in 3.x (a good thing), i realise there is probably some configuration for this hidden somewhere.
"3.5 derived a lot of its power from a very solid, well refined OLE framework, and 4.1 has yet to even approach that"
the "OLE framework" in KDE is called KParts, and the infrastructure hasn't changed one bit between KDE3 and KDE4.
i've noticed problems with ole in kde 4.1 also, dragging and dropping no longer seems to work in many cases - but i think this is more a problem with the new applications not yet fully implementing support for it, rather than a problem with the underlying framework.
i am eagerly awaiting the next amarok 2.x release, because as other posters have pointed out, 2.0 is a bit of a step backwards in terms of functionality.
don't take this post as a complaint, i think it's great what the kde team are doing. i wouldn't want it any other way
oh, and if you're tempted to say "they should have just held 2.0 until January, then", don't bother: making releases from the code repository is an absolutely requirement to keep open source projects moving, and one of the downsides of that is that often a first release of a new series isn't what a consumer-grade user is going to what to cut their teeth on. that's why there is another step in row, e.g. distributions. not that they seem to always be doing their users the best favours lately in that regard.