RubyPinch

the latest recap from the reddit live thread

https://www.reddit.com/live/x99pqdwudg0l/updates/b7a15982-4a...

What do we know so far?

A white truck have Thursday evening, driven through a police cordon and into a big group of people, who were celebrating, France national day, (Independence Day) in Nice.

The truck driver is dead and shot by the french police. According to french media and local charges, there is at least 70+ dead and 100+ injured.

Authorities have cordoned off the crime scene, rescue workers have arrived and helicopters in the air. The local prefecture has urged people in the area to remain indoors.

Several media sources reports guns and grenades have been found inside the truck, that drove over the crowd. Police are still determining if he worked alone. Eiffel Tower covered in smoke has nothing to do with the attack, it was just fireworks. French officials call it "Accidental".

French President Francois Hollande was returning back to Paris for crisis talks in the capital, his office said. Mr Hollande was in the southern city of Avignon on a private visit.

Some reports spoke of shots being exchanged between police and the occupants of the lorry but these have not been confirmed.

Remember to follow the authorities instructions, and notify relatives if you are okay. If it is not important, please use WiFi instead of Mobile Data if you are in Nice.

"not caring to act" would also be a very wrong thing and as one would expect from any other job, they should be fired for not working.

You are taking my comment a bit too literally (especially since the only thing I was trying to convey was: url files != filesystem files). I don't mean defined behavior, I mean what is expected, since that is what you were talking about.

If we go with defined behavior, then wget using the server-provided name just like a web browser does (resolving the redirects, and then explicitly noting that the file is being saved with that new file name), is completely expected, no?

You talk of native ads, + bloggers being ruined by ad blockers (with all their near zero operating costs?). Isn't native/sponsorship ads practically the perfect fit for blogs? along with being unblockable?

Can you give a couple of examples of how you feel it is arbitrary?

And you are not really giving any "benefit of the doubt" by calling them scammers straight out, are ya?

eh, the path the url contains isn't a file system path, its a string of characters that a server can treat in a million different ways, so its not exactly practical to rely on that

e.g. if the url was along the lines of

    http://example.com/dl/f3ct4t3c4c3/

what do you expect the file name to be?

If I'm not mistaken, the view is,

a) don't want to provide nice tools to windows users because then they'll no longer have the need to switch to a libre system

b) do want to provide nice tools to windows users because then they'll get a taste of how liberating freedom is

obviously there is a balance there, and I think GNU/NT might be a bit too far into entrenching-the-user for his tastes, though I can't speak for him obviously.

It seems there is no political note on his site for the announcement of ubuntu-on-windows.

There are some smaller groups that are working on their own engines (slowly but surely)

https://gngr.info/ comes to mind

> and only Ruby programmers who have used ActiveRecord will know how the first one does.

do you really think the first one is /that/ hard to understand?

> So, in fact, the W3C is not telling us what algorithms to use at all. [so they'll all pick bottom-of-the-barrel-algos, which] in the hands of amateurs are akin to handling plutonium.

It isn't up to the browser to stop people shooting themselves in the foot, "Why is your web app's download verifier so slow?" "Oh because some person's blog demanded that only cryptographic functions he liked should be allowed, so I had to use a javascript-based one instead" sounds like a pain in the ass, but totally possible (mega, mediafire, etc), hypothetical

And browsers at this point in time are getting far better at making an approximate "standard" for these kinds of things

> However, this approach just doesn’t work in a browser, as illustrated by the MEGApwn utility

Yes, this approach doesn't work in a system where you can't generate a number on the other side of the sandbox. Hence, we should not try to make a system that would allow putting/creating a number on the other side of the sandbox? That logic is a bit daft, isn't it?

> send [...] using FTP, SFTP, Rsync or SCP,

and upload and download are both free, operations (archiving/unarchiving?, et al) are not

Unless they changed it in the space of 16 minutes, I think you might of wanted to give a closer look for making your tl;dr

I don't know whether "get it out there" is the right idea here

It feels more like a warning to avoid WAFer, as opposed to a good advertisement.

Its encryption, you apply a transform before putting it onto the dropbox, and then you apply a transform after you pull it back, and the key it'd be encrypted against would be per user (like most encryption)

unless the "corruption" is reversible by the torrent client, which it would be

as long as the torrent client knows how to reverse the changes it made to the file (why wouldn't it?) then there won't be any problem.

Its just a really really simple form of "encryption", which most torrent clients do support

excessively large userbase compared to the amount of people who vote/comment is what I figure

+ I'd imagine quite a lot of people were expecting this blogpost, probably anyone who put more than $50 towards the DAO, and is currently awake

> Nope, just a wrapper

Nope, its still a fully fledged client, because being a capable client is not /that/ dependant on the UI rendering method, believe it or not.

> but it still has all the disadvantages that you incur when your client is just a web page in a browser.

No? Do you think electron exposes absolutely nothing? There is code being executed with access to the rest of your computer, this has the same access as any other language to the rest of your computer, I mean, hell even if you wanna do something weird, you could write some stuff in C (or use the pythonesque ctypes module), and then run that in turn, once again with access to the rest of your computer.

I could understand these complaints if this was an important critical thing, but its a chat client, its only job is to display text nicely with formatting, browsers are pretty good at that

refactoring (select a variable name, select all instances of that name, change), and also 1 time pre-processing data

The acquiring company removed that feature the moment they acquired SF

GA, popups, FB, et al. all get done in with modern ad blockers, don't they?

github also does versioned releases, no?

https://github.com/kennethreitz/requests/releases as an example

> Adblock Plus is not less "vulnerable", so to speak, than the other mentioned add-ons, despite what the article states. It's just that those "researchers" were not competent enough to understand how to "exploit" it.

This, (plus the fact that ABP was harder to exploit than others via the researchers methods), made me giggle a bit considering the pasts of the two extensions

https://google.com/search?q=adblockplus+noscript

On the other hand, that specific thing is the entire reason for the fork existing, its drive and motivation.

It could be anything. "We feel own-cloud isn't libre enough", "We don't feel this direction is profitable", "We feel owncloud was too open", "I personally disliked one of the people there any wanted to sink the ship", etc etc (note: I am being a bit tongue in cheek here)

If its a reason I agree with, then migration makes sense, if its a reason I don't agree with, then obviously migration might not be a good idea. But no one knows what the driving motivation of nextcloud is! So its a bit more worry-causing then reassuring

they are, but like, they are usually ultra tiny (smaller than a business card), or prohibitively expensive.

The best way of getting screens is to hop on ebay, and get a replacement screen, then reverse engineer the connecter they use

Nice news, but I doubt this'll be any easier for hobbyists to acquire without harvesting them from devices

it locks out new browsers because acquiring CDMs can be a pain if you want to roll-your-own

https://hacks.mozilla.org/2014/05/reconciling-mozillas-missi...

ctrl+f for "What does this mean for downstream users of the Firefox code base?"

tl;dr you either need to run a mozilla-built sandbox with no modifications, or literally call up adobe and ask about being given a CDM for your own browser, which they might just scoff at

to run one app as root, you load up instructions to root the currently installed OS, and install one of the generic SU* apps to manage it

yeah but so? from my read-through, its not literally "save the one and only firefox", its "we need an environment that allows for other browsers to enter the field" which DRM prevents

articles written like this (just like, as if a layer of snark was laid on top, and how they NEED to have a bad guy) really bother me

and also omg JIRA GOT HACKED! yeah, by who? a guy who wanted feedback on a kickstarter? no there was nothing to do with any "hacks"

And just so keen to blame JIRA etc, when it could be easily the fault of the single service desk that has this issue