Rectangle-packing app needed to “montage” scans of paper receipts (perhaps with LaTeX and ImageMagick interfacing)
Rectangle-packing app needed to “montage” scans of paper receipts (perhaps with LaTeX and ImageMagick interfacing)
Rectangle-packing app needed to “montage” scans of paper receipts (perhaps with LaTeX and ImageMagick interfacing)
Rectangle-packing app needed to “montage” scans of paper receipts (perhaps with LaTeX and ImageMagick interfacing)
No way to backup our Lemmy posts.. really? That’s crazy, after so many years. App needed!
Lemmy web client: the “Next” button just loops back to the same page
A way to download radio schedules would be nice. Are the UK’s open data laws useful?
We need an app to harvest supported h/w lists of all FOSS smartphone platforms - to easily see which OS works on a particular phone
Two Three browsers that should/will give us netneutrality by making web fetches p2p (CENO, Akoopa & Agregore)
CENO: a p2p web browser that uses torrents to circumvent censorship -- does not work
NymVPN: The First Real-World Decentralized Noise-Generating Mixnet for Anonymity -- this Tor successor will be presented at FOSDEM
Software (“Akoopa”) forks Tor Browser to browse the web on torrents -- tor users may finally get an alternative to Cloudflare better than archive.org
Software (“Akoopa”) to browse the web on torrents -- one of my dreams may become reality
Software to re-decentralize the web by building a modular browser (will be at FOSDEM)
The philosophy that it’s okay to force everyone to change their behaviour to appear less like baddies (bots/criminals/adversaries)
The philosophy that it’s okay to force everyone to change their behaviour to appear less like baddies (bots/criminals/adversaries)
Why not repurpose obsolete smartphones as DAB metadata displays?
Why not repurpose obsolete smartphones as DAB metadata displays?
Why not repurpose obsolete smartphones as DAB metadata displays?
🥾 Microsoft boot lickers represent a majority of FOSS devs. FOSS principles solve many problems but not this one. 🌀 Debian gives some refuge.
Bug reporting is a global shit-show. It needs federation. And a bug report aggregator with local data store.
Bug reporting is a global shit-show. It needs federation. And a bug report aggregator with local data store.
The mastodon-archive man page gives an idea of what it does:
usage: mastodon-archive.py [-h] [--quiet] {archive,replies,media,text,context,html,split,expire,report,followers,following,mutuals,whitelist,fix-boosts,login,meow} ...
Archive your toots, favourites and bookmarks, and work with them.
positional arguments: {archive,replies,media,text,context,html,split,expire,report,followers,following,mutuals,whitelist,fix-boosts,login,meow} archive archive your toots, favourites and bookmarks replies archive missing toots you replied to media download media referred to by toots in your archive text search and export toots in the archive as plain text context show a toot in context (i.e. with its ancestors and its descendants html export toots and media in the archive as static HTML split split an archive into two expire delete older toots from the server and unfavour favourites if and only if they are in your archive report report some numbers about your toots, favourites and bookmarks followers show followers following find people you are following but who never mention you mutuals find people you are following and who follow you back whitelist print the whitelist to help you debug problems fix-boosts mark all the boosts as not deleted (triggering their deletion) login login to the instance for testing purposes meow import your backup into Meow, a browser-based export viewer (see https://purr.neocities.org/about/)
options: -h, --help show this help message and exit --quiet, -q do not output normal status messages
Once you have created archives in the current directory, you can use 'all' instead of your account and the commands will be run once for every archive in the directory.
Something that merely performs the backup function would be a great start, and the most useful function. But from there it could get quite complex with useful features. Mastodon-archive goes as far as to fetch content by others when it is a direct reply to something the user said. But I would favor going further and grab the whole thread of any thread the user spoke in.
Some non-essential but useful features in a Lemmy variant might be:
In any case, a simple one-off backup would not need a huge effort. I suspect it would start with this API call: https://lemmy.readme.io/reference/get_user The natural next advancement would be to run the same job multiple times and expect it to not re-fetch already fetched content. For some reason that’s a little messy on Mastodon.. not sure about Lemmy. On mastdodon, Kensanada’s code decides that after seeing an already archived msg 5 times that it need not crawl deeper. Feels a bit ad hoc / non-deterministic.