A Global Look at Teletext

Link: text-mode.org/?p=23643
Discussion: news.ycombinator.com/item?id=4…

Last week, I started an Ableton Move track. Today, I finally finished it.

This is a thing I call "Fly on the Wall." Basically, I just wanted an excuse to use one of the Sliced Loops presets, which are in the latest Move beta, along with one of the new autofilters in combination with a second filter and LFO to make one of the included single-sample E-piano patches sound less boring.

- Knock-knock.
- Who's there?
- Dozen.
- Dozen who?
- Dozen anyone want to let me in?

Celebrating a dozen of #Fractal versions with knocking support! Get Fractal 12, the new version of your favourite #Matrix client for #GNOME from #Flathub now!

discourse.gnome.org/t/fractal-…

Oh look, a new #xmpp client for the web that actually looks good 🚀

--

GitHub - iquercorb/xows: Lightweight and modern XMPP over WebSocket Web client.

github.com/iquercorb/xows?tab=…

I'm excited to announce that #Convo, my #XMPP messaging app for #KaiOS has received a grant from @nlnet, or, more specifically, @NGIZero! 🎉 🤸

nlnet.nl/project/Convo/

I can now turn what began as a quick project made in a providential three weeks of free time into an app that can...actually do basic things like add contacts 😅

More importantly, it'll make the open and standardised messaging protocol available to a mobile platform where few large players have dared to tread 👟

#NLnet #NGIzero

The things I learn, even at my age, simply by reading documentation are WILD!

Today: #SQLite3

"In addition to reading and writing SQLite database files, the sqlite3 program will also read and write ZIP archives."

sqlite.org/cli.html

Happy 21st Birthday @openstreetmap! 🍰 🥳 🎈

Gonna meet up with friends to celebrate, do some on-the-ground surveying, probably also walk around with a 360° cam to get imagery for @panoramax. And fly a drone, to get some nice aerial imagery while we're at it! 🗺️ 📷

And of course have some cake too 😂

#OpenStreetMap #panoramax

As it is the start of the month I would like to invite my fellow #Blind, #DeafBlind, and #VisuallyImpaired people, along with their family, and friends, to #OurBlind. OurBlind comprises the #Discord, #Lemmy, and #Reddit communities operated by the staff of the r/Blind subreddit, as well as those who have joined since the creation of the Discord in 2022, and Lemmy in 2023. We have members from all over the world, and of all ages, hearing and vision levels, and are a welcoming and safe space for Our #LGBTQIA and #neurodiverse friends. Our general community guidelines, and the links to reach our platforms can be found on our website.

ourblind.com/

@main @mastoblind

I want to defend Wayland here and explain a crucial piece that I think people are missing...

The splitting of protocols in Wayland and compositor reimplementation were to allow for new form factors. It had to sacrifice the guarantee of all desktop app functionality being present to achieve that.

The idea (as I see it) was never to have 500 desktop compositors all trying to reimplement the same thing with slight differences. Iinstead, it was for 500 different interfaces for different platforms that are compatible with the same apps (e.g. desktop, laptop, phone, car screens, AR/VR, watch). Different form factors have totally different ways of dealing with interface, but share enough common features where it makes sense to have 1 base protocol and many other ones for device/form specific features.

Problem is, while in 2008-2016 we had a ton of new experimental UIs coming out on a semi-regular basis (that was the peak of the whole convergent phone/tablet craze, smartwatches started, fancy car UI, touch tables, early AR/VR) things have quieted down. The purpose of Wayland's insane modularity hasn't been visible to most people given it's almost always complained about in a desktop contest vs X11. But X11 was literally only designed for a desktop form factor and has been refined for that 1 purpose for decades!

As an example of different form factors, Wayland lets IVI (in-vehicle infotainment) systems work way better than Xorg could have. Desktop window layouting on that platform would inherently produce massive amounts of unnecessary complexity, and the ability to direct scanout saves on power/expensive compute. Automotive Grade Linux and COVESA maintain reference interfaces for cars so companies can iterate a ton faster. Wayland gives the app compatibility and they can make the system UI work with more flexibility and ease than an X11 window manager.

Take Linux Mobile too, the compositor can reliably enforce window layout and boundaries and composition. While this could technically be done with an X window manager and compositor, doing it with Wayland guarantees reliability as the app simply doesn't have a choice or room for error. Some things like drag and drop of toolbars doesn't make much sense on mobile given how small the screens are.

There's some interfaces where X11 is basically impossible to use. In AR/VR (where i am making a Wayland compositor) the concept of a screen simply does not exist. How is an app supposed to position itself when the very concept of 3D is not part of the protocol? In Wayland I don't have to implement the protocols that don''t work (e.g. layer shell) and therefore any apps that don't need it will be compatible..

Wayland has allowed for insane levels of flexibility, things that no other display server architecture can do reasonably. Total flexibility between app and screen, direct scanout without hacks, AR/VR support, etc.

Here's some fun and useful stuff that's been done with Wayland, stuff that X11 could never reasonably do:

1. LG Smart TV UI: youtu.be/4cmYCK9PBkM
2. Multiple user collaboration on touch tables with arbitrary rotation: youtu.be/8xtjJTJAQsY
3. AR/VR apps running in windows and volumes at the same time, all interactable back in 2014 (eat your heart out magic leap and apple): github.com/evil0sheep/motorcar
4. Presentation slides that were themselves a Wayland compositor written in Qt and QML so therefore allowed fully interactive live demos in an integrated form factor with a very popular and easy to code UI framework: youtu.be/mIg1P3i2ZfI
5. Cosmic panels are actually Wayland compositors, meaning widgets can draw literally anything from any toolkit in any language.

Now, could Wayland devs maybe have distributed features across protocols better? Worked with app toolkit devs to ensure the protocols they made actually fit what the apps and compositors needed? Stopped bikeshedding (though imo many cases of "bikeshedding" are simply accounting for other form factors)? Absolutely!

My point here is simple: there was a reason for making it this modular, for not having a standard implementation. It wasn't just devs trying to impose some ideology, it wasn't some corporate takeover. It's good reasons that people using X11 on their desktop/laptop don't encounter. If we made something that wasn't universal, most apps wouldn't be compatible with it and therefore everything but the desktop form factor would lack apps.

Kopia is a Cross-platform open source backup tool for Windows, macOS & Linux with fast, incremental backups, client-side end-to-end encryption, compression and data deduplication. CLI and GUI included for backups and restore.

github.com/kopia/kopia