I don't see any keyboard or stylus in that Jolla.

For me that is not even in the same league than the N900.

There is the Gemini PDA from 2018 which has a physical keyboard. I heard it was mostly a disappointment.

There was another phone with keyboard around the same time, but I forgot the name. That was claimed to be very much in the spirit of the N950 and its cancelled follow-up, the Nokia Lauta.

All with Sailfish, the spiritual successor of Meamo/Meego from Nokia.

Mostly a disappointment? The keyboard is fantastic. I can tell because I have a Cosmo Communicator (successor with 4G) and Astro Slide (successor with slide mechanic and 5G). The keyboard of these is great, but... they got barely no support, and the company who build these is like AWOL. Either way, like the GPD Pocket series, the keyboard is larger compared to the Nokia N900 (3G) and Nokia N810 (WLAN only)

> There was another phone with keyboard around the same time, but I forgot the name. That was claimed to be very much in the spirit of the N950 and its cancelled follow-up, the Nokia Lauta.

Probably F(x)tec and their successors. Those have a similar small keyboard as Nokia N900 and Nokia N810

There's also the Hackberry. This device uses a real Blackberry keyboard, with custom firmware. It works together with a 3D printed case, and a RPi CM5. This keyboard, while small, is very ergonomic.

What is preventing the emergence of an open source project providing the HDMI 2.1 bytecode ready to be downloaded into a FPGA, giving any Linux user the possibility to very easily DIY an adapter? Or even sell and ship the hardware without any loaded bytecode, and then users load it beforehand?

No, because each participant can check its contribution in the log.

Everybody gets a copy of a verifiable hash etc when voting, allowing voters to mathematically check their vote.

The kind of knowledge allowing to design such clever algorithms is the real meaning of the word "crypto" (cryptography).

I see what you're saying now, I was imagining the type of transparency log that's usually run by a single institution and audited by a few others.

Even if every voter gets a hash and can check that their vote is in the log, you still have a bunch of places where a central actor can misbehave: Deciding who gets to write to the log in the first place, rate-limiting or dropping submissions, or running split-view logs in the event that there's not a ton of replication - hoping that wouldn't be the case in an election.

With a (properly designed) blockchain, you at least push those assumptions into a consensus layer with many writers/validators and game-theory penalties for rewriting its history. It's still not magic; but for something like elections, I'd rather minimize the points where a single operator can tilt the playing field, which is why I was thinking "blockchain" instead of "centralized transparency log"

No, just publish the hash of the full log. No blockchain required at all. Anybody can check they are seeing the same log as others by checking the log hash.

These kind of things are part of transparency log threat models, for example: https://www.rfc-editor.org/rfc/rfc6962.html#page-24.

I think you meant Laplace (Laplacian operator).

That's the mnemonic I was taught, but granted, it takes some artistic license to make it rhyme.

Ha! lol ^^ Ok, I see!

To scientific-oriented minds it only refers to the mathematical operator.

I personally did not know about, and don't care about, the "horrifying" thing you see in nabla. And I will keep being like that.

If we were to start tracking all the things that are "a typo away from a bad thing", not a lot of words would be left.

I'm sure you have a list of things that you would not want to be "one typo away" from.

"Rare Books A**ociation" already has 1 bad word right in it. No typo needed.

I don't. One typo away means it stays different.

In the replying posts, there is mention of a discovered bug that could have resulted in most of the reported problems.

It is normal to want to discuss in order to check if that was the bug, in which case fixing the bug would have solved the issues.

Given that the bug is a well-known and inherent flaw of the technology used, I don't understand what good this would do. It's not enough to say "whoops, we didn't think the machine would do the thing the machine is known to do".

To fix the bug the architecture of the feature would have to be different, and that was completely obvious from the start.

That is not the problematic part of the grant conditions.

The following antidiscrimination laws part was the part quoted in the article linked here. The part they said was recently added. What part are you referring to?

Nope, you cherry-picked around the part where they say no to DEI.

You misread it. It says no to DEI, that violates nondiscrimination laws.

It includes "DEI, that violates nondiscrimination laws" presented as an accepted fact. So that includes a statement that is opinionated and political, not based on facts or rationality, and roughly half the US population at least does not agree with it.

So, besides how dishonest your comment may be, at least all the readers (who somehow missed that unmissable point, but I digress) get the idea.

Edit: the presence of the comma forbids any interpretation as "{follows DEI} AND {violates nondiscrimination laws}", and instead it reads as "{follows DEI} AND {by the way you already know/agree that DEI violates nondiscrimination laws}". Which any project leader that doesn't believe that DEI violates nondiscrimination laws will reject instantaneously.

But I have the sense that you are not discussing in good faith anyway, so...

Although you can just make the disease carriers immune to the disease.

In that case, not even need to exterminate any species.

That's typically done by introducing some Wolbachia in their gut.

(Edited: as the Rebble project just uses the Pebble app)

On Android, should I give a try to GadgetBridge, which seems both more open but way less official, instead of the Pebble app?

And by the way, why not make the Pebble app open source? I don't see any compelling reason.

Not impressed to see the official Pebble app and app store be closed source once again. Looks like Pebble is taking the Google Play route by making it inconvenient to use the underlying open source software without a proprietary service.

The underlying library (libpebble3) is open source, and Rebble has plans to fund their own app based on it. I plan to switch to that once it's ready.

In the meantime, I believe GadgetBridge is more limited, so I'm planning to stick with the official app for now.

I've used Gadgetbridge with the Pebble and many other compatible smartwatches, would recommend.

Interesting, this constant current source notion.

For a design without feedback, and in an energetically inefficient way, maybe this can work too:

1. Determine what will be the maximum resistance of the "current consumer" part of your circuit throughout its operation.

2. Prepare a resistor several magnitudes larger than the resistance above.

3. Connect to the resistor above a (huge) voltage source so that the resulting current is the one you target for your current source

4. Put the "current consumer" part of your circuit in series with the large resistor.

This is pretty much what we do to apply small bias currents to our superconducting circuits. The signals are small (<1 uA), and the power is dissipated outside of the cryostat, so this method is very simple and effective. The voltage and resistors don’t even need to be that huge, ~10 MOhm or below, and correspondingly, <10 V.

It works. In most applications it would be wasteful of electrical power (and money). You have to generate this very large voltage that (it turns out) you don't really need.

On the other hand that circuit is very easy to understand and build and test.