conduit runs on pi zero -- though you can't directly migrate so that is of limited use to you. It would probably fail to join matrixhq or python room but, this is due to obvious resource constraints. Any reasonable horsepower and you won't have an issue.
HN user
aranjedeath
Next please make it more readable. Section 3 of the homepage has 3 different flavors of dark purple. I can barely read it.
I've been really happy with Scroll (.com). $5/mo to remove ads on some news sites. The money goes directly to the publisher, minus the company's bit. It's really good now, and I wouldn't complain if the price went up as the site list expanded.
Yeah, it runs better.
I've used FreeBSD on my production systems instead of Linux since I started this whole bit 15 years ago. Linux surprises me. FreeBSD, for example, does not. I do not walk away from production FreeBSD systems and have them fall over for reasons other than hardware failure. Full stop.
Also, for clarity, the browsing and gaming done on phones isn't casual.
Yeah, definite problem. I ran 1280x1024 until last month when that monitor (lcd, from 1999) finally died. The web was a horrible place and made me angry at humanity. I've got 1920x1080 now, and I now have enough screen pixels to see what they were fucking up my 1280 for. Not worth it.
Is this what will replace (as a meta-solution, it appears) the backed-out third party cookie blocking stuff?
1920x1920, hands down. (higher numbers also accepted, as long as 1:1)
They have a mistaken belief that it's a PDF host. It's not, in the words of its founder.
I mean except that it's not actually meant to be a pdf host. Hasn't been in years.
This. So many solutions in search of problems.
The cache-sharing other users are citing is useful, but ultimately not the most-useful part. The most useful feature is the fact that, given tons of sites are now serving global audiences, you as the site owner/administrator no longer have to deal with provisioning servers to datacenters or infrastructure of any sort (for these static resources) nearer to your customers. If you optimize by putting all of these external links into <head> and shipping that bit of your page out earlier than it takes to generate the rest of the page, you'll see pretty solid performance gains for anyone not where YOU are (near your likely us/eu based servers). At some point in optimization the speed of light becomes the hard barrier, and not caching concerns.
Moto G!
I think the point is NOT to do that. Keep the power structure flat, until such a time as somebody YC wants to intervene (by the aforementioned email).
That 1700mhz is a tmo-licensed band for the US that offers UTMS AWS, which provides 3g at rather snappy speeds. If you're not intending to go abroad, the US edition makes sense. If else, the global model has pretty nearly every widely-deployed 3g band.
If you've bought into the lexicon of marketing it is. They're stealing revenue from you.
If you haven't, you're an asshole and you're fucking your users for no reason at all (ads are no reason).
Then you're advocating risk management, and not security.
Yeah. I won't touch these because of that license.
It's essentially CC-SA, but with this: "You are not allowed to take our work “as-is” and sell it, redistribute or re-publish it, or sell simple “pluginized” versions of it."
NOPE. mit/bsd/isc/lgpl/apl or compatible or bust.
The major issue I've had with wp is the speed. I don't know if it's a php problem or a wp problem, but running wp on shit-tier commodity hardware results in a complete inability for your site to be {hn'd/slashdotted/dugg/whatever} due to the ~500ms page generation times (that only increase with any plugins at all). The caching plugins mostly resolve this, but still not well enough to be accessible during a wave of pageviews.
It seems like unless you're willing to pay for managed wp hosting (or fancy hardware), you can't expect more than 10 pageviews/s to be handled. This makes me sad.
If the function you're looking for is integrity or privacy, the statement stands.
The big issue here on mobile isn't caching, but that unless you've absolutely nailed the caching headers (and omitted! etags), the phone will still burn an entire RTT on checking the file. If the only people you serve are in SF or NYC, that's probably fine. If you want to target anyone anywhere else on earth, get rid of that wasted RTT.
So really what they're doing is stealing opera's idea. This could be advertising, or it could be awesome. I suppose we'll just have to wait and see what the details are and who they partner with.
Thank you for granting the world the spoils of your hard work.
Can you provide a definition of either that excludes the other?
Thanks, I'll get rid of that.
There appears to be a bug!
Thanks!
I'll take that into consideration, thanks for the feedback :)
Perhaps it's a failing of your browser? I've set nothing to prevent you from zooming.
Also, what makes it unreadable? I'm aware that I still have some work to do on the stylesheet. I don't have a mobile device, a small-ish screen, or a retina display so my testing of devices is limited. Constructive feedback welcome :)