mcepl

joined 1 year ago
[–] mcepl@lemmy.world 1 points 2 months ago

This post literally links to the leading one.

[–] mcepl@lemmy.world 1 points 6 months ago

Hmm, how to react to that? “Go through his brain and look for loose thoughts.”? (Sounds like Legilimency from Harry Potter world)

[–] mcepl@lemmy.world 1 points 8 months ago

https://github.com/swaywm/sway/ still claims that sway is “i3-compatible Wayland compositor”.

[–] mcepl@lemmy.world 2 points 8 months ago (3 children)

Ehm, what would be a difference for you, if you install sway?

[–] mcepl@lemmy.world 3 points 8 months ago (1 children)

Not vim necessarily, but I would really suggest thinking about a plain text editor of your choice and some of those lightweight markup languages (Markdown itself, reStructuredText, ASCIIDoc … I prefer rST, but they are mostly the same). Exactly because it allows me to concentrate on the content and ignore formatting. Besides, formatting, do you write for print or as everybody else these days for HTML? Why do you need a large word processor which is build primarily for preparing documents for print? Every serious text editor has some kind of plugins with spellcheckers, grammar checkers, dictionaries, etc.

[–] mcepl@lemmy.world 26 points 8 months ago* (last edited 8 months ago) (1 children)

Yes, of course, the sockets are the answer to everything (and BTW, d-bus uses sockets as well, e.g. /run/dbus/system_bus_socket on my current system), but the problem is no standard for the communication over these sockets (or where is the socket located). For example, X11 developed one system of communicating over their socket, but it was used just by few X11 programs, and everybody else had their other system of communication. And even if an app found some socket, there was absolutely no standard how exactly should programs communicate over it. How to send more than just plain ASCII strings? Each program had to write their own serialization/deserialization code, their own format for marshalling binary data, etc. Now there is just one standard for those protocols, and even libraries with the standard (and well tested) code for it.

[–] mcepl@lemmy.world 2 points 8 months ago* (last edited 8 months ago)

https://youtu.be/4WuYGcs0t6I (Richard Brown (FOSDEM 2023): “I was wrong about Flatpak, AppImage, and Snap”)

[–] mcepl@lemmy.world 1 points 8 months ago

Yup, and "I use Gentoo" before that.

[–] mcepl@lemmy.world 1 points 8 months ago

Without regards about this discussion, run, don’t just go, and buy a vertical mouse. Just saved my wrists.

[–] mcepl@lemmy.world 5 points 8 months ago* (last edited 8 months ago) (1 children)

Give a man a regular expression and he’ll match a string… teach him to make his own regular expressions and you’ve got a man with problems. -- yakugo in http://regex.info/blog/2006-09-15/247#comment-3022 (and yes, it is http:// never https:// for this domain)

[–] mcepl@lemmy.world 5 points 8 months ago
  1. Many Linux installers can preserve /home when asked nicely.
  2. (as root) rsync -avz /home/youruser/ other-machine:/home/
 

Is there any difference in cache files for Flatpaked Firefox and the normal one?

I have been using FanFicFare application for downloading Fanfiction stories as EPub from the main fanfiction websites. It works just fine for most of them, but there are now terrible problems with the biggest of them all, https://fanfiction.net, which is behind Cloudflare and generally inaccessible to scripts.

Therefore functionality has been added to script which with appropriate flags (-o use_browser_cache=true -o use_browser_cache_only=true) and when correctly configured it can “download” HTML pages from the Firefox (or Chrome) cache instead and stitch them together into EPub same as if the pages were downloaded from the Internet.

It all works perfectly fine with Firefox as packaged by major distributions (openSUSE in my case), but it doesn't work with Firefox installed from Flatpak. Is there any difference between the storage of cache in Flatpak Firefox? Is there some kind of access protection to its caches?

view more: next ›