That knowledge is not illegal, nor would it necessarily be illegal to write it down.

> nor would it necessarily be illegal to write it down.

Just don’t write it down encrypted.

> That knowledge is not illegal, nor would it necessarily be illegal to write it down.

In Germany, it is often illegal to disseminate such material (e.g. for building bombs) by § 130a StGB:

> https://www.gesetze-im-internet.de/stgb/__130a.html

DeepL translation:

"§ 130a Instructions for criminal offenses

(1) Anyone who disseminates or makes publicly available content (§ 11 (3)) that is suitable for serving as instruction for an unlawful act referred to in § 126 (1) and is intended to promote or arouse the willingness of others to commit such an act shall be punished with imprisonment of up to three years or a fine.

(2) The same penalty shall apply to anyone who

1. disseminates or makes available to the public content (§ 11 (3)) that is suitable for serving as instructions for an unlawful act referred to in § 126 (1), or

2. gives instructions in public or at a meeting for an unlawful act referred to in Section 126 (1)

in order to encourage or incite others to commit such an act.

(3) § 86 (4) shall apply mutatis mutandis."

---

For reference: § 126 StGB is:

> https://www.gesetze-im-internet.de/stgb/__126.html

DeepL translation:

"§ 126 Disturbance of public order by threatening to commit criminal offenses

(1) Anyone who, in a manner likely to disturb the public peace,

1. commits one of the cases of breach of the peace specified in § 125a sentence 2 nos. 1 to 4,

2. commits a criminal offense against sexual self-determination in the cases specified in § 177 paragraphs 4 to 8 or § 178,

3. murder (§ 211), manslaughter (§ 212) or genocide (§ 6 of the International Criminal Code) or a crime against humanity (§ 7 of the International Criminal Code) or a war crime (§§ 8, 9, 10, 11 or 12 of the International Criminal Code),

4. grievous bodily harm (§ 224) or serious bodily harm (§ 226),

5. a criminal offense against personal freedom in the cases of Section 232 (3) sentence 2, Section 232a (3), (4) or (5), Section 232b (3) or (4), Section 233a (3) or (4), in each case insofar as these are crimes, Sections 234 to 234b, § 239a or § 239b,

6. robbery or extortion (§§ 249 to 251 or § 255),

7. a crime dangerous to the public in the cases of Sections 306 to 306c or 307 (1) to (3), Section 308 (1) to (3), Section 309 (1) to (4), Sections 313, 314 or 315 (3), § 315b (3), § 316a (1) or (3), § 316c (1) or (3) or § 318 (3) or (4), or

8. a dangerous offense in the cases of § 309 (6), § 311 (1), § 316b (1), § 317 (1) or § 318 (1)

shall be punished with imprisonment of up to three years or a fine.

(2) Anyone who, in a manner likely to disturb public peace, knowingly falsely claims that one of the unlawful acts referred to in paragraph 1 is about to be committed shall also be punished.

I can't belive that people have been fooled by the environmental credentials of "paper" straws.

Yes, a situation that Google is steadily fixing.

That's about the worst use case for existing eink panels, as they have a limited number of switching cycles before the dots start to degrade.

For dynamic content, a higher refresh rate absolutely will lower an eink panel's lifespan. As the refresh rate increases, more of the underlying content's changes will be captured and more pixels will change state.

Unless you are switching every pixel with every refresh, the panel will last longer than that. However, it's still a huge limitation on its lifetime.

That could still get annoying though, since maybe the middle third of the display is going to get rapidly flipped on + off as you scroll through text/browse around websites. If that part of the display dies, but the outside 2 thirds still works, I think the panel is basically useless anyway.

think in terms of "page-up" and "page-down" instead of scroll-wheel / thumb scrolling and it starts to feel alright.

Waveshare specify 1 million switches per eink dot for their panels.

https://files.waveshare.com/upload/4/4e/2.13inch_e-Paper_V4_...

https://files.waveshare.com/upload/6/60/7.5inch_e-Paper_V2_S...

1 million switches for a pixel is about 5.5 hours at 50 Hz, assuming the worst case of a state change on every frame. Surely it can't be that bad for larger panels? The existing e-ink monitors from Dasung and Onyx would have had problems by now.

I imagine most people are using those monitors for text-based applications, which have a much lower rate of pixel change. Still - the pixel switch lifetime is currently a limitiation of eink.

That's a separate effect - eink degrades under UV. Fossil eink watches did not have enough UV filtering.

It's more like capex vs opex. Some languages and frameworks - you have to maintain the same level of effort, just to keep your apps working.