HN user

shedside

311 karma

Technical Director, AttendZen

Posts8
Comments27
View on HN
Nostr 10 months ago

"apolitical" and the hero image is literally someone taking a swipe at "government inefficiency"

I work at AttendZen -- our product is built using Svelte, but our marketing website (currently) isn't. I'll investigate to see what may have caused a slowdown here, but it's definitely not down to Svelte.

I'm in exactly the same boat. It's such a shame that AFAIK nothing can import .fw.png files and keep them editable; I'll need to manually export everything to .psd before I eventually have to upgrade my OS.

What kills me is that literally nothing (inc Photoshop) will import a .fw.png file and keep it editable. I know it's using some kind of proprietary extension to the PNG format, and that some gradients and textures would inevitably be Fireworks specific, but it'd still be useful to be able to open an old mockup and tinker with it.

It'd still be enabled prior to the original charge being made. The details in the link suggest that some charges would be exempted anyway (eg ones that don't use the new Checkout, ones over a certain threshold). So it's a question of whether or not a given individual charge is insured, not a question of whether your Stripe account as a whole is insured.

Don't know if anyone from Stripe is listening here but: it'd be amazing to be able to deploy chargeback protection selectively, as a Radar rule. So that for example we could say: charges from the US are protected (and subject to the extra fee) while charges from the UK are not.

Game economies have fascinated me since I sold a party hat on Runescape for the real-world equivalent of several hundred dollars. Scarcity is the main driving force of value everywhere, and the guaranteed transparency of smart contracts should have unique This is a really interesting read; I'm impressed a crypto game has put this much effort into their system.

I'm curious about something. Why this:

  if shipping-method <> 'FX'
      move normal-ship-date-yyyymmdd to expected-shipping-date
  else
      move nextday-ship-date-yyyymmdd to expected-shipping-date.
And not the following?
  if shipping-method = 'FX'
      move nextday-ship-date-yyyymmdd to expected-shipping-date
  else
      move normal-ship-date-yyyymmdd to expected-shipping-date.
The latter seems clearer to me, and the line below (regarding the cust-type variable) suggests the syntax would be okay. It would also have the advantage of avoiding the column-length issue described in the post. What am I missing here?

Also, according to Stripe's Terms and Conditions, “the Stripe Service is not made available to persons … for personal, family or household purposes” — this isn’t the case for GoCardless, where signing up as an individual to collect gift payments by Direct Debit is A-OK.

I think the problem is that without signing-up, there's no indication that it's a paid service, let alone what the price actually is.

A "Pricing" page in your navigation would be ideal, IMO. Even an entry in the FAQ ("How much does this cost?") would suffice, especially if it's the top item.

A different approach I've tried before is to perform a lookup on the visitor's IP address, and then to auto-select the country that we think they might be from. If we get it wrong, they can always select another country the usual way.