Hacker Newsnew | past | comments | ask | show | jobs | submit | whym's commentslogin

If nothing else, the fact that many people write anything with ink and brush helps to sustain the calligraphy culture. Nowadays, to many (if not most) of them the new year kakizome ritual is the only occasion they practice brush calligraphy in an entire year.


This is what I find most interesting about Japanese culture. The Japanese do things for seemingly superficial reasons which can seem redundant to an outsider but the more I learn, the more I see utility in a lot of it.

They’ve seem so much come and go over the centuries they seem to just go their own way because it works for them. Almost feels like they’ve been burned enough times to know better than to just throw the baby out with the bath water.

The most efficient in the short term, certainly not always.


They do seem to understand ergonomics and user experience better than most.

My Sony Xperia has all its buttons on one side. Seems awfully unorthodox, as almost all the other brands put them on both sides.

Until of course you start using the phone with one hand or lay it on its side to watch a movie.


I'm not sure why but the Japanese seem to put a great emphasis on detail. If I ever find out why that is, I'll let you know ;)


Do not think it's a bad thing... Even if it's just once a year


Various businesses provide paid service called 見守りサービス to have someone (or a machine) check up on you. The idea is to detect health emergencies early enough and act on getting help, in case family members and neighbors can't. Not that that is the best option, but at least money can help to some extent.


Even an automated phone call service to make sure someone picks up. I’m surprised it isn’t a thing.


Wellness checks are a thing that come in various flavors.


It looks like this is what it does essentially:

                let luminance = (0.2126 * avg_r as f32 + 0.7152 * avg_g as f32 + 0.0722 * avg_b as f32) as u8;
                let character = match luminance {
                    0..=31 => '#',
                    32..=63 => '@',
                    64..=95 => '8',
                    96..=127 => '&',
                    128..=159 => 'o',
                    160..=191 => ':',
                    192..=223 => '*',
                    224..=255 => '.',
                };
https://github.com/thed24/ascii-gen/blob/main/src/converter....


What does 'luminance' mean in this context?


It's scaling the colors differently to account for perceived brightness differences instead of just averaging RGB values.


Ah, thank you!


There has been an RFC about it (for years).

"Remove .m. subdomain, serve mobile and desktop variants through the same URL" https://phabricator.wikimedia.org/T214998


There problem is when your auto-detection gets it wrong and you keep getting served the mobile version even if you are not (looking at you www.arista.com).


This is a good use of a session cookie. Or even a stored cookie.

It would be considered a non-tracking essential site function value too, so you wouldn't need to beg permission (contrary to what people who want us to be against privacy legislation will claim), and the site is probably already asking for permission anyway for other reasons so even that point is moot.


Unfortunately "non-tracking cookies" are no longer a thing in most browsers.


I was meaning non-tracking essential cookies, as defined by privacy legislation that requires permission for things that are not essential for site features.

Or are you suggesting mainstream browsers are blocking same-origin session-level cookies by default now? I'm not aware of any. And if you have a browser that is blocking such things, the worst that will happen is the current behaviour (repeated mis-guesses because the preference isn't stored) continues.


Safari drops first-party cookies (and all other storage) on sites that have not seen interaction in 7 days.


This is not entirely accurate. It's only script-writable storage. HTTP cookies are not removed.

I'm not defending Safari's policy, by the way, just describing. I think it sucks, and a conspiracy theorist might note how it favors native apps over web apps.


Thanks for the clarification!


Needing to re-override the incorrectly detected mobile/not upon return after a full week away will be massively less annoying than needing to do it every new page request, so that shouldn't be problematical.

That Safari does this is useful information that I may need to warn users of one of my projects about, as it means intentionally offline data has a much shorter expiry date than on other platforms.


Wouldn't this log you out of everything?


Everything you've not visited in the last seven days, yes.

Things you touch regularly should be fine.

And apparently it only affects mass local storage, not cookies which are most often used for season management (so you might stay logged in but the app need to reset data previously called in local storage).


how would a cookie help with better auto-detection? to store the platform, maybe, but how do you determine whether the user wants a mobile/desktop version to begin with?


It doesn't help the detection, it means that the override when the detection fails is remembered so the site knows to just pick a particular version instead of using the detection method at all.

It is a work-around improving the UX on the second and subsequent requests, not a fix for the root cause.


If you do it right you don't have auto-detection because you don't have separate versions of the page in the first place. CSS is powerful enough to adapt a page to whatever viewport it happens to be displayed on.


From WordNet:

> 1. skittish, flighty, spooky, nervous -- (unpredictably excitable (especially of horses))

(I didn't know the word skittish, and I figured this might help others, too.)


> 自作自演 (jisakujien ; self-made self-staged ; for example, used for the act of creating a staged situation and then acting as if it were genuine)

The original meaning was a screenwriter-actor performing the script they wrote, which is a perfectly fine thing to do. It can mean 'sockpuppeting', too, and that other use might be more common nowadays, though.


> (or whatever they are called these days, Google for Work?)

Gmail is currently branded as part of Google Workspace, and shows the Workspace logo upon sign in. It probably has been that way architecturarly for a long time, but I think they have made it more explicit relatively recently, at least for non-corporate users.

It looks like "Google for Work" is an old name of Google Workspace.


Like their chat apps, they change names so often that I just call them Google Docs most of the time.


I don't think any fork was deleted. 3.5k forks as of now vs 3.4k forks in January: https://web.archive.org/web/20220129022012/https://github.co...

Many people won't notice some of their stars having disappeared, but many would be surprised to see their forks deleted without their consent, especially those that are not merely a mirror. People can have diverged forks after adding substantial changes without feeding them back to the original for a variety of reasons.


A lot of the cherry trees planted in Japan are clones, which causes synchronicity - the cherry trees in an area are grafted from a single, best tree found there, and thus bloom at the same time for the same duration, more or less. (At least that's how it's commonly understood, I don't know about the exact science into that.) That, I think, makes the blossom feel more short-lived than a non-synchronized blossom.


> やさしい料学

It seems like that's also a typo or scanno of 科学. Aside from the one letter, everything else about that book matches the bibliographic information of another book whose alternative title (or subtitle) is "やさしい科学": http://webcatplus.nii.ac.jp/webcatplus/details/book/isbn/978...


Argh, in which case, the scanner made the same mistake I did wwwwww


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: