tazjin

Your posts are very much like "I have discovered a truly marvelous proof of this, which this margin is too narrow to contain".

If a definitive answer on this topic was known then it, well, would be known.

Neither you nor any of the other people making confident takes in either direction actually know. You're just guessing.

It does, but only for chats between two specific devices. Multi-device support is one of its best features that you lose with E2E.

Key distribution is just too hard. I think we won't get a messenger for non-tech people that works well with multi-device and E2E basically ever.

EWM implements a Wayland compositor as a native thread spawned by a dynamic module in Emacs, it's a full compositor within the Emacs process: https://codeberg.org/ezemtsov/ewm

So it is architecturally possible (but infeasible in plain Emacs Lisp).

For river (the thing this article is about) I wrote an Emacs WM, but also opted for a dynamic module for the Wayland protocol parts: https://code.tvl.fyi/tree/tools/emacs-pkgs/reka

This one could technically be written in plain Emacs Lisp, but I'm happy to use something that already has all the XML codegen stuff for Wayland figured out. Dynamic modules work pretty well, fwiw.

It is probably country and language dependent, I think. I don't know anyone under 40 who doesn't write in cursive (in Russian), and for other languages I personally also write in cursive (and learnt that in school). I'm in my 30s.

Okay, so which hardware are you buying that isn't using any Chinese components?) I don't think the empire can make this kind of hardware from scratch without China at the moment.

Killing off free repos is not going to happen. That would be a suicide move on the level of the Digg redesign, or Tumblr's porn ban.

It kind of would be good for everyone if they did do it though. Need to get rid of this monopoly, and maybe people will discover that there are alternatives with actually good workflows out there.

People go through all this trouble to host convoluted chat systems, and all this time IRC is right there. There's modern servers like Ergo and modern clients like Halloy (or for the JavaScript addicts: Convos, The Lounge, Kiwi, ...) providing all the multi-device history sharing and emoji reactions you could need. All on top of a super simple, extremely battle tested protocol.

These weird anti-Graphene posts confuse me. I use GrapheneOS, fwiw, and I believe some things the project does (like its attacks on F-Droid) are misguided for orthogonal reasons.

However, it all makes sense from the perspective of Graphene not attempting to be a general purpose OS like Lineage, but explicitly a security focused OS. Security is often in conflict with what the average consumer wants, and they can go use Lineage or whatever.

It's like writing lots of comments complaining about OpenBSD devs coming across as grumpy and refusing to support Bluetooth. That is part of their value proposition! You're just not the target audience and that is okay.

I've only seen the carrier locked phones and long-term contracts in a handful of countries. I've lived in a lot of countries on three continents.

In many places the default is prepaid SIMs with separately purchased phones. Sometimes the prepaying can be automated (e.g. in Russia), sometimes it involves you physically going to a shop once a month or so (e.g. in Egypt).

Haskell has exceptions, so dependencies can still do plenty of harmful stuff ;)

The "assistant" is a personality that the "entity" (or model) knows how to perform as, it's strictly a subset.

The best article on this topic is probably "the void". It's long, but it's worth reading: https://nostalgebraist.tumblr.com/post/785766737747574784/th...

No. It was obvious from the title that this was about the UK, and also why should they - American sites don't indicate this either, and they have no monopoly on the language.

Huh? Clearly writing it is not easy, as per your own comment

Does anyone know of active work happening on such a license?

Xiaomi, Honor and Huawei make ARM-based notebooks like that. The closest to your description is probably the Qingyun line of laptops.

I'm not in the US.

I spent some time on Google Maps, and the furthest spot I managed to find from a town was about 35km. Note that I didn't say anything about supermarkets - this is a thread about car reliability, so the context is how far you can be from a town where it's reasonable to expect that someone can help you with your car.

Haha, how far is the middle of nowhere from the nearest town in Scotland? A few dozen kilometres?

The EU is entirely dependent on US services, which don't much care about a fringe phone OS some fraction of people in the EU use. It's like adding duck/egg, crow/egg and other similar problems into the dependency web, too.

You can sell the phones alright, and they might even work, but the fact is that participation in society - especially if you live in a city - will be much harder without Android/iOS.

Note, not impossible: You can always carry cash to avoid phone-based bank payments (which would be needed at e.g. my local farmer's market, where nobody has a card payment terminal), some taxi services (Yandex Go for example) provide a web view with some of the features, you can open map services in the browser ...

But for the browser-based cases the experience will be even worse than the standard app experience, and friction is overall much higher.

As a result, only a very small fraction of nerds are committed enough to buy and use these devices. You then have a chicken&egg problem about getting a third option to work.

The only way this has been done semi-successfully in recent years is Huawei's HarmonyOS - and they did it by way of a) already being an absolutely massive phone company, and b) keeping around an expensive Android-compatibility core for many years.

You mean there doesn't seem to be any English non-US resource.

My current take is that if you start an open-source project now, you should go full AGPL (or similar copyleft license), and require a CLA for contributors.

If your thing ends up actually good you now have a defence against exploitation, and a way to generate income reliably (by selling the code under a different license). afaik, organisations like the FSF even endorse this.

I regularly take the train between Moscow and Kazan. It's 12 hours, you can get on in the evening, have dinner on the train and then get a decent 8 hours of sleep before getting up, having some coffee and arriving.

It's much longer than the equivalent flight, but also much more comfortable. There's something annoying about airports - with the train I can get to the station 15-20 minutes before departure and it's fine.

Once the train rides get much longer than 12 hours it shifts, but there's a sweet spot right around there.

You don't need to. This is the first generation where there's millions of hours of online podcasts with tech bros for them to enjoy. In general, we're a uniquely well-documented set of generations, even if we exclude all the stuff that will be lost when Google/Facebook/VK etc. collapse.

where use of the GPL isn't merely inconvenient, but legally impossible

What sort of ecosystems are these?

Unfortunately nowadays traveling with DB has become a game of Russian roulette.

Ironically, Russian trains (even over distances of thousands of kilometres) are usually almost perfectly on time.

Germany's DB seems to fill the same niche as other companies there, like Telekom: semi-private companies living off old state-built infrastructure that they're now incapable of (or unwilling to?) maintain.

Or, we can expect better from software. Maybe someone can fork Firefox and make it run better, hard cap how much a browser window can use.

You can already do this. For example, I use `systemd-run` to run browsers with CPU quotas applied. Firefox gets 400% CPU (i.e. up to 4 cores), and no more.

Example command: systemd-run --user --scope -p CPUQuota=400% firefox

Is anyone else worried that a lot of people coming from the Rust world contribute to free software and mindlessly slap on it MIT license

Yeah; I actually used to do that to (use the "default license"), but eventually came to the same realisation and have been moving all my projects to full copyleft.

(I know Erlang well, but haven't used Gleam)

The library the parent links to says this:

Not all Erlang/OTP functionality is included in this library. Some is not possible to represent in a type safe way, so it is not included.

Does this mean in practice that you can use all parts of OTP, but you might lose type checking for the parts the library doesn't cover?

That is literally how a large fraction of airlines work. It's called Amadeus, and it did have a big global outage not too long ago.