Kickstarter is not a store. As part of your backing/pledge, you got a gift. That gift is a first run of the product, and warranty is not the same as a product you buy in a store. Or so the party line goes, I'm not necessarily agreeing or disagreeing.

Yeah and it's pretty surprising to me, considering the amount of Chromebooks and other devices that are currently sold.

For me personally, I need decent Flash. My (European) country's national broadcaster has a digital Flash-based channel. I recently found out that Adobe dropped Flash hardware acceleration somewhere last year. You can't force it on through some obscure configuration file, either.

That makes for a big disadvantage for most Linux-friendly stuff, I need something Microsofty or Apple-ish.

"Good afternoon, madam. How may I help you?"

"Good afternoon. I'd like a FrintArms HandCannon, please."

"A--? Oh, now, that's an awfully big gun for such a lovely lady. I
mean, not everybody thinks ladies should carry guns at all, though I
say they have a right to. But I think... I might... Let's have a look
down here. I might have just the thing for you. Yes, here we are!
Look at that, isn't it neat? Now that is a FrintArms product as well,
but it's what's called a laser -- a light-pistol some people call
them. Very small, as you see; fits easily into a pocket or bag; won't
spoil the line of a jacket; and you won't feel you're lugging half a
tonne of iron around with you. We do a range of matching accessories,
including -- if I may say so -- a rather saucy garter holster. Wish I
got to do the fitting for that! Ha -- just my little joke. And
there's *even*... here we are -- this special presentation pack: gun,
charged battery, charging unit, beautiful glider-hide shoulder holster
with adjustable fitting and contrast stitching, and a discount on your
next battery. Full instructions, of course, and a voucher for free
lessons at your local gun club or range. Or there's the *special*
presentation pack; it has all the other one's got but with *two*
charged batteries and a night-sight, too. Here, feel that -- don't
worry, it's a dummy battery -- isn't it neat? Feel how light it is?
Smooth, see? No bits to stick out and catch on your clothes, *and*
beautifully balanced. And of course the beauty of a laser is, there's
no recoil. Because it's shooting light, you see? Beautiful gun,
beautiful gun; my wife has one. Really. That's not a line, she
really has. Now, I can do you that one -- with a battery and a free
charge -- for ninety-five; or the presentation pack on a special
offer for one-nineteen; or this, the special presentation pack, for
one-forty-nine."

"I'll take the special."

"Sound choice, madam, *sound* choice. Now, do--?"

"And a HandCannon, with the eighty-mill silencer, five GP clips, three
six-five AP/wire-fl'echettes clips, two bipropellant HE clips, and a
Special Projectile Pack if you have one -- the one with the embedding
rounds, not the signalers. I assume the night-sight on this toy is
compatible?"

"Aah... yes, And how does madam wish to pay?"

She slapped her credit card on the counter. "Eventually."

                -- Iain M. Banks, "Against a Dark Background"

what URL? what webserver? won't work over ssh. wont work OVER your connection. it has to work VIA it to be feasible.

I'm using Gnome 2 and Compiz, so I'm not sure whether this translates to your platform, but in the Gnome file manager I can enter sftp://username@hostname:/home/username/foo.jpg . I guess the problem is figuring out as which hostname the server is accessible, which will probably mean an old-style ~/.tyls configuration file ("When logged in from 192.168.1.14, then prefix the pathnames with sftp://bob@192.168.1.5/"). Since this is completely separate from Terminology itself, one could implement this right now as a lightweight Perl script that can run on a NAS.

now to display a thumbnail i could have tyls generate small low res thumbs itself and embed the thumbnail image inside escape

Well, for remote hosts I think a generic "This is an image" or "this is a video clip" icon should do, otherwise you might be sending huge amounts of data over a 1 Mbps data connection.

I just had a look at tyls.c; it looks to me like the escape codes have the filename and a generic icon identifier ("like "application-x-tar") embedded, or no icon identifier if it is a media file. I assume that the terminal client then looks up the file and generates the thumbnail.

Why is it infeasible to use URIs rather than pathnames, so that the terminal can fetch the data? I understand that it's more work than adding three lines of code, but your wording "Haven't figured out how to sensibly do it remotely." sounds like there is a more fundamental problem.

Doesn't work over a remote shell. Has to be local atm. Haven't figured out how to sensibly do it remotely.

Do you say this as a beta tester or as a developer?

I suppose that one could implement the 'tyls' replacement for ls without all the GUI libraries (probably a 20 line perl script could do the job). Maybe without thumbnails, but at least with hyperlinked filenames. If the filenames are then encoded as, e.g., sftp://host/path/foo.jpg, then it would not be too hard to implement a handler inside terminology.

have you tried mounting the remote location and streaming with sshfs?

Yes, I tried. But things like mass re-tagging media (ogg vorbis) files are very slow if the actual file content needs to be sent back and forth over wi-fi, compared to doing the file operations locally on the media server.

I wonder whether it works if you ssh into another machine. I have been wanting something like that while logged into my media server, which doesn't have X11 applications installed. It's not mentioned in the feature list and I can't judge whether the underlying architecture would allow tunneling these functions over ssh to a box that doesn't have enlightenment installed. I'd think that a special ssh client on the client side would suffice to have simultaneous channels for command-line data and multimedia data to the host machine.

What the fuck are you talking about, you dumb fuck?

Evernote Premium users pay $40 per year. I'm not borrowing anything.

To really make things right, they should stop bribing officials. Because that's what happened here, or so I have the feeling.

I wonder how the write times change when they become over-write times, and sectors have to be erased before they can be written.

I'm surprised no one else responded to this; TFA didn't mention it either; I recall having experienced a significant performance difference between a new and a used USB stick in the past.

I happened to have an unused USB stick (SanDisk, 4 GB) lying around, so here are the test results I get right now. Out of the box, it takes about 4 seconds to write 40 MiB, using the command

time sh -c 'cp /tmp/random_data_40MiB /media/FBDD-DDE3/rnd40M-3; sync'

Strangely, sustained writes (looping the above command) are about a factor 2 slower; maybe there is some cooling-down time to prevent overheating of the flash chip? After filling up the entire USB stick and deleting all the files again, there is no difference in performance compared to when it was fresh: 10 MiB/s for a burst write and 5 MiB/s for sustained writes.

That was my whole point: if the blanket is truly reflective for infrared, it doesn't matter much what temperature the blanket is. The problem is that usually only one side is reflective; the other side is not reflective at for thermal radiation.

One space blanket should be enough provided that the correct side is facing outward: the one with the high infrared reflectivity and low emissivity.

That emissivity is around 0.04, which means that the apparent infrared temperature is 0.96*Te+0.04*Ts, withTe the environmental temperature and Ts your surface temperature. Example: Te=20 C, Ts=35 C: apparent temperature 20.6 C, which will drown in the noise.

Unfortunately it's difficult to tell which side is the reflective one by eye. Of the few ones that I've tested, the other side can be close to a black body radiator. The instructions "put this side inwards to reflect body heat back" are not always correct.