vanadium

This is pretty much my jam at home and away. Works great.

You're right, it was in fact the Veer! Thanks for the correction. (Derp.)

Actually, a webOS phone with a software-keyboard was in fact coming down the pipeline. https://www.webosnation.com/windsornot-webos-slate-smartphon...

One could also (as was tradition) infinitely hack around most of the Palm Pre line to enable it in the end. Just before HP gave up the webOS ghost, it was a popular homebrew thing to do for a certain contingent.

As for the original hardware, it could have really used time when there really wasn't any time to spare in the competitive landscape.

I also had a (Developer) Pre 2 which was incrementally better, and while that was a nice piece of kit, the Palm Pixi was a horrible misstep (with its minuscule size and--gasp--magnetic headphone jack) I first witnessed at their unveiling in San Francisco. The Pre 3 was the only webOS phone that had a genuine shot left, but the HP Touchpad debacle pretty much sealed it. There was even a smaller HP Touchpad in the works at the time (fully working prototypes are found now and then) to diversify the line.

I was among the first batch or two of webOS app developers in 2009 (into webOS' smartphone death in '12) and wow, this makes me nostalgic all over again. I'm going to need to have a look at this when I have some time.

Good to see LG keeping it even tangentially relevant.

~85% of my searches on DDG are great (and improving), and the !bang syntax handles the rest; usually "the rest" are esoteric items. I see no reason to use anyone else as a primary search engine anymore.

I've had the opposite experience with DDG. While DDG itself resolves about 85% of my searches just fine, getting the hang of the !bang syntax has really elevated my search game without compromising a whole lot. I've been 6-months free of Google as my primary search engine, and see no reason to go back.

Insofar as other steps, I shut down my Twitter account (with a dictionary word username) last year as an experiment to see if I'd care enough to resurrect it before the account was deleted--a 30-day span. I didn't come back to check again for ~40-45 days, and I don't especially miss it. That was enough for me to realize how little value it provided me.

(Never really bothered with Instagram, Snapchat, Pinterest, and the like.)

This year I'm looking into non-Google alternatives for my family's email and common functions (calendaring, etc). It's a slow slog in between a ton of other priorities, but the importance of decentralizing again is growing non-trivially.

Also, I plan to resurrect my blog/personal site for the first time in, spitballing here, about 8 years now. Putting my content back on my terms and reversing the tide in my own way.

Jury nullification is still definitely a thing. The trick is actually getting on the jury.

I agree with 99% of what you said, but in the case of weed, while I don't think it should be hidden per se, it has a known "secondhand" effect on those in close proximity.

So perhaps it stands to reason it's just the usage that should be kept at a distance rather than the admission of use. Too bad so many are still terrified to admit their use where it's still illegal. May that change more rapidly in the future.

Rick Steves has been an outspoken proponent of legalization for a long, long time now, and it's a testament to his resolve that he's still doing it today with every bit as much fervor as he had when the headwinds were strong.

Keep it up, Rick!

Is your wife ok? ;)

But no, on a more serious note, the process should look more like:

1. Institution asks for Credit pull

2. Person gets alerted for approval of said request

3. After pull, credit remains locked

I'm glad I wasn't the only one wondering, "Ok, where's the technique here beyond just adding AMP markup in a conventional page?"

Still not entirely convinced what's supposed to work about this method.

Everything in moderation. When I worked from home for 5 years (in a company with the same distributed ethos as Basecamp 10 years back) it was easy to become extremely socially isolated if I wanted to. And it happened a couple of times over that span, but recognizing the balance of good mental health spun that back into a balanced state. (To be sure, my wife was immensely helpful about recognizing it and forcing me out the door more.)

I've been working in offices again for the past, I don't know, 7-8 years now which initially gave me some whiplash as an introvert finding himself working in a position where extroversion tends to rule the day. Nowadays, however, I have a little electronics workshop in my basement where I can scurry off to and think with clarity all to myself after the day is done. It's rejuvenating and gives me a stronger sense of worth and balance in my overall mental health.

The Ledger Nano S also uses WebUSB to sign into the Stellar (Crypto) dashboard and can be used as a U2F authentication device.

I'm curious (assuming even) that it could be subject to this exploit?

Why take out ads when you can just infiltrate /r/the_donald and influence them directly and personally? Like you said, way better ROI.

It's as simple as citing a document that lays out how they arrived at this statistic. With all due respect, perhaps it's pleading for an ideal here, but it still remains a questionable statistic in my opinion.

I don't understand why questioning a statistic, or especially my use of the word "citation", is controversial.

I just noticed this myself in the past week.

Respectfully no, but it would be relevant to understand the methodology of how they were able to discern a 1-in-4 statistic which seems, on its face at least, questionable at best. Maybe they're right and the methodology might be sound, but it doesn't change my perspective without that backing information to contextualize it.

A "primary source" also isn't in any way immune to rational inquiry. I don't mean for this parallel in any way to imply a relationship, but just look at our administration or any one of innumerable other examples to this end. Taking something at face value, to me at least, requires more than a decontextualized statement of fact when my immediate impulse is to question it (in this particular case).

For instance, define "job". Are we talking about a recommendation leading to a project for a contractor, or are we talking a full-time position? I mean, that's just the start. In what ways are they determining what constitutes "finding a job"? Talking to friends and friends of friends? Or directly messaging a corporation's page on Facebook?

There's a lot of squish here and I wish they were more forthcoming about what that statistic actually means.

"One in four people in the US have searched for or found a job using Facebook"

[citation needed]

Man, how I LOVED my ReplayTV back in the day.

Using 1.6/0.8 3G speeds (with 300ms RTT) as the baseline, and specifically targeting a 3s SpeedIndex embarrasses most non-AMP experiences by virtue of the AMP cache underlying the SERPs. These are the terms with which Google's marketing AMP specifically with its own tools for marketers. (To wit: https://testmysite.thinkwithgoogle.com/intl/en-us)

You can get damned close--and even exceed it if you're a minimalist--by throwing every bleeding-edge performance optimization under the sun at it, but nothing is going to stop marketers throwing Adobe's render-blocking VisitorAPI in the <head> to offset many of those optimizations, either. (Seriously, and you can't async it, either. Marketers get angry and Adobe doesn't support it.)

The advantage of AMP dissipates rapidly as one tests in 4G and low-end cable speeds, however. At that point, hitting a 1s-2s SpeedIndex isn't terribly difficult if you're using front-end performance best practices, even with a framework bootstrapping itself to the DOM.

In my experience, the variety of specific versions of libraries sites are locked to dilutes that performance benefit. Just look at a cross-sampling of sites calling jQuery or <insert your favorite library or framework here>.

In theory, the maximum benefit of a CDN only comes if everyone is on 1) the same version or, similar but different, 2) an evergreen version. And the latter is a big red neon sign screaming "DANGER".

Thanks for the tip; we've been doing it in a similar fashion, and this solves the biggest variable: "How do we enforce that 4 hour maximum?"

Then hopefully I can turn it off in my GSuite administration account...

...doubt it.

This is how I do it, as a Director dn hiring manager. 4 hours max, and the exercise is entirely freeform against a set of 10 typical requirements; as a Front End Engineer candidate for my team, I want to see your opinion and execution matched to the problem at hand.

It can be done in 2 hours in the most simplistic, undeliberated way using legacy practices, but 8 if you're a perfectionist. Come in somewhere in the middle, but stop at 4 hours no matter where you're at.

I don't even require that the exercise is completed, but I want you to speak to your thought process and where you went/were going when you hit the 4 hour mark. The ability to understand our space, make good decisions, and show progress toward executing on them is ultimately what matters in the end.

And then layer in techniques for performance and accessibility best practices. Those are complexity modifiers beyond just slinging code out of an AI.

Reportedly, that's just a persona and he amped it up for the King of Kong film. But I definitely get where you're coming from.

Litecoin's supported on Coinbase, if that's the route someone wants to take.

Same. Friend of mine tipped me off to having rediscovered his account, I gave it a try, and everything worked out after the conversion to the new platform (which is when STR became XLM).

This was maybe 4-5 weeks ago.

Any WebPageTest comparison between Desktop and Mobile will demonstrate that RTT can be _vastly_ different between Desktop and Mobile.

Just look at Time to First Byte (TTFB); when you pile on SSL negotiation (since most have moved to HTTPS), the advantage is even greater since all AMP pages currently fall under the aegis of Google's domain and all non-AMP pages will require that overhead at first click.

Same. It's bad enough that my son (then 2, now 6) almost ran into a very busy street while I was in the car waiting as my wife was getting him ready to go home from daycare.

That feeling of utter panic and helplessness watching him run while my wife and I screamed for him to stop will never, ever go away. It still pains me when the memory comes up, of what could have been.

He stopped 3 feet from an oncoming 18-wheeler and turned around in more fear than I've ever seen in a little kid since.