in reply to feld

I was looking at it for general usage, where users expect to be able to do partial updates of large files and not have it take a minute to update. Some clients can do partial updates, but I abandoned the idea of using webdav because none of the clients publish what features like these they support, so how knows when macos or windows will break/deprecate/remove partial updates.
Peter Vágner reshared this.

#deltachat is being used in virtually all world regions where one or more other messengers fail to work. We recently released a major milestone (V2 security hardening releases) that prepared the ground for chat profiles to have multiple #chatmail relays at once ... failure or blocking of a single relay would not disrupt chatting anymore. But multi transport also helps with the "centralization problem in decentralized systems" ... delta.chat/en/2025-06-04-surge…
(Funding is looking good currently btw!)

Peter Vágner reshared this.

Peter Vágner reshared this.

In today's episode of #accessibility shit-fuckery: our new dishwasher.
In terms of form factor, Fisher & Paykel DishDrawers really suit us: you effectively get two half dishwashers, so you can easily run a half load, run one while you're still filling the other, etc. We had them at our old house years ago and they were awesome. They were also the most accessible dishwasher I've encountered by design: they had tactile buttons, and even though some of the buttons cycled between options, there were different beeps when you wrapped around to the start of the options, so if you couldn't see the screen, you could choose what you wanted easily once familiar.
So when our old dishwasher died last week, it was a clear choice: we'd get DishDrawers. There's always a risk that new models will regress accessibility, and unfortunately, it's pretty difficult to test or find out about stuff like this. But this new model also has WiFi connectivity, so I figured that would work as a fallback at least.
It turns out that they're all capacitive touch buttons; i.e. not tactile, no press. Worse, there are no distinct beeps when you wrap around to the first option, etc.
So I resigned myself to using the app, which is surprisingly very accessible. But... no go there either. Because of a safety feature you can't disable, you have to enable remote start using the (inaccessible) buttons on the dishwasher. Remote start gets auto disabled when the door is opened, after the next wash completes or after 72 hours, whichever comes first.
At best, that makes this thing extremely tedious for me to use. I can stick tactile dots above or below the buttons, but even then, it's easy to accidentally touch a button while you're looking for them and you can easily choose the wrong option due to the lack of useful audible feedback. I already have this problem with our air fryer and it frustrates the hell out of me. But I guess it just is what it is, as is so often the case.
The worst part is that they took a reasonably accessible product and made it inaccessible. And for what? Visually pleasing touch buttons that probably don't even function when you have wet hands (because surely people don't have wet hands in a kitchen?). It's Thermomix all over again. And the message these companies send is clear: "we don't care about people with disabilities at all. We don't even give it a thought."
I called Fisher & Paykel to see if there's anything they can do and it's been escalated to their tech team, but I'm not holding my breath, especially because the inability to permanently enable remote start is a deliberate safety choice. I'm just so, so tired of struggling with and fighting these battles every. Single. Day. I barely even have the energy to be angry. The temptation to just give up is immense.

reshared this

Peter Vágner reshared this.

This is what I’ve been working on for last months at #CVUTFEL – electronic door sign for classrooms. 10.2" e-ink display, ESPink #ESP32 board from #Laskakit, battery (for some), a custom case, firmware and control server. Receives images via MQTT, sends telemetry back. #IoT

The case was designed in FreeCAD and printed it on Prusa MK3S and Prusa Core One. Firmware is built on Arduino SDK with patched GxEPD2_4G lib. Control server is written in TypeScript and runs on NodeJS. It renders screens to 2-bit grayscale PNG and sends via Mosquitto.

The price is ~115 EUR of you order the e-ink display and battery directly from China.

Most of this is my work, from the hardware up to the control server and also monitoring. It’s a very interesting project, a nice change from what I normally do because it’s a physical object. :)

This batch is 32 pieces and they will be installed mainly in Dejvice this month.

This entry was edited (4 months ago)

Peter Vágner reshared this.

Peter Vágner reshared this.

For a service that depends directly on a Postgres database they've shown:

- they don't know how to properly manage storage
- they still never turned on pg_checksum
- they have no idea how to run a reliable production Postgres cluster

These are unserious people trying to run a serious project and it should make you very concerned about how professionally they do all their work
RT: mastodon.matrix.org/users/matr…


Sorry, but it's bad news: we haven't been able to restore the DB primary filesystem to a state we're confident in running as a primary (especially given our experiences with slow-burning postgres db corruption). So we're having to do a full 55TB DB snapshot restore from last night, which will take >10h to recover the data, and then >4h to actually restore, and then >3h to catch up on missing traffic. Huge apologies for the outage. Again, folks using their own homeservers are not impacted.

Peter Vágner reshared this.

in reply to feld

Oh a mysterious "slow burn" of Postgres corruption? Where is the engagement on the Postgres mailing lists? I haven't seen a single thread about this issue on the pgsql-general or pgsql-hackers lists.

It's either a hardware storage bug, a raid implementation bug, a kernel bug, or their Postgres/filesystem tuning is trading data reliability for performance. But they're not sharing anything of value.

Postgres doesn't just corrupt itself. We have several DBs > 100TB at $work. Many people have significantly larger databases...

I kinda doubt their recovery times too. They will probably forget that they need to disable indexes to make the restore have a reasonable speed. And pg_restore is single threaded per table. 1.5TB can take 1.5 days.

blog.peerdb.io/how-can-we-make…

I think they're fucked. I wonder if they will be able to recover without it taking months, literally. They haven't indicated they're using anything but vanilla Postgres.

This could be the end of the matrix.org homeserver.

This entry was edited (4 months ago)

Peter Vágner reshared this.

in reply to Blurry Moon

@sun Oh I don't disagree, but Oracle has had billions poured into it so they can make that possible. Postgres is nearly as good as Oracle in almost all use cases, but these types of maintenance operations have not yet been engineered for performance.

The companies doing the Postgres forks have been the ones innovating here and putting their time and expertise into making sure they solve their customers' needs. And often those improvements get merged upstream. But as far as R&D goes it's still a drop in the bucket compared to Oracle 🫠

in reply to Hat Man

@j @sun At that point you basically consult them for every patch / upgrade so they can keep your changes working. This is sometimes a major issue keeping companies from upgrading to the next major release as their query planner etc will change and you could lose the performance you had or new problems arise that need different custom patches to keep your workload performing as expected.
in reply to Hat Man

@j if you aren't a big company the few benefits aren't worth it, in fact I would say it has little benefit unless you buy their most expensive horizontally scaleable option which is meant for busineses where the data size is so massive it should be nosql but you're architecturally locked into rdbms. very time I've mentioned it on here people say "you're doing it wrong" well I have to explain that a lot of corporate customers are just plain locked into somethigng that got built in the 1990s and it would take a hundred million dollars and shitloads of uinacceptable risk to rewrite. for those customers there is a big fat oracle database and you will pay a LOT for it.
in reply to Hat Man

@j for years and years people went with oracle because it was the only ANSI SQL compliant database, everybody else either didn't have x feature or it was a proprietary extension. but this hasn't been true for years, Postgres is compliant.

oracle also spends a gazillion dollars convincing your company to put everything into oracle though, so they have really stupid bad shit you should never do, but on the surface you think "I'm already paying them so I'll integrate that too". it's pretty transparent that they're taking advantage of know-nothing managers to trap companies into never being able to leave.

in reply to Blurry Moon

@sun @j We had a scheduled overnight outage in 2007 to upgrade Oracle 9i to 10g. It was an 8 hour outage and the process to backup then apply the patches took 7 hours.

We couldn't afford more Sun servers. A restore from backup was also 8 hours. We practiced it several times because even doing one thing out of order breaks the database.

It was all or nothing (and probably losing our jobs).

It worked. I was never so scared though

in reply to Blurry Moon

@sun @j You can and I have done so without issues, it's just not a simple install, configure Postgres and let it run thing. You have to change record sizes to avoid fragmentation, if you are on fast SSDs disable ZIL on your DB dataset and hope that Postgres will ensure data integrity with fsync and pg_wal, or move it to a special ZIL SLOG on fast SSDs. And those are the absolute basics of what you have to do to make it somewhat work.
in reply to Blurry Moon

@sun @phnt here's this too
vadosware.io/post/everything-i…

Setting record size to 8k is faster than 16k but only for a little bit because it gets super fragmented. Setting to 16k fixes the fragmentation and provides better compression ratios since compression happens to each record block. Setting to 32 or higher could be interesting and help compression even more. You won't see improvements beyond the default 128k on like 95% of drives and it could even hurt performance. That being said 1M+ record sizes may be useful in conjunction with zstd-4 for long-term archival of compressible data like database backups. All of this can be changed whenever so it's not that big of a deal. Block size you're stuck with forever so make sure you set the correct block size.

Most of the data the database actually cares about at any time will live in the arc (ram cache) and if you use compression it's compressed in the ARC so you get even better cache hits.

For compression I used lz4. Zstd (even compression level 1) was too much latency. Lz4 is really great and shaved off about 45% of data needing to be written to disk. That was the main reason I switched to zfs. It was the only practical filesystem for postgres that supports disk compression.

It makes postgres upgrades super fast and easy. Just take a snapshot, hard link the database files, fire up the new postgres version and it should work but if it starts fugging the database then you can just easily restore the snapshot.

I came for the compression and ending up loving it because not only is it the best filesystem but it's the best disk management system too. You can even just create raw volumes and format them however you want. You can have ext4 on zfs, you can have NTFS on zfs, you could even put zfs on top of zfs if you really wanted to.

Zfs is also the only way to have a compressed swap partition

in reply to Hat Man

> All of this can be changed whenever so it's not that big of a deal.

when you make these changes to ZFS filesystems it does not change the existing data. That problem is left to you to solve -- traditionally by restoring all the data from backup.

However, a new tool is coming called "zfs rewrite" that will let you atomically rewrite underlying blocks so the data gets the new storage settings applied to the filesystem.

openzfs.github.io/openzfs-docs…

edit: this would also be useful for re-balancing your zpool if you add new zvols or something

This entry was edited (4 months ago)
Peter Vágner reshared this.

We updated our #akkoma integration page with an easy way to link your account to a Prosody #xmpp server: joinjabber.org/tutorials/integ…

Thanks to @nigel for testing it.

@akkoma maybe something to add to the official docu as well?

Peter Vágner reshared this.

Unknown parent

akkoma - Link to source

Kris

I assume as long as SASL-SCRAM-plain is the only way to achive auth integration with other system, there is really no way around that. Channel Binding is a nice feature, but personally I find it much lower priority than auth integration.

Maybe you could look into supporting Oauth2/OIDC login flows in Conversations? At least Prosody seems to have good support for this now, and I think this might be the only realistic way to have both Channel Binding and auth integration.

Peter Vágner reshared this.

One of the benefits of eSpeak-NG is that it doesn't make assumptions like reading "CUP" is Cuban Pesos (hello US OneCore voices) - but the flip side is that eSpeak will read the year 1987 as "nineteen hundred eighty seven". If you'd like it to read that as "nineteen eighty seven" & learn a little #regex on the way, then @fastfinge has you covered with the "Correcting Years With NVDA and Espeak" blog post: stuff.interfree.ca/2025/08/28/…

#NVDA #NVDAsr #Tips #Accessibility

reshared this

in reply to NV Access

I can't resist the temptation to discuss more OneCore oddities, we also can't forget the OneCore bug with reading ernesto, or have you been using applications where unchecking check boxes was necessary? Also fun fact. Microsoft David always uses its OneCore data even in SAPI5. Zira uses OneCore data in OneCore, but its older data in SAPI5. What this means, is that David will always exhibit these problems, but Zira will only if using OneCore and not SAPI.
Peter Vágner reshared this.

A utility that extracts text from images or PDFs using a local or remote OpenAI-compatible API endpoint with vision-capable multimodal models. For PDFs, each page is rendered to an image and processed sequentially; outputs are concatenated into a single Markdown document. github.com/robert-mcdermott/do…

reshared this

Peter Vágner reshared this.

Meta [is probably] secretly scanning your phone's camera roll - how to check and turn it off zdnet.com/article/meta-might-b… #meta #facebook #privacy #fail #ethics

Peter Vágner reshared this.

Peter Vágner reshared this.

I've been dabbling a bit more with AI-driven development and have a basic windows RSS reader joining my Sports Scores and Image Description Toolkit apps.RSS Quick, A Basic RSS Reader for Windows 1.0 Available theideaplace.net/rss-quick-a-b…

Peter Vágner reshared this.

in reply to André Polykanine

@menelion I use VS code, a GitHub Copilot subscription, and then various frameworks. My sports score and image description tool kit apps were python. RSS quick is a C sharp WPF application because I find the accessibility better for graphical apps. I also, as I think I have been in my blog post, want to be transparent that I am using AI for a sizable part of my development. I have the ideas and the understanding of what I want to happen and am using AI to help me deliver it more rapidly.
Peter Vágner reshared this.

Hey everybody, I've been playing the alpha of a creature collecting roguelite with accessibility for blind and other disabilities, there's also a demo on steam. The dev is trying to fund more development of the game so that it doesn't have to released with anything missing as the planned release date was September. If you like indie devs, roguelikes, and accessibility in games, please consider backing! :-)

kickstarter.com/projects/zeinm…

reshared this

Peter Vágner reshared this.

Recently, the meta rayban glasses have kind of been hitting me from all directions, and not gonna lie, I'm starting to consider buying them, since I rely a lot on identifying colours on displays of household appliances, reading documents on paper, recognizing frequencies/channel numbers on radios and so on. Could anyone who owns them please enlighten me if they work for the things I described? And mainly if the AI functions are supported outside of the US (since I'm from Czechia)? I remember reading about this limitation a few months ago, but maybe I'm imagining things. I'd be very glad for any answers, and if you could boost this post, that would really help me out a bunch. Thanks!

Peter Vágner reshared this.

Peter Vágner reshared this.

I made some final tweaks to the #Tactile #SVG Bingo card output for both portrait and landscape modes, made the site responsive, pretty, and functional in light and dark modes with CSS, and am happy to release this further out into the world! Thanks to @ChanceyFleet for bringing this little project to me! Now anyone can make tactile and embossable Bingo Cards whenever they want! We can do so much nonvisually with just a little code and a means of tactile output! blindsvg.com/pages/projects/bi…

reshared this

Peter Vágner reshared this.

It's concerning to me that arguably *the* way to get Linux apps, Flathub, has all of its packaging data hosted on GitHub, with seemingly no plans to move away from it. With the direction GitHub is going, I am worried that Flathub will want to move and it'll be too late to do it cleanly.

Update: With the way the United States is going.

#Flatpak #Flathub #Linux

This entry was edited (2 weeks ago)

reshared this

Peter Vágner reshared this.

It felt very weird to be on a plane that had a server with Nginx and Drupal installed on it. According to http headers at least, and those rarely lie. Definitely not a ground link, you aren't getting 5ms pings over satellite.

Their IFE system appears to serve MP3s ripped straight from iTunes (no DRM), with album metadata and such left intact. Is this legal? God only knows.

Peter Vágner reshared this.

Peter Vágner reshared this.

The ability to switch between NVDA profiles with different keystrokes and to tweak output settings for each one individually is just fantastic. Whenever I mess something up on my main audio interface, I can get things working again in moments by switching to my "rescue" profile (that's just what I call it) which is hard routed to always use my laptop speakers. Highly recommend this for anyone who plays around with virtual mixers, audio cables, etc. It did save my ass more times than I can count!

reshared this

Peter Vágner reshared this.

here's a few settings you may wish to consider for your firefox's about:config page.
browser.ml.chat.enabled = false<br>browser.ml.chat.shortcuts = false<br>browser.ml.chat.shortcuts.custom = false<br>browser.ml.chat.sidebar = false<br>browser.ml.enable = false<br>extensions.ml.enabled = false<br>

if your firefox is recent enough, you might want these to disable AI tab groups too (thanks @ilmari!)
browser.tabs.groups.smart.enabled = false<br>browser.tabs.groups.smart.optin = false<br>browser.tabs.groups.smart.userEnabled = false<br>
This entry was edited (5 months ago)

reshared this

Peter Vágner reshared this.

There y'all go. Since a few asked for it, and I realized none of my code shared similarities in design or philosophy to the BTSpeak's tool, I released my Radio-browser Python CLI tool here: github.com/tgeczy/radio-browse…
- useful on Raspberry Pi or other Linux distributions where just having a simple radio station player is what's missing. Can't say it'll get any mooer fancy than this, but we'll see! Took like 5 or 6 days to write it up in the end, wasn't just going to throw it all to AI to write without thorough supervision and fixing bugs, errors.
This entry was edited (5 months ago)

reshared this

Peter Vágner reshared this.

I've been an email hosting customer with #MythicBeasts (@beasts) for just under a day and a half, and I'm honestly very impressed. I opted for their email only plan since I already have webspace somewhere else. The main website and control pannel UI are very accessible to #blind #ScreenReader users like myself, with sections clearly structured with headings, pretty much no unlabelled links, buttons or other elements, and no annoying ads, pop-ups or anything else that could hijack a screen reader or lag a browser to pieces. I contacted them about an issue I'm having yesterday and the initial reply, *human* reply that is, took just over 10 minutes. The issue is still ongoing as of now, but I'm confident that it will be fixed soon; I did contact them at the backside of the working day after all. Not bad at all for the monthly price of just under a fiver! Also, bonus points for being a 2000s ISP, having started in the year 2000.
This entry was edited (5 months ago)

Peter Vágner reshared this.

Peter Vágner reshared this.

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.

Peter Vágner reshared this.

Peter Vágner reshared this.

FYI for TeamTalk server administrators who run Debian on an X86_64 machine, and may be considering upgrading to Debian 13: The ubuntu24-x86_64 package runs on Debian 13. You'll need the ubuntu22-x86_64 package for Debian 12. And BearWare, just because your opinion is that Ubuntu is the only version of Linux in existence, allow me to correct you to say that Debian was and is first.
Adendum: Someone pointed out that if you're using TeamTalk client in a Linux GUI, the Ubuntu24 version has accessibility problems, and the Ubuntu22 version will still run on Debian 13.
This entry was edited (5 months ago)

Peter Vágner reshared this.

Peter Vágner reshared this.

- 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-…

reshared this

Peter Vágner reshared this.

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=…

#xmpp

reshared this

Peter Vágner reshared this.

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

reshared this

Peter Vágner reshared this.

Among currently available ARM64 single-board computers, which one has the simplest and most fully open boot process? The Raspberry Pi family has boot handled by the VideoCore, a whole other processor running its own RTOS during and after boot. Other ARM64 boards, like the Rockchip RK3566-based Quartz64 that I own, have a Rockchip version of ARM Trusted Firmware (which IIUC runs continuously at a higher privilege level) as a blob. Is there any ARM64 board that avoids both of these?

Peter Vágner reshared this.

in reply to Matt Campbell

I'm a month late but:
Rockchip RK3399 (e.g. Pine64 ROCKPro64) has zero blobs. As in, both DDR init and ATF are open (former in mainline u-boot, latter in mainline ATF).

RK3588 (e.g. Radxa ROCK 5B+) has open mainline ATF, but closed DDR init (runs once at boot) at the moment.

K3576 (e.g. Radxa ROCK 4D) also has open mainline ATF, but closed DDR init.

RK3566 *does* have something in ATF but I've heard it has problems. Closed DDR init as well though.

Peter Vágner reshared this.

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

This entry was edited (5 months ago)

reshared this

Peter Vágner reshared this.

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

Peter Vágner reshared this.

in reply to Bastian Greshake Tzovaras

Had a blast at our little #OpenStreetMap birthday celebration. 🍰 🧉

It ended up being too windy to fly drones for long. Instead we recorded street-level images for #panoramax and GPS tracks, in addition to doing a lot of live surveying – using a huge range of tools that allow contributing to OSM!

In no particular order we at least used: @everydoor, @streetcomplete, @MapComplete, @CoMaps, HOTOSM's ChatMap, iD and JOSM.

Having so many different ways of making contributions is a real feature.

Peter Vágner reshared this.

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

reshared this

Peter Vágner reshared this.

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.

This entry was edited (5 months ago)

reshared this