#documentation

z428@loma.ml

Close to 4pm. Cleaning up. Book-keeping several different ways. Non-functional requirements meet non-technical effort. Or: The experience of sinking amazing amounts of time in unplanned, unchartered side-arms of complex processes. Here be dragons, this is where things start becoming unpredictable.

#outerworld #technology_and_its_amazing_consequences #early_office_hours #documentation_and_other_unpleasant_tasks

#technology and its amazing consequences #early office hours #documentation and other unpleasant tasks

analysisparalysis@pod.beautifulmathuncensored.de

Is there a middle ground between pay and get support or open source, don’t complain?

I have a beef with open source artificial intelligence the way it currently is presented.

It starts with promises. A new model like llama, much better than the predecessor due to more parameters.

Then everyone fine tunes models and uploads them.

Whenever you run into issues compiling, using and managing expectations, nobody is there to talk to, because “open source”.

Often, provided there’s documentation, it’s written for computers, not people.

Transformers being black boxes, you always have the choice to take it or leave it. There is no debugging, really.

Most, me included, do not know how the math behind it works, so we are at the mercy of tutorials, which detail an ultra-niche case, 1% of users can apply.

Is there a middle ground between pay and get support or open source, don’t complain?

#artificial-intelligence #open-source #support #debugging #documentation #math #tutorials #complaints #middle-ground #pay

hankg@friendica.myportal.social

Over the summer I was really ramping up my Friendica contributions so wrote some quick guides on how to set it up for serving or developing. Then other projects looked like it'd be a while before I'd get back to it so I crushed all my VMs. Now I'm contributing again so have my handy blog posts to help me bootstrap again. This is *exactly* why I put this stuff on my blog in the first place. Helps others and even makes it easier to help my future self. #blogging #friendica #friendicadev #fediverse #documentation https://nequalsonelifestyle.com/2022/07/30/creating-friendica-server-ubuntu/

yew@diasp.eu

My friend Jakob in Russia mailed...

Hans-Martin est un paysan à l'ancienne qui vit hors du tempsHans-Martin is an old-fashioned farmer who lives out of time

Marie-Ange Tinevez commd 3 weeks ago

C'est un homme merveilleux est doté d'une sensibilité et de douceur dans ses explications.
C'est plutôt rare de voir des personnes comme lui qui tient et perpétue ces traditions de la terre.
BRAVO cher monsieur et continuez de prendre soin de vous.
Magnifique reportage !!!

#farmer #skills #instrument #crafts #Switzerland #documentation

lorenzoancora@pod.mttv.it

Gain unprivileged access to an overlapped directory in Flatpak

Issue

/usr and other hierarchies on the host cannot be accessed from Flatpak, because they conflict with the sandbox. Instead, you are presented with a fake, overlapped filesystem hierarchy. Currently, Flatpak alone has no working options to solve this issue, as configuration overrides have no effect on those special filesystem hierarchies. As Linux does not support directory hard links, this is a serious nuisance!

Solution

Luckily, there is a workaround to safely access the original directory without having root access, if your sysadmin (or you, if you own the system) installed the bindfs package.

The bindfs command uses a FUSE filesystem to mirror the contents of a directory to another directory:

bindfs /overlapped ~/.overlapped

If high performance is needed:

bindfs -o multithreaded /overlapped ~/.overlapped

If security (read-only access) is needed:

bindfs -o ro /overlapped ~/.overlapped

Example

TASK: access the documentation on a Debian system from a Flatpak app.

user@localhost:~$ mkdir .doc
user@localhost:~$ bindfs -o ro,multithreaded /usr/share/doc .doc
user@localhost:~$ ls .doc

…will grant you fast, read-only access to /usr/share/doc by visiting .doc in your user home.
ls .doc will list the contents of /usr/share/doc, while .doc is not a symlink but a simple directory created by you.
You can now eg. use the Flatpak version of Mozilla Firefox to browse file:///home/yourusername/.doc and it will let you read the files in /usr/share/doc, which are normally inaccessible under Flatpak.

Note: this is not an official workaround, I've found by accident. If you know better alternatives please feel free to comment so other users can benefit. Thank you.


Tags: #linux #gnulinux #debian #flatpak #sandbox #virtualization #security #hacking #filesystem #fs #docs #sysadmin #sys #documentation

anonymiss@despora.de
dredmorbius@diaspora.glasswings.com

I'm planning an update to my Markdown Quick Reference

I'd like to fix a few of the omissions and a couple of mis-categorisations, such as the role of the description text in images.

Other features & behaviours:

Possibly, #jq tools for recovering source code of posts and comments.

Other suggestions / additions / changes / corrections welcomed.

I'm also posting this as its own post so that the revision itself can be reshared (a quirk of reshares...).

#Markdown #quickGuide #tips #googleplus #newhere #formatting #HOWTOs #Documentation #Diaspora