HN user

jermy

70 karma
Posts0
Comments59
View on HN
No posts found.

The way you describe is how it worked in zope templates (allowing a 'no items here' text if there was nothing to iterate over in a list) - it was frustrating that the later python implementation was different.

They plug in to a socket in the glove compartment, and I don't think the rental is counted as completed until they are returned there. I'd naively assumed this was standard across the globe, but clearly there must be other factors to warrant not allowing you to remove the key.

On the other hand, the fuel payment card does missing - but at least Zipcar in the UK are efficient at refunding your own payment when provided with a receipt.

Intermediate Vim 7 years ago

Just to extend this - if you're often using different users (or need to otherwise deploy via a configuration manager), I've found out that a good way of having system-wide options on Debian is /etc/vim/vimrc.local with something like:

   " Workaround stupid defaults.vim behaviour
   if filereadable("/usr/share/vim/vim80/defaults.vim")
      source /usr/share/vim/vim80/defaults.vim
   endif
   let g:skip_defaults_vim = 1
 
   " Disable stupid seeking to last position
   autocmd! vimStartup BufRead
 
   " Disable stupid mouse support
   set mouse=
Intermediate Vim 7 years ago

Likewise - with visual mode it's normally pretty quick to select an area and do a basic regex, even for things like re-indentation (auto-completes to something like :'<,'>s/^/\t/) even though I'm sure there's a 'proper' way to do that

We deploy our software packages to our own infrastructure and clients using a private APT repository and basic HTTP auth. Obviously we're running it with apt-transport-https installed for making the latter not completely insecure.

I see no reason to do that for signed packages from the main repositories, however.

Jökulsárlón lagoon in southern Iceland is a fascinating place for this - large blocks of ice break from the glacier at the top end and slowly float towards the outlet of the lagoon to the sea.

Near the outlet the iceburgs catch on the bed of the lagoon and tumble as they melt. There's a glorious variety of colours as the ice as the freshly exposed dark glacier ice is exposed - like in the attached article - before the ice surface melts and it returns to a white colour.

I'm not who you responded to, but the DeckLink Mini Recorder (towards the bottom of https://www.blackmagicdesign.com/products/decklink/models) is a very capable PCI-e HDMI and SDI capture card for around £100/$140.

Apart from possibly needing an update to the kernel package, all of the DeckLink devices are supported by the same SDK, with only some small variations (like giving the user the choice of selecting which input connector to use or similar).

Is this possible? Fault currents are much more obvious at a higher voltage than lower, and I thought most RCDs would not be made to be sensitive enough to catch what might be a dangerous DC leakage.

A friend wrote a blog post at http://www.huffingtonpost.co.uk/hannah-griffiths/isis-climat... whilst in Iraq, which refers to the Columbia University paper at http://www.pnas.org/content/112/11/3241.full

It's very much a picture of the drought causing people to move to overstretched towns and cities to look for work, and rising discontent with their government as a result. In some areas, mercenary work might be the only paid work available.

You should probably first consider seeing if there are critical bits of code that can be rewritten to use MMX/SSE instructions, since your data is in the right cache already, without needing to move it anywhere else.

The MS-DOS Showcase 12 years ago

Windows NT 3.1 (1993) and its successors (NT 4.0, Windows 2000, XP and the server equivalents) was independent of DOS, but was separate to the other OSes (Windows 3.1, 3.11, 95, 98, ME) that ran with a hybrid 16-bit/32-bit monolithic kernel on top of some sort of MS-DOS.

Forbidden Technologies - London, UK (Wimbledon)

We are looking for two software engineers for R&D work on the FORscene cloud-based video editing platform. Jobs are based in Wimbledon (South-west London, so no need to travel in to the city). Main technologies in use are C++, Java and Python, and we run our own cloud linux infrastructure.

All details are at http://www.forbidden.co.uk/company/jobs/

Forbidden Technologies - Wimbledon, London, UK

We're still looking for an R&D manager to take over the technical lead and management of a growing team working on developing FORscene, the market leading professional cloud-based video editing system.

Technology is a combination of C/C++ for video compression and processing, Java for editing interfaces (Web applet and Android), and python for everything else.

Wimbledon has good transport links, and ideal for anybody based in the South-West of London and not wanting to commute into the city. Competitive salary and share options (we're a listed company - FBT on AIM).

See http://www.forbidden.co.uk/company/jobs/ for more details.

Forbidden Technologies - Wimbledon, London, UK

We're looking for an R&D manager to take over the technical lead and management of a growing team working on developing FORscene, the market leading professional cloud-based video editing system.

Technology is a combination of C/C++ for video compression and processing, Java for editing interfaces (Web applet and Android), and python for everything else.

Wimbledon has good transport links, and ideal for anybody based in the South-West of London and not wanting to commute into the city. Competitive salary and share options (we're a listed company - FBT on AIM).

See http://www.forbidden.co.uk/company/jobs/ for more details.

It's very unlikely to be useful, unless you are running the same platform and have an interest in implementing business rules for the same use cases as the BBC have. Much of the interesting functionality will have been licenced from outside providers, and most of the cost will have been paying Siemens, paying Siemens to cancel the contract, and other staff and consultant fees.

The irony is that we (the company I work for) already do low-resolution web-based proxy editing. The BBC has know about us since 2006 - we were even part of the original DMI tender process, but have been sidelined through all of that, with preferred vendors and consultants taking over (actually, we were also part of two of the six large-consultancy bids on the second round, but that tender was again dropped when Siemens were idiotically awarded the contract instead).

You're absolutely right about proxy content not being right for all markets - especially Drama - but it's not just a question of getting a good enough quality encode. If you don't have a calibrated display on your BBC desktop, then it's pretty meaningless. We are used as a production tool for logging and rough-cut editing on high shooting ratio (typically reality) programmes before an offline edit, and will save a lot of hours in editing suite time.

The DMI has been in the way of us being able to sell to the BBC for many years now, even though it has been a ghost ship for most of the last year. We were unsurprisingly delighted (as a company, of course, not as licence payers) that it has been officially dropped today.

Since I've had nothing better to do that look at the pictures for a bit, I'm confident that it was Sunday, 28th October 2012, with one set of photos starting around 1pm facing north and another one used for filling in gaps a bit later - starting somewhere between 3pm and 4pm (harder to be precise - there are fewer clocks visible from this one).

Video at http://blogs.rsa.com/idp-beat/announcing-rsa-distributed-cre...

Any suggestions of what might be worth $150,000 in all of this?

At a basic end, this seems to be similar to storing every other character of a suitable hash on two nodes (preferably running heterogeneous architectures). RSA's ability to 're-randomise' suggests the ability for the two machines to be able produce a plaintext version of the password, which obviously seems particularly dangerous, especially if somebody is sloppy and backs up both nodes to the same location.

Is there any distributed encryption algorithm that could be done that would allow straightforward credential verification as well as the ability to re-salt a hash securely without knowing the plaintext?