davidpelayo

I spent yesterday some time rotating my passwords and I found out that the Apple Id passwords are limited to 63 characters maximum.

Googling, I found nothing about this topic.

Then I went to the Apple StackExchange (probably not the right place) to ask about it without success (https://apple.stackexchange.com/q/387364/263000).

I'd like to see the potential technical reasons why a company would go for such design - rather than needing anyone from Apple sharing such internal details (as the guy at StackExchange replied).

Thanks!

Dear reader.

Today, I've spent almost 3 hours trying to purchase a few items at IKEA online (the Spanish online store, ikea.es).

As a web developer, I find incredibly difficult to develop an end-to-end website online purchasing experience only compatible with IE11, which was the case.

Of course in order to figure that out, I needed a process of testing the same process again and again with the following list of browsers: - Chrome, Firefox and Safari latest versions for Mac OS X 10.14 and Windows 10. - Microsoft Edge on Windows 10.

None of the above worked. In some cases, an error was thrown so the payment form submission couldn't be correctly sent. In others, some data matching such as the shipping address wasn't simply accepted.

In the end, after complaining on Twitter and contacting them directly, I decided to give it a last try with IE11 and voilà!

To sum up: I would have found profoundly useful to have a website that lists if the full purchasing experience is compatible with my browser, the same that caniuse.com does with the Web APIs per browser.

Any ideas?

Lastly, I wonder whether there is a good collaborative resource providing consensus-based good parenting practises and guidelines, from a general point of view: Which, of course, would include, techniques, methodologies or guidelines depending on the age, type, culture or context where children grow up.

Am I requesting for a kind of an impossible-to-find asset?

I'd appreciate your thoughts on this.

Hi HN. I'm wondering what's the best way to capture the customer feedback (on a web or app). It's true I've seen many startups and ideas to collect feedback, prioritize them, present them in a backlog fancy way (publicly or internally to the team), in order to close the feedback circle and have better tools to make a team more productive and understand better their customer needs.

However, all I've found so far doesn't emphasize on the need of targeting what feedback relates to what. General feedback is often required. Comments, screenshots (here another problem! there is not such tool -afaik- for providing issues screenshots to a startup, instead, the end user has to do it manually and send it, in case she/he decides to report it), but it's such a mess to define concretely what the feedback is about.

So, what if you could have an app that generates embeddable and stickable-to-existing-components feedback widgets so the website owner owns directly what feedback relates to what beforehand? Then, potentially, the data is mashed and presented in ways to be analized in order to drive better decisions. Metrics I could imagine are: time the user required to give feedback, how much attention the widget got from the end user, time to response from first interaction etc., all together in one place with the ability to be easily integrated with other platforms: drive, zapier, JIRA, easy plug-in on CMS like wordpress or event static websites. You could think of these widgets as the Disqus ones, which requires almost no effort at all to aggregate such an amount of data.

We've presented this idea in welapse.com, so I would appreciate feedback from you, smart readers!

Thanks!