Readit NewsGovernment says it’s ok, so it must be ok. That’s all people think.
What I really don't get is the product is hiding a lot of stuff for no reason. Whenever I zoom in my neighbourhood: it doesn't display all the streets, some shops are missing even at maximum zoom, search is removing some results that should match my query, etc...
I have slowly lost trust in the products (except for navigation), it's still my main source but I usually double check with google search or apple map.
If you have a rice cooker, you can use the rice from it. If not and you don't want to clean two pots, just boil the rice in a saucepan and once ready, get it out and fry the canned tuna with some chopped onion and black pepper.
Going to Indonesia, you can find out that's a variety of their national dish (nasi goreng). A sunny side up egg on top of that is an extra bonus.
Speaking of nasi goreng, the one from the Aceh region of Indonesia is my favorite.
But that text/markdown would have to be restricted not to include any html tags, which are allowed in the "common" md spec.
> would have to be restricted not to include any html tags
The point of this would be to deliver pure content, so "any tag" would definitely not be allowed. My user agent would decide what to render and how.
On the other hand web apps absolutely can play a little more with the UX if it provides value to the user. But if it's in the browser, some of this really do still apply. I'm all in on web apps, its a universally accessible platform for development outside the walled gardens of app stores.
What we need to stop doing is treating every single website as an app!
If you want your page to appear in search results on a search engine, it's not a web app it's a website.
An example: I don't really want to add a click event listener to a link to make it display in a modal (or whatever). Because this event is too low-level and now my listener needs to check modifier keys. What I really want is to somehow tell the browser "if the current window URL is about to change via this anchor element, call this function instead". The user is still free to open their links in new windows or tabs and my code will not be triggered for those cases.
A CSS example: I don't really want to set cursor images for every element and pseudo-class. I'm forced to list every element that uses the cursor I'm overriding. What I really want is to tell the browser "use this custom cursor image wherever you were going to use the default (hand/wait/resize/etc) cursor". My code would then be future-proofed for new elements/UI.
Sometimes I feel that certain browser APIs suffer from the XY problem.
All you need is a system to authenticate reputable sellers. Instead of looking at the stars on a product and clicking “buy now,” folks just need so ask: do I know this seller? Is this the ACTUAL publisher selling me this book?
I’d rather go into a real shop anyway. Unless it’s buying some hard-to-find item there’s no excuse.
You’re assuming that scams don’t make their way into regular distributors as they try to cut corners and maintain competitiveness.
You already see established brands lower the quality of their products after the first round of reviews online. If found out, they just blame manufacturing. Sorry.