pwdisswordfish4

Why do you measure floppy capacity in megabarns?

It came from the same developer. The mere fact that he was that sloppy in securing a publicly-facing service to leave a vulnerability so severe and so easily discovered should have you asking: why should I believe that anything else in this project is any more robust and secure (and will be in the future)?

What are you people complaining about? The command does exactly what it advertised, it chucks disks.

XFCE is barely maintained, unfortunately. The recent port to Gtk3 lost some functionality as a result of regressions in the toolkit: keybindings in menus are no longer hover-rebindable, and the themes have not been properly ported, leaving me only with bloated Adwaita. For some reason, the package with window manager themes has not been released for 4.12 (the package from 4.10 works fine, though). There’s no path for migration to Wayland. Integration with display managers (i.e. screen locking) and systemd’s power management is flaky.

And I am saying all this with regret, as a long time user; I consider it the best desktop environment I have used.

I almost wish they had forked Gtk2 instead of porting to Gtk3 (or even more crazily, ported Gtk2 to Gdk3 to take advantage of ‘plumbing’ improvements in the latter, like Wayland support), but I do realise they just don’t have the manpower.

There's still a missing word or something else going on: "Flurly is a Shopify alternative attempts"

Beginners and also C++ programmers, expert and beginner alike. Even though it’s just as misleading in C++. This:

    int a = 0;
    int& x = a, y = a;

declares x to be a reference, but y an independent variable. Similarly, a template parametrised by a variadic pack of function pointers is declared thus:

    template <void (*...x)(void)>

It’s a good thing I don’t work in C++ too often, because my forehead would have probably sustained noticeable injury from all the facepalming each time I see ‘int& x’ instead of ‘int &x’ and ‘typename... T’ instead of ‘typename ...T’.

There's a typo on the Shopify page: "Flurly is a Shopify alternative attemps"

Nice job. A suggestion: support alternative payment processors besides Stripe.

I paid with cryptocurrency for the first time today when I realized my webhost accepted it in lieu of cash and that it had the lowest fees among all payment options. For example, right now my webhost's calculator says that for a $10 deposit there's a 20 cent fee for a net deposit of $9.80 if I use "Bitcoin". (I actually have no Bitcoin and managed to pay anyway, because my webhost is using BitPay as a processor, which seems not to limit you to Bitcoin only.)

A product on Flurly right now using Stripe at the same price looks like it would be $10 - (2.9% + $0.30) - 1% for a net of $9.31 after net $0.69 fees. Considering the example on Flurly's homepage is $1, for this and the $10 example I gave and for other small payments, it's obviously a better deal for sellers if buyers avoid using Stripe. And it turned out to be easier to log in to Coinbase and pay with some giveaway coins I'd received than it would have been to pull out my credit card and fill in the info.

Might have something to do with the fact that the dialogue was apparently originally written in Polish, which usually omits subject pronouns (they can be inferred from the verb form). If the translator was Polish, they might have carried that over to English.

(Noticed how I dropped ‘it’?)

BitKeeper has been available under Apache license for several years now. It's interesting that they didn't choose it. Not enough third-party use to justify adoption?

> We changed how our sessions work to get around it

In other words, you fixed the bugs in how your original implementation relied on bad assumptions that it shouldn't have tried to rely on to begin with.

The only real quibble here might be that duplicate requests cost you unnecessary transit.

The Dat people are notoriously opposed to blockchain hype. That doesn't mean you should actually go build anything on top of their projects (for reasons to do with what the top post in this thread touch on—they don't know much about stability or focus).

I considered, especially since this is a Show HN, to not say anything and let it slide, but considering the potential long tail for negative effects, where web dev circles are already filled with mildly annoying falsehoods and crazy beliefs, it seems kind of irresponsible to opt for letting it slide out of some (possibly mistaken) notion of politeness.

There are some bad conclusions that can be drawn from this chart, if not just downright bad info contained in it, at least in its current form.

For example, if the date labels are going to be this arbitrary, it would probably be better to just omit them altogether.