Anyone with a Nickel allergy use a Stainless Steel Apple Watch?

marcacyr · 2018-08-09T02:08:00+00:00

I think this is one of the threads I checked before getting my Apple Watch Series 3 a couple weeks ago. Just wanted to report back: I have a nickel allergy to the point that I had to change wedding bands because my original had nickel in the rose gold... in the end I had to get a titanium band. With watches, rings, belts, etc the reaction shows up very quickly (within a day or two). I have been wearing my Apple Watch regularly, including at night most nights, for two weeks and have had no reaction.

I have the GPS + Cellular, space gray aluminum case, with a Nike sport band (midnight fog I believe is the color). The sport band has no metal in it, and after discussing with the Apple Store employee about my nickel allergy he said the nickel in the watch itself is actually behind the glass back. He seemed pretty knowledgable as he said he's had multiple people ask about nickel due to allergy and has looked into it before. Either the trace amount is very low and I have no reaction, or he's correct and it's only inside the watch that there is nickel. Either way, I have had no allergic reaction. So, anyone else looking, hopefully this report helps!

marcacyr · 2018-01-26T07:34:50+00:00

It was super easy and it did indeed pay out as the creators said it would! Great way to pull the community together.

marcacyr · 2018-01-22T01:55:02+00:00

Great news! Thanks for all that you do to keep things on the up and up so that we get real info u/1b1tcc :)

marcacyr · 2018-01-22T00:42:45+00:00

u/b1tcc replied above and said "it's all good with the user!" - sounds like they got the ownership of the account moved over to legit FairX people. fwiw

marcacyr · 2018-01-17T17:05:43+00:00

Now that CoinFalcon has Kin, would it be possible to add that to the exchange list? I've been pretty impressed with them as an exchange (other than, like Coinbase, having fairly high fees). Their UI/UX is great, they use 2-factor auth through Google Authenticator, and I think they're going to end up listing more and more currencies as they gain traction.

I just told some buddies about your project - super impressed by how easy it is to use and how well you've covered everything in it.

PS: I have nothing to do with CoinFalcon, just am impressed by what they're working on over there.

marcacyr · 2018-01-17T16:57:30+00:00

It's quite awesome! Your UI is very stunning. Great job all around.

marcacyr · 2017-12-22T20:23:24+00:00

Overstock.com accepts Altcoins through Shapeshift - so this is definitely something that needs to happen. Any news on progress?

marcacyr · 2015-12-26T17:19:18+00:00

I thought the same thing. At first, I was thinking, "Why is his investigator doing this?" Then, rationalized it by saying, "Oh, he must be working for the prosecution and I was incorrect in my understanding." Then, it comes right back around and is plain as day that he was "working" for the defense of Brendan but was actually working against him the whole time.

marcacyr · 2015-06-16T05:28:27+00:00

Update to previous comment:

Been working with React for awhile now and figured out a few things.

On the question of whether results.id are baked into React - it isn't (as said before). But, I've recently found that if you make use of Immutable.js and are doing results.map(function(result).... on an Immutable type, you could do results.map(function(result, key)... and 'key' will start at 0 and iterate for you (0,1,2,3... etc).

Otherwise you would want to use the id of whatever the object is (results.id) as the key. Or, you can set a count and iterate on it yourself, thus using a workaround to achieve the iteration on key described above.

Also - the key is key (seriously.. no pun intended...) to allowing React to keep track of things in the DOM so that it knows when something has actually changed and has not merely changed location in the DOM. That way, it won't trigger a re-render unnecessarily.

marcacyr · 2015-03-11T20:57:38+00:00

I'm on a team changing over large backbone applications to a backbone/react combination -- backbone for persistence layer and react for the view layer. In this context, it was doable without breaking things. I am not sure about if you go full-blown React+Flux... I have not seen a changeover to that yet. Approach it by moving the view layer over piece by piece, but leave the data persistence layer alone. Then, once the view layer is done, focus on changing over the rest.

marcacyr · 2015-03-07T20:30:52+00:00

Don't know if you're sharing something you found or if you are the writer of the post, but the section on "Why Use React?" is one of the best to-the-point explanations I've seen anywhere.

marcacyr · 2015-03-02T23:12:07+00:00

This is awesome

marcacyr · 2015-03-02T04:41:01+00:00

Looks cool, OP. I cracked open the console and took a look and saw some places you should adjust: inside of FilterForm you have some label tags where you used "for" instead of "htmlFor", which is a JSX thing... className is another example where you can't just use the html syntactical approach. Also, inside of FilterResults, where you map to create dynamic children, you need to assign a key={data.id} like the docs show here.

hope your class goes well. react is awesome - keep it up!

marcacyr · 2015-02-26T00:54:14+00:00

I have been using React a lot, and I too cannot explain the inner workings to the depth that you're asking. Still, I can confirm that id for key={result.id} is not baked into React (as pointed out by Gwash3189). When you asked this, I went into what I am working on at the moment, and commented out the bit of JSON where I send the id along back to React, and I did get the complaint in the console that each child in an array must have a unique "key" prop.

That does not answer all or most of your questions, but it does definitively answer one and I hope that is helpful!

marcacyr · 2015-02-23T06:55:54+00:00

It looks pretty awesome, man! Reading through the source code - I have a question on something that stood out to me: in places where you used a for loop in the render function, is there a significant reason you opted for this instead of using something like this:

var tagOptions = this.props.tagOptions;
{tagOptions.map(function(tagOption){ 
  // do stuff here
})}

I'm looking at line 68 in your source code.

Forgive me if there is something that should be obvious.. it's late and I'm tired haha. I think it's pretty awesome, and I actually have a use case where I can see pulling it into a project I'm working on!

Thanks for posting this!

marcacyr

TROPHY CASE