WebDAV isn't dead yet
Peter Vágner reshared this.
WebDAV isn't dead yet
Peter Vágner reshared this.
Beginning June we witnessed a sudden surge of Delta Chat usage especially in the US and Cuba. We don’t know the social dynamics behind it but it probably helps that Delta Chat apps resiliently work...delta.chat
Peter Vágner reshared this.
[arch-dev-public]: New way to support Arch Linux: GitHub Sponsors
Peter Vágner reshared this.
reshared this
Introducing the development blog for Eternal DuskEternal Dusk Development Blog
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.
Peter Vágner reshared this.
HTTP Upload on conversations.im is temporarily unavailable. Our hosting provider is working on resolving the issue.
In the meantime you should be able to get half decent results - at least in 1:1 chats - by long pressing the failed file transfer and selecting 'Retry as P2P'.
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…
Peter Vágner reshared this.
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.
pg_dump and pg_restore are reliable tools for backing up and restoring Postgres databases. They're essential for database migrations, disaster recovery and so on.Sai Srirampur (PeerDB Blog)
Peter Vágner reshared this.
@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 🫠
@j @sun Tons of features you probably don't need and a unique ability to drain your company of all its money both in licensing costs and Oracle DBA salaries
Although if you have a particular problem they will make you a custom patch you can apply to your Oracle database. A change to the code nobody else will ever have. It's bizarre.
@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.
@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
they should be using zfs at that scale
It also makes snapshots stupid easy. You can get pretty creative to do point in time postgres restore for a 100 TB DB in under 15 minutes.
@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
+ UPDATE (2021/12/21) After lots of feedback on Reddit (thanks /u/BucketOfSpinningRust!) and doing some more experimenting and digging, I've updated this post with more information -- new/updated sections are marked "Update".vadosware.io
> 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
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?
How to easily integrate a XMPP server with Akkoma or Pleroma. In the following we will concentrate on Akkoma (a better Pleroma fork), but Pleroma should work more or less the same.JoinJabber
Peter Vágner reshared this.
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
A utility that extracts text from images or PDFs using a local or remote OpenAI-compatible LLM API endpoint with vision-capable multimodal models. For PDFs, each page is rendered to an image and pr...GitHub
reshared this
Some Facebook users have noticed new settings that let Meta analyze and retain your phone's photos. Yes, you read that right.Elyse Betters Picaro (ZDNET)
Peter Vágner reshared this.
I’ve been dabbling further with AI-driven development and have another app for exploration. This time it is a basic RSS Reader for Windows I’m calling RSS Quick. Get the full details an…The Idea Place
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! 
reshared this
Peter Vágner reshared this.
reshared this
This form creates as many Tactile Bingo Card SVG files that you want and downloads them as a zip file.blindsvg.com
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.
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.
reshared this
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>browser.tabs.groups.smart.enabled = false<br>browser.tabs.groups.smart.optin = false<br>browser.tabs.groups.smart.userEnabled = false<br>reshared this
A Cli package for the public Radio browser API, built to be lightweight , accessible and easy to use from the ground up. - GitHub - tgeczy/radio-browser-whiptail-cli: A Cli package for the public ...GitHub
reshared this
reshared this
honestly yeah
just tell developers that improving accessibility api support will enable them to navigate their entire computer with vim hotkeys
Peter Vágner reshared this.
Peter Vágner reshared this.
A Global Look at Teletext
Link: text-mode.org/?p=23643
Discussion: news.ycombinator.com/item?id=4…
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 likes this.
Peter Vágner reshared this.
Peter Vágner likes 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-…
Knock, knock, knock… on wood rooms, baby 🎵 Ooh ooh ooh ooh ooh ooh 🎶 That’s right, Fractal 12 adds support for knocking, among other things. Read all about the improvements since 11.GNOME Discourse
Peter Vágner likes this.
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 over WebSocket Web client. Contribute to iquercorb/xows development by creating an account on GitHub.GitHub
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! 🎉 🤸
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 👟
reshared this
Peter Vágner reshared this.
This sounds like a question for @hackerboards
(Their website is a database about single-board computers, although from a quick check I couldn't find specifics on open boot processes
hackerboards.com/ )
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.
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."
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 😂
Peter Vágner reshared this.
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 likes this.
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.
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:
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.
A wayland compositor to explore 3D windowing. Contribute to evil0sheep/motorcar development by creating an account on GitHub.GitHub
reshared this
reshared this
feld
in reply to feld • • •there's an old comment (~2015) on HN by the rsync.net team saying they removed WebDAV support from their service because of issues with mod_dav in Apache and it was abandoned / couldn't reach the devs...
but the git history disagrees with that. It came back to life.
github.com/apache/httpd/commit…
History for modules/dav - apache/httpd
GitHubHat Man
in reply to feld • • •feld
in reply to Hat Man • • •Hat Man
in reply to feld • • •feld
in reply to Hat Man • • •it would need to be SFTP in a jail/container that's behind a wireguard tunnel that goes to a cloud server... would not be fun to set that up; would have to definitely use a separate port from 22 and then I couldn't integrate it with my LDAP auth as easily unless I setup all the pam ldap shit...

edit: also some of the things I use this for do not support SFTP, sooo
verita84
in reply to feld • • •feld
in reply to verita84 • • •verita84
in reply to feld • • •Yeah. So glad I went back to NFS instead of that shit. I was a big fan of them for years and even helped in their Slack channel and earned a minio sweater.
We're they GPL or some other license that will prevent a fork to fixing their mess
feld
in reply to verita84 • • •John-Mark Gurney
in reply to feld • • •One problem with webdav is that there isn't a standard way to write partial files. The spec only allows complete overwriting of files. Apache and others provide an extension to do partial updates, but as you mention in your post, the v is for version, and so it wasn't designed to do partial updates, only wholesale replacement.
I can dig up references that talk more about it, if you want.
feld
in reply to John-Mark Gurney • • •John-Mark Gurney
in reply to feld • • •feld
in reply to John-Mark Gurney • • •