1,556 karma · joined September 8, 2010
Lots of good points in this article but I don't think this is an issue. IMHO custom elements shouldn't be used to define content, we have standard elements for that, it should be used for rich interactive components. For example a datepicker. If there is content in the element then I do not see how search engines would interpret it any different than a normal div, or even better the custom elements should define content appropriately such as <my-component><article>text</>
id="hn-comments-drawer storyId-38300167 maxDepth-3"
Please use data-attributes or another more suitable alternative than id for settings.
https://developer.mozilla.org/en-US/docs/Learn/HTML/Howto/Us...
The 1% is for all non local currency payouts. Example: "The primary currency for Stripe accounts in France is EUR. All other currencies fall under alternative currencies." "1% Of the payout amount, when you choose to payout in select alternative currencies." Ref https://stripe.com/docs/payouts/alternative-currencies So basically this will result in very expensive payouts for anyone doing USD charges outside US or EUR charges outside Europe. Like many SaaS companies are. Charging any other currency is problematic for many customers so it is not really an option. Like I don't want to be charged in pesos for a SaaS that I am using.
The alternative is to have Stripe convert USD to my local currency. For a small 2% fee.
This is absurd. A 1% fee to transfer USD to a USD bank account?
The alternative is to charge in another currency - which Stripe will put a 2% currency fee on.
This is already on top of their expensive transaction costs.
Will actively look for alternatives now.
Given that Zoom requires admin rights to install and has had numerous security issues I definitively use the browser version even though they really push their native client.
Nifty extension though.