Who this is for:
- You are Danilo (danix), building a Hugo theme for danix.xyz—a bilingual (Italian/English) hacker-themed portfolio/blog site. You're currently working on visual polish and styling enhancements to make content stand out against the dynamic matrix rain background.
+ You are Danilo (danix), building a Hugo theme for danix.xyz — a bilingual (Italian/English) hacker-themed portfolio/blog site. You just completed a major article import and processing pipeline, moving ~36 articles from the old site into the new theme structure.
What we covered:
- **Session 1 (Previous):** Added padding and glow effects to content sections. The single page content grid and article list items now have 2rem padding, 1px borders, and accent glow effects with CSS variables for light/dark theme support.
-
- **Session 2 (This session):** Implemented frosted glass + glow effect on header and footer for visual cohesion. Created a reusable `.frosted-bar` CSS component combining `backdrop-filter: blur(10px)` for frosted glass, glow shadow matching content cards, and theme-aware border styling. Applied to both header (with `border-b`) and footer (with `border-t`). Extracted RGBA values to CSS variables for maintainability. Fixed internal footer divider for styling consistency.
+ The session covered article import strategy and execution. We discussed asset organization using static/uppies/year/month/ folder structure, confirmed Italian and English articles should share the same slug with different translations, and then executed a complete import workflow:
+ ran the importer script to copy articles from the old site, audited imported articles for frontmatter issues, fixed type field values (remapping article → life/tech/quote), fixed minor issues like tags="" and draft="true" strings, migrated all co-located assets to static/uppies/
+ organized by publication date, created Italian article stubs with TODO placeholders, and created seven missing shortcodes (strike, em, dropcap, figure, highlight, img, youtube, gal-img) to allow articles to render. All 36 articles now build successfully with hugo server.
What was confirmed:
- **CSS Component (.frosted-bar):**
- - Uses `rgba(var(--bg2-rgb), 0.92)` background with dark/light theme variants
- - Includes `backdrop-filter: blur(10px)` for frosted glass effect
- - Applies `box-shadow: 0 0 20px var(--accent-glow)` glow matching content cards
- - Border direction controlled by templates (`.border-b` for header, `.border-t` for footer)
- - Full CSS variable support for light/dark/no-JS modes
-
- **Templates Updated:**
- - Header: Changed from `bg-bg2/92 backdrop-blur border-b border-border` to `frosted-bar border-b`
- - Footer: Changed from `border-t border-border/30 bg-surface/20` to `frosted-bar border-t`
- - Internal footer divider: Updated from `border-border/30` to `border-border` for consistency
-
- **Build Status:**
- - CSS rebuilt successfully with `npm run build`
- - No console errors or CSS regressions
- - Verified dark/light theme switching
- - Tested responsive design on mobile
- - All commits are clean and focused
-
- **Feature Branch:** `feature/footer-frosted-glass` with 7 commits (including plan documentation)
+ All 36 English articles are now in content/en/articles/ with corrected frontmatter. 1 article is type="quote", 2 are type="tech", 33 are type="life" (default when in doubt). 21 image/media files moved to static/uppies/ organized by year/month from article publication dates. All image paths in frontmatter updated to /uppies/year/month/filename. Italian stubs created in content/it/articles/ with matching slugs and draft=true status. Hugo builds without errors and articles render with correct type badges. Images load correctly from /uppies/ paths on the
+ article list page. Shortcodes for typora-root-url are preserved as requested.
Still in progress:
- Feature branch is ready but not yet merged to master. Waiting for your approval to merge or handle separately.
+ All 36 Italian article stubs remain untranslated (marked draft=true). No CSS changes were needed for the import, so npm run build was not required.
Next steps:
- 1. Review the frosted glass effects on header and footer in both dark and light modes
- 2. Hard refresh browser to clear cached CSS if needed
- 3. Decide whether to merge feature branch to master, or continue with other features first
- 4. Remaining work: fix taxonomy layouts (archive/term pages), implement more article type features, conduct comprehensive testing before publishing
\ No newline at end of file
+ Commit the imported articles, asset migrations, and new shortcodes. Translate Italian article stubs and set their draft=false when ready. Test articles end-to-end in the browser to verify all content, images, and features render correctly across both languages. Consider publishing a few translated articles to make the bilingual site live.
\ No newline at end of file
date = "2011-08-11T18:09:41+00:00"
draft = true
type = "quote"
-image = "loneliness.jpg"
+image = "/uppies/2011/08/loneliness.jpg"
author = "Danilo 'danix' M."
excerpt = "again on loneliness, solitude and misantropy"
categories = ["blogging", "quotes"]
--- /dev/null
++++
+title = "baking programs"
+date = "2019-01-02T15:36:49+00:00"
+author = "Danilo M."
+draft = false
+type = "life"
+excerpt = "baking a cake and building a program from source have a lot in common, and both will leave you satisfied once they've finished cooking"
+image = "/uppies/2019/01/bake-a-cake.jpg"
+categories = ["diy", "linux", "slackware"]
+tags = ["slackbuild"]
++++
+Compiling programs always feels like you’re baking a cake, you look for it, check the dependancies and then run the slackbuild, leave your computer to go grab a drink and when you come back you see an error, checking for it you notice you’ve forgotten a dependency, it’s like you put your cake in the oven, starts cooking and after a while you go “_oh shit, I forgot to add sugar to the dough_“.
+
+I’ve been compiling a couple programs in the past few days and I’ve ended up patching them a lot, to compile audacity I had to go around and add 6 patches before the script managed to compile correctly, and today with qpdfview it was the same, still dependancy errors but in the end I made it work and let me tell you, when you come back to your PC and the script has ended and it says the program is installed it’s almost like you could smell it, your freshly baked cake waiting for you to enjoy it..
\ No newline at end of file
--- /dev/null
++++
+title = "Bash Notes"
+date = "2023-04-07T11:20:20+02:00"
+draft = true
+type = "life"
+author = "danilo 'danix' m."
+format = "post"
+excerpt = "A 'sticky notes' kind of app, written in bash for all shell entusiasts."
+image = "/img/default_article.jpg"
+categories = ["bash", "notes", "linux", "diy"]
+tags = []
++++
+
+# bash notes
+
+## a simple note taking script written in bash
+
+I've found myself in need of a simple way to take notes, and since the other solutions available didn't meet my needs, I've decided to write my own script.
+
+It's a simple (enough) bash script, the only dependence (yet) is [jq](https://stedolan.github.io/jq/).
+
+here's all the functions that are now available:
+
+```bash
+Usage:
+ notes.sh [PARAMS] ...
+
+notes parameters are:
+ -h | --help : This help text
+ -p | --plain : Output is in plain text
+ (without this option the output is formatted)
+ (this option must precede all others)
+ -l | --list : List existing notes
+ -a | --add=["<title>"] : Add new note
+ -e | --edit=[<note>] : Edit note
+ -d | --delete=[<note> | all] : Delete single note or all notes at once
+ -s | --show=[<note>] : Display note using your favourite PAGER
+ -r | --restore=[<dir>] : Restore a previous backup from dir
+ -v | --version : Print version
+ --userconf : Export User config file
+ --backup [<dest>] : Backup your data in your destination folder
+
+if a non option is passed and is a valid note ID, the note will be displayed.
+```
+
+All the basic functionalities are present and working, it probably needs some polishing and some testing, so if you want to give it a try, let me know what you think.
+
+### Settings
+
+When you first run it, notes.sh will create all the files it needs to operate.
+By default the directory will be populated in `~/.local/share/bash-notes`.
+
+If you want to modify the predefined settings, you can export a user configuration file by running
+
+```bash
+notes.sh --userconf
+```
+
+And you'll have all your settings in `~/.config/bash-notes.rc`. This file will be sourced every time you run the script.
+
+You can change all these settings by editing the file:
+
+```bash
+# Binaries to use
+JQ=${JQ:-/usr/bin/jq}
+EDITOR=${EDITOR:-/usr/bin/vim}
+TERMINAL=${TERMINAL:-/usr/bin/alacritty}
+# add options for your terminal. Remember to add the last option to execute
+# your editor program, otherwise the script will fail.
+# see example in the addnote function
+TERM_OPTS="--class notes --title notes -e "
+# Setting PAGER here overrides whatever is set in your default shell
+# comment this option to use your default pager if set in your shell.
+PAGER=${PAGER:-/usr/bin/more}
+
+# set this to true to have output in plain text
+# or use the -p option on the command line before every other option
+PLAIN=false
+# base directory for program files
+BASEDIR=${BASEDIR:-~/.local/share/bash-notes}
+# notes database in json format
+DB=${BASEDIR}/db.json
+# directory containing the actual notes
+NOTESDIR=${BASEDIR}/notes
+```
+
+Most are pretty self explanatory, the only one that might need clarification is `TERM_OPTS` which is used to set the terminal window that will run the editor while writing the note.
+
+Special attention is needed when specifying the options, in my case, using [alacritty](https://github.com/alacritty/alacritty), the option that allows to run some software in the newly created window is `-e`, so I need to specify this as the last option.
+
+### Functionalities
+
+bash-notes can:
+
+ * write a new note `--add="Your note title"` or in short `-a"Your note title"`
+
+ * modify an existing note `--edit=[note ID]`, short version `-e[note ID]`
+
+ * delete a note `--delete=[note ID]`, or `-d[note ID]`
+
+ * delete all notes `--delete=all`, or `-dall`
+
+ * list existing notes `--list` or `-l` in short
+
+ * display a note `--show=[note ID]`, or `-s[note ID]`.
+
+ It's also possible to simply pass [note ID] as an argument to the script and the corresponding note will be displayed.
+
+ ```bash
+ notes.sh 1
+ ```
+
+The *note id* is assigned when the note is created, and that's how you refer to the note in the program.
+
+##### Plain listing vs "colorful"
+
+The `--plain` or `-p` option in short, dictates how the output from the script is formatted, here's a sample listing of all the notes:
+
+```bash
+notes.sh -l
+listing all notes
+
+[ID] [TITLE] [CREATED]
+[1] ciao nota 25/03/2023 18:53 +0100CET
+[2] hello there 25/03/2023 19:02 +0100CET
+```
+
+And here's the same listing with the plain option:
+
+```bash
+notes.sh -pl
+1 - ciao nota - 25/03/2023 18:53 +0100CET
+2 - hello there - 25/03/2023 19:02 +0100CET
+```
+
+It's just a proof of concept at the moment, but the idea is to use a more interesting output maybe using markup, and strip it down in plain mode. After all is still a work in progress.
+The plain option must precede all other options or it won't work. I'll try and fix this behavior in the future.
+
+I'd love to implement some kind of searching functionality, but I'll have to look into that.
+
+##### Backups
+
+Since version 0.3, this script can also handle backups of all your notes, you can specify a backup folder with
+
+```bash
+notes.sh --backup=/some/dir
+```
+
+and the script will create the directory if it doesn't exists and backup all your data, including the rc file if you made one.
+
+If you want to restore a backup you can do so with
+
+```bash
+notes.sh --restore=/some/dir
+```
+
+And the script will take care of putting everything back where it belongs.
+
+> ##### A bit of a warning on restoring backups
+>
+> *Keep in mind that all your existing notes will be overwritten in the process.*
+
+### Installing
+
+Simply copy the script in your $PATH and make it executable, something like this should work:
+
+```bash
+mv notes.sh ~/bin/
+chmod 755 ~/bin/notes.sh
+```
+
+Adapt to your needs as you see fit.
+
+The first time you run the script it will take care of creating all the files and folders it needs in the standard directories.
+
+### Debugging
+
+If the script doesn't work for you for some reasons, you can turn on debugging by running the script like this:
+
+```bash
+DEBUG=true notes.sh [options]
+```
+
+And then you'll be able to check all that happened in the log file at `/tmp/debug_bash-notes.log`
+
+### Vision
+
+Ok, maybe vision is a bit of a stretch, but I've written this script to use it in my daily workflow with [rofi](https://github.com/davatorium/rofi) and [i3wm](https://github.com/i3/i3). I'll adapt the way it works to better suit this need of mine.
+
+There are of course things I'd love to add, but my main goal is for it to work the way I planned to use it.
+
+### TO DO
+
+* add a way to search the notes
+* ~~add a way to display a note without running vim~~ *(done in version 0.3)*
+* markdown support?
+ * maybe implement an export feature that builds the html or pdf file from the note
+ (pandoc??)
+* write a bash completion script to enable autocomplete in the shell
+* other ideas may come [...]
+
+### Contributing
+
+It'd mean so much to receive some feedback, patches if you feel like contributing, I'm not expecting much as this is a personal project, but feel free to interact as much as you want.
+
+### ChangeLog
+
+ * v0.3 - backups management. Some UX improvements
+ * create and restore backups of all your notes and settings.
+ * display notes using predefined PAGER variable or define your own program to use.
+
+ * v0.2 - debugging implemented
+ - you can now generate a debug log in case something doesn't work
+ * v0.1 - first public upload
+ - all major functionalities are present and working
+
+### Mantainer
+
+ * [danix](https://danix.xyz) - it's just me, really...
+
+### LICENSE
+
+> bash-notes © 2023 by danix is licensed under CC BY-NC 4.0. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc/4.0/
\ No newline at end of file
type = "tech"
date = "2021-05-01T17:51:58+00:00"
excerpt = ""
-image = "PXL_20210501_114542849.jpg"
+image = "/uppies/2021/05/PXL_20210501_114542849.jpg"
categories = ["3D Printing", "diy"]
tags = ["3D printing", "cad", "cura", "fusion360", "slicer", "solvespace"]
--- /dev/null
++++
+title = "Ceasar quote"
+author = "Danilo M."
+type = "life"
+date = "2011-07-28T19:03:39+00:00"
+excerpt = "A quote from Julius Caesar"
+categories = ["blogging"]
+tags = ["Caesar", "quote"]
+format = "quote"
++++
+{{< quote source="Julius Caesar" >}}
+What we wish, we readily believe, and what we ourselves think, we imagine others think also.
+{{< /quote >}}
\ No newline at end of file
--- /dev/null
++++
+title = "Come Funziona Questo Sito"
+date = "2024-11-12T11:12:25+01:00"
+draft = true
+type = "life"
+author = "danilo 'danix' m."
+excerpt = "Questo sito è sviluppato con HUGO, ecco come funziona."
+categories = ["blogging", "diy", "hugo", "code"]
+tags = ["web", "development"]
+typora-root-url = "../../static"
++++
+
+Questo sito è sviluppato con HUGO, un framework per costruire siti "statici".
+
--- /dev/null
++++
+title = "conquista la folla.."
+author = "Danilo M."
+type = "life"
+draft = true
+date = "2013-04-21T08:17:11+00:00"
+categories = ["blogging"]
+tags = ["gladiator", "massimo decimo meridio"]
+format = "quote"
++++
+{{< quote source="Massimo X Meridio" >}}
+conquisterò la folla… gli darò qualcosa che non ha mai visto prima
+{{< /quote >}}
\ No newline at end of file
--- /dev/null
++++
+title = "convertire file video in mp3"
+author = "Danilo M."
+type = "life"
+date = "2012-05-25T15:42:02+00:00"
+excerpt = "a simple way to convert from a video file to an mp3"
+categories = ["code", "diy", "linux"]
+tags = ["audio", "convert", "mp3", "video"]
++++
+un piccolo appunto su come convertire velocemente un video in mp3..
+
+```bash
+ffmpeg -i file_da_convertire.flv -f mp3 -ab 192000 -vn nuovo_file.mp3
+```
+
+ovviamente bisogna avere ffmpeg installato nel sistema, le opzioni che abbiamo passato sulla riga sono:
+
+ * `-i`: file di input
+ * `-f`: formato di output
+ * `-ab`: bitrate del file mp3
+ * `-vn`: non catturare il video
+
+Semplice e veloce, provare per credere.. ;) e ovviamente se usate questo comando o lo migliorate in qualche modo fatemelo sapere nei commenti..
\ No newline at end of file
author = "Danilo M."
type = "tech"
date = "2016-01-25T12:41:06+00:00"
-image = "G0092546.jpg"
+image = "/uppies/2016/01/G0092546.jpg"
categories = ["code", "diy", "fotografia"]
tags = ["bash", "convert", "gif", "imagemagik", "mogrify", "script"]
+++
--- /dev/null
++++
+title = "Git – how to setup your own server pt 2"
+author = "Danilo M."
+type = "life"
+date = "2018-12-17T07:39:08+00:00"
+excerpt = "followup on my previous article regarding GIT and how to automatically deploy python flask scripts to serve a web app with apache."
+draft = true
+image = "/uppies/2018/12/gitout.jpg"
+categories = ["blogging", "code", "diy", "linux"]
+tags = ["automation", "do it yourself", "flask", "git", "howto", "python", "ssh"]
++++
+This is a followup on [my previous article about how to setup your server][1] to handle a GIT repository and deploy to a web server like apache.
+
+Since I started experimenting with python and web publishing with it I wanted a way to push all the changes to my codebase directly to a web server, in a similar way as to what I already do with php and apache.<figure class="wp-block-pullquote" style="border-color:#abb8c3">
+
+<blockquote class="has-text-color has-very-dark-gray-color">
+ <p>
+ I want to do it myself, the way I like it..
+ </p>
+
+ <cite>danix</cite>
+</blockquote></figure>
+
+Serving python scripts is slightly different than serving html or php, here’s a scheme that shows what happens when using python (flask in this example) to serve some web content.
+
+
+<div class="wp-block-image">
+ <figure class="aligncenter"><img loading="lazy" width="1024" height="393" src="https://danix.xyz/wp-content/uploads/2018/12/flask-scheme-1024x393.png" alt="" class="wp-image-3852" srcset="https://danix.xyz/wp-content/uploads/2018/12/flask-scheme-1024x393.png 1024w, https://danix.xyz/wp-content/uploads/2018/12/flask-scheme-300x115.png 300w, https://danix.xyz/wp-content/uploads/2018/12/flask-scheme-768x294.png 768w, https://danix.xyz/wp-content/uploads/2018/12/flask-scheme.png 1200w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption>a simple scheme of how python scripts are served on the web.</figcaption></figure>
+</div>
+
+As you can see the web server is acting as a reverse proxy to the [WSGI][2] server Gunicorn, Apache receives a request from a client, forwards the request to Gunicorn which in turn asks the python web service, in our case our flask web app. Other than as a reverse proxy, apache is used also to serve static content which is not originated in python, like images, css or js scripts.
+
+In order to deploy a python web app I had to install the mod_wsgi extension for apache, then I decided to use a folder in my system to install the virtual environment for python to run my web app and point to that directory in my vhost configuration file inside apache. After that I created a directory where to store all files for my web app and instructed apache to serve them using the virtualenv I created earlier. This is more or less what I did:
+
+<pre class="wp-block-preformatted"># create the virtual environment for python inside<br /># the folder /usr/local/virtualenvs/my-app:<br />virtualenv /usr/local/virtualenvs/my-app<br /><br /># now create the directory inside the apache root<br /># to store our web app<br />mkdir /var/www/htdocs/my-app<br /></pre>
+
+Now if we put all the py files for our flask web app we can run it inside apache, this is the configuration for the vhost I used:
+
+<pre class="wp-block-preformatted"><VirtualHost *:80><br /><code> ServerName my-app.mysite.ext</code><br /><code> ErrorLog "/var/log/httpd/my-app.error_log"</code><br /><code> CustomLog "/var/log/httpd/my-app.access_log" common</code><br /><code> WSGIDaemonProcess my-app user=apache group=apache threads=5 python-home=/usr/local/virtualenvs/my-app</code><br /><code> WSGIScriptAlias / /var/www/htdocs/my-app/my-app.wsgi</code><br /><code> WSGIProcessGroup my-app</code><br /><code> Alias "/static/" "/var/www/htdocs/my-app/static/"</code><br /><code> <Directory "/var/www/htdocs/my-app/static/"></code><br /><code> Order allow,deny</code><br /><code> Allow from all</code><br /><code> </Directory></code><br /><code> <Directory "/var/www/htdocs/my-app/"></code><br /><code> Require all granted</code><br /><code> </Directory></code><br /></VirtualHost><br /><br /></pre>
+
+With this setting I can now reach my web app and test it after restarting the web server.
+
+ [1]: https://danix.xyz/2018/07/git-setup-own-server/
+ [2]: https://en.wikipedia.org/wiki/Web_Server_Gateway_Interface
\ No newline at end of file
--- /dev/null
++++
+title = "Git Setup Your Own Server"
+date = "2021-06-13T12:07:49+02:00"
+type = "life"
+author = "danix"
+excerpt = "I'll show you how to setup your own git server easily"
+image = "/uppies/2021/06/gitout.jpg"
+tags = ["git", "server", "setup", "howto", "do it yourself", "ssh"]
+categories = ["code", "diy", "linux"]
++++
+
+Hello everyone,
+
+I recently decided to move all my code under GIT, I've used it before and I've used also SVN, but I find GIT to be more straightforward in some aspects.
+
+In order to use git I needed a place online where to store my projects, and I thought that github could be a good place, but the fact that you have to pay to keep a project private just didn't sound right in my opinion. Of course github is there to make money (specially now that M$ bought it), but I prefer to have a simpler setup and be able to do things my way as much as possible.
+
+So I started planning what I wanted my git server to have. Here's a list:
+
+ * **Security** - I decided to make it work only under ssh, that way only someone who has the key can clone or access the repository. I also added an unprivileged git user that has only access to very few commands, so even if somebody manages to access through ssh he'll find himrself with only very few options available.
+ * {{< strike >}}**Notifications** - my server already tells me a lot of what happens, so I wanted my git service to do the same. I implemented a mail service that notifies me every time a new repository is added or everytime there's a push to a repository.{{< /strike >}}
+ * **Automation** - I wanted to have less steps possible between creation of the project and deployment to production. Now in two steps I can create a repository and clone it to my local computer, and when I'm done I just need to push my modifications and the code is deployed {{< em >}}automatically{{< /em >}}.
+ * **Visibility** - I haven't yet decided if I want my code to be visible, so I haven't even started thinking about this possibility.
+
+<!--more-->
+
+## Installation
+
+Installing a git server is quite simple once you know how it works, on my server it was a matter of having a bare repository setup but in order to have the level of security that I wanted there were a few steps involved.
+
+> A bit of a disclaimer here, I use a Slackware64-14.2 on my server and Slackware64-current on my laptop, so all the commands here worked for me but I can't be sure if the procedures that I followed will work on different distros with different setups. If you have any trouble following what I've done let me know in the comments and I'll try to help you.
+
+I've added a new user and group to my server but before doing so I added /usr/bin/git-shell to /etc/shells in order to use it as login shell for my git user.
+
+{{< highlight bash >}}
+echo "/usr/bin/git-shell" >> /etc/shells
+groupadd git
+mkdir /var/git
+useradd -d /var/git -g git -M -s /usr/bin/git-shell
+{{< /highlight >}}
+
+now the user is all set and ready to be used. Next step will be to create the .ssh directory and the authorized_keys file to hold the keys for the developers that have to access the git server. Here's how I did it:
+
+```bash
+mkdir /var/git/.ssh
+touch /var/git/.ssh/authorized_keys
+chown -R git:git /var/git
+chmod 0700 /var/git/.ssh
+chmod 0600 /var/git/.ssh/authorized_keys
+```
+
+ok, now the files are in place and the permissions are correct for ssh to work well.
+
+Let's head back to my working computer, I created an ssh keypair for my usual user and copied the public key to the authorized_keys file on the server. I won't go into much detail on how to do so, but just a suggestion, keep it without password, it'll be much faster to work later.
+
+Since I have ssh access to the same server for my normal user I used the ~/.ssh/config file on my computer to set a new host that will ease my access routine for the git user as well as my regular user, that's my config (more or less):
+
+```bash
+cat ~/.ssh/config
+Host regular_ssh
+ HostName server.tld
+ User myuser
+ IdentityFile ~/.ssh/id_rsa
+
+Host git_ssh
+ HostName server.tld
+ User git
+ IdentityFile ~/.ssh/git_rsa
+```
+
+Now when I need to access the server with my regular user I'll just run
+
+`ssh regular_ssh`
+
+and when I need to access as git user I'll run
+
+`ssh git_ssh`
+
+and ssh will take care of all the options and start the connection with the correct credentials for me. Neat!
+
+Now that the access for the git user is setup we have one last thing to do before being able to use it. We'll give him only limited commands to use, That way the git user will be even more limited and much more secure. Inside the documentation shipped with git there's a lot of scripts to get you started with this, so we'll copy them inside a special directory called git-shell-commands, like this:
+
+```bash
+cp -R /usr/doc/git-2.14.4/contrib/git-shell-commands /var/git
+chown -R git:git /var/git
+
+```
+
+Now we have 2 commands inside the git-shell-commands directory, list and help, the first will show all projects inside the /var/git directory and the other will show a simple help text and a list of all the commands available. Now to give you an example of how easy it is to add commands to the git-shell I will create a simple command that acts as the clear command, it will clean the screen, to do so, from inside the /var/git directory I did:
+
+```bash
+echo $(which clear) > git-shell-commands/clear
+chmod 0755 git-shell-commands/clear
+
+```
+
+and now I have a "clear" command available for my git user. Another useful command will be "create" to add a repository and a "destroy" to remove it. Let's see them in the next page.
+
+<!--nextpage-->
+
+Let's focus on the two most important scripts for our git server, the **create** and the **delete** script:
+
+### create
+
+{{< highlight bash "linenos=table" >}}
+#! /bin/bash
+
+# usage: create <PROJECT> - create a git bare repository named PROJECT.git
+# this command will setup the repo and send a mail for confirmation.
+
+GITDIR="/var/git"
+MULTIMAIL="/usr/doc/git-2.14.4/contrib/hooks/multimail/git_multimail.py"
+GITUSER="git"
+GITGRP="git"
+
+function is_bare() {
+ repodir=$1
+ if "$(git --git-dir="$repodir" rev-parse --is-bare-repository)" = true
+ then
+ true
+ else
+ false
+ fi
+}
+
+function git_init() {
+ PROJECT=$1
+ echo "creating project \"${PROJECT}.git\""
+ if [ ! -d ${GITDIR}/${PROJECT}.git ]; then
+ mkdir ${GITDIR}/${PROJECT}.git
+ fi
+ cd ${GITDIR}/${PROJECT}.git
+ git init --bare
+ mkdir custom-hooks
+ ln -s $MULTIMAIL custom-hooks/
+ touch hooks/post-receive
+ cat > hooks/post-receive <<EOPR
+#!/bin/sh
+/usr/bin/pee ${GITDIR}/${PROJECT}.git/custom-hooks/deploy.sh \
+ ${GITDIR}/${PROJECT}.git/custom-hooks/git_multimail.py
+
+EOPR
+ cat >> config <<EOT
+
+[multimailhook]
+ mailer = "sendmail"
+ refchangeShowGraph = true
+ mailingList = "receiver@someemail.tld"
+ commitEmailFormat = "html"
+ htmlInIntro = true
+ htmlInFooter = true
+ from = "sender@someemail.tld"
+ administrator = "admin@someemail.tld"
+ quiet = true
+ logFile = "/var/log/multimail.log"
+ errorLogFile = "/var/log/multimail_err.log"
+EOT
+ touch custom-hooks/deploy.sh
+ cat > custom-hooks/deploy.sh <<EODP
+#!/bin/bash
+# Directory where to deploy files from repository
+DPTARGET=""
+# Directory containing repository
+DPGIT_DIR="${GITDIR}/${PROJECT}.git"
+# Branch that is going to be deployed to server
+DPBRANCH="master"
+
+while read oldrev newrev ref
+do
+ # if DPTARGET is empty we don't want deploy for this project
+ if [[ ! "" == \$DPTARGET ]]; then
+ # let's check that we are deploying to the correct branch
+ if [[ \$ref = refs/heads/\${DPBRANCH} ]]; then
+ echo "Ref \$ref received. Deploying \${DPBRANCH} branch to production..."
+ git --work-tree=\$DPTARGET --git-dir=\$DPGIT_DIR checkout -f $DPBRANCH
+ NOW=\$(date +"%d%m%Y-%H%M")
+ git tag release_\$NOW \$DPBRANCH
+ echo " /==============================="
+ echo " | DEPLOYMENT COMPLETED"
+ echo " | Target branch: \$DPTARGET"
+ echo " | Target folder: \$DPGIT_DIR"
+ echo " | Tag name : release_\$NOW"
+ echo " \=============================="
+ else
+ echo "Ref \$ref received. Doing nothing: only the \${DPBRANCH} branch may be deployed on this server."
+ fi
+ else
+ echo "Target directory not declared. Skipping deploy to server."
+ fi
+done
+
+EODP
+ chmod 0755 hooks/post-receive custom-hooks/deploy.sh
+ cd ${GITDIR}/
+ chown -R ${GITUSER}:${GITGRP} ${GITDIR}/${PROJECT}.git
+ echo "All done, you can now work on \"${PROJECT}.git\""
+ exit 0
+}
+
+if [ ! -z $1 ]; then
+ PROJECT=$1
+else
+ read -p 'Project name: ' PROJECT
+fi
+
+if [ ! -d ${GITDIR}/${PROJECT}.git ]; then
+ git_init $PROJECT
+else
+ echo "Project directory ${PROJECT}.git already exists."
+ if [ $(ls -A ${GITDIR}/${PROJECT}.git) ]; then
+ if is_bare ${GITDIR}/${PROJECT}.git
+ then
+ echo "looks like \"${PROJECT}.git\" is an existing git project directory, choose another name."
+ exit 171
+ else
+ echo "\"${PROJECT}.git\" is not empty, I can't create a Git Project in it. Choose another name."
+ exit 172
+ fi
+ else
+ echo "\"${PROJECT}.git\" is an empty directory. Do you want to initialize a Git Project here? [y/N]"
+ read answer
+ case $answer in
+ Y|y)
+ git_init $PROJECT
+ ;;
+ N|n)
+ echo "Aborting due to user request."
+ exit 173
+ ;;
+ *)
+ # we assume no as default answer.
+ echo "you said \"$answer\" which I don't understand, so to me is no. Aborting."
+ exit 177
+ ;;
+ esac
+ fi
+fi
+{{< /highlight >}}
+
+This is the create script, as you can see it's a bit complex because it will do a few things for me:
+
+ * create the bare repository using the argument provided on the command line or asking for a project name
+ * check before creating the repo, if another repo with the same name exists or if a directory with files in it exists. That way I'll make sure to only create a repo inside an empty directory.
+ * add a custom-hooks directory that will hold a link to the multimail.py script as well as my deploy.sh script
+ * create a post-receive script that uses **pee** from the [moreutils][1] project to run multiple scripts at the same hook.
+ * ensure sane permissions on the whole project directory.
+ * always assume no (the safest option) when asking the user about the action to take.
+
+So after saving this script as create inside the git-shell-commands directory, we'll give it executable permissions and we can move to the delete script.
+
+{{< highlight bash >}}
+cat create-bare-repo.sh > /var/git/git-shell-commands/create
+chown git:git -R /var/git/git-shell-commands
+chmod 0755 /var/git/git-shell-commands/create
+{{< /highlight >}}
+
+### delete
+
+Let's see the delete script:
+
+{{< highlight bash "linenos=table" >}}
+#! /bin/bash
+
+# usage: delete <REPOSITORY> - PERMANENTLY delete a repository if existing.
+# CAREFUL, this action cannot be undone. This command will ask for confirmation.
+
+GITDIR="/var/git"
+
+function is_bare() {
+ repodir=$1
+ if "$(git --git-dir="$repodir" rev-parse --is-bare-repository)" = true
+ then
+ true
+ else
+ false
+ fi
+}
+
+if [ ! -z $1 ]; then
+ PROJECT=$1
+else
+ read -p 'Project to delete: ' PROJECT
+fi
+
+if [ -d ${GITDIR}/${PROJECT}.git ]; then
+ if [[ $(ls -A ${GITDIR}/${PROJECT}.git) ]]; then
+ if is_bare ${GITDIR}/${PROJECT}.git
+ then
+ echo "You are going to delete the git repository \"${PROJECT}.git\" Do you really want to continue? Note, this action cannot be reverted. [y/N]"
+ read delAnswer
+ case $delAnswer in
+ Y|y)
+ rm -rf ${PROJECT}.git
+ ;;
+ N|n)
+ echo "Aborting due to user request."
+ exit 173
+ ;;
+ *)
+ echo "you said \"$delAnswer\" which I don't understand. Assuming No. Aborting."
+ exit 177
+ ;;
+ esac
+ else
+ echo "\"${PROJECT}.git\" doesn't look like a git repository. Check with your System Administrator."
+ exit 177
+ fi
+ else
+ echo "\"${PROJECT}.git\" is an empty directory, Skipping. Check with your System Administrator."
+ exit 177
+ fi
+fi
+{{< /highlight >}}
+
+This script is much simpler than the previous one, it'll accept the name of the project as argument on the command line or will ask for it and will only delete it if it is a proper git repository, otherwise it will just exit with an error code.
+
+I improved the way those scripts recognise a git repository from simply relying on the fact that there's a HEAD file inside the directory they're checking, which wasn't the best option, to using git itself to check if the directory is a bare repository. Much better!!
+
+Since we are here let's modify the help command to make it show a short description of every available command.
+
+{{< highlight bash "linenos=table" >}}
+#!/bin/sh
+
+# usage: help - Lists all the available commands
+# help <command> - Detailled explanation of how "command" works
+
+if tty -s
+then
+ HELPTEXT="Hi $USER, Run 'help' for help, 'help <command>' for specific help on a command, run 'exit' to exit. Available commands:"
+else
+ HELPTEXT="Hi $USER, Run 'help' for help, 'help <command>' for specific help on a command. Available commands:"
+fi
+
+cd "$(dirname "$0")"
+
+if [[ ! -z $1 ]]; then
+ cmd=$1
+ if [[ -f $cmd && -x $cmd ]]; then
+ awk 'NR>=3&&NR<=4' $cmd | cut -c 3-
+ else
+ echo "command \"$cmd\" doesn't exists"
+ fi
+else
+ echo $HELPTEXT
+ for cmd in *
+ do
+ case "$cmd" in
+ help) ;;
+ *) [ -f "$cmd" ] && [ -x "$cmd" ] && echo "$cmd" ;;
+ esac
+ done
+fi
+{{< /highlight >}}
+
+The main thing I added is the support for a command line argument, now I'm able to run it by itself and display the usual output with a list of available commands, or followed by a command name to give a brief explanation like this:
+
+{{< highlight bash >}}
+git> help
+Hi git, Run 'help' for help, 'help <command>' for specific help on a command, run 'exit' to exit. Available commands:
+clear
+create
+delete
+list
+git> help create
+usage: create - create a git bare repository named PROJECT.git
+ this command will setup the repo and send a mail for confirmation.
+git>
+{{< /highlight >}}
+
+Pretty nice isn't it?! Now it's much more user friendly, and to show the description I used awk and cut to parse the comment at the top of every script I have in the `git-shell-commands` directory.
+
+In the next page we'll see the usual routine I follow when working with this new setup.
+
+<!--nextpage-->
+
+## My GIT Routine
+
+Let's say I had a new idea for a WordPress plugin, I can't wait to start writing, so the setup of the GIT environment should be as fast as possible. That's where my setup will come in handy. Let's open the terminal, I'll go inside my testing directory and from there I'll run:
+
+{{< highlight bash >}}ssh git_ssh 'create awesomePlugin'
+creating project "awesomePlugin.git"
+Initialized empty Git repository in /var/git/awesomePlugin.git/
+All done, you can now work on "awesomePlugin.git"
+{{< /highlight >}}
+
+The project is created, now I just need to clone it
+
+{{< highlight bash >}}git clone ssh://git_ssh:/var/git/awesomePLugin.git
+Cloning into 'awesomePlugin'...
+warning: Looks like you cloned an empty repository.
+{{< /highlight >}}
+
+And that's it, I now have a local and a remote copy of my git repository ready to work with.
+
+Let's say I'm working on this plugin and I get to the point where I feel like I can use it on my own blog, I want the deploy to be as fast as the rest of the process was, so I'll ssh as my normal user and modify the `deploy.sh` script inside the `custom-hooks` directory for this project to add the working directory and the branch I want to use for deploy (you can use master, but it's better to use a different branch only for this pourpose, this way you can keep the production code stable and use master for experimenting until ready to deploy)
+
+Inside the deploy.sh script I'll edit those 2 lines:
+
+{{< highlight bash >}}# Directory where to deploy files from repository
+DPTARGET=""
+# Branch that is going to be deployed to server
+DPBRANCH="master"
+{{< /highlight >}}
+
+adding `/var/www/wp-content/plugins/awesomePlugin` as `DPTARGET` and production as `DPBRANCH`.
+
+now on my local system I'll add a new branch and use that before committing my stable code.
+
+{{< highlight bash >}}git checkout -b production
+Switched to a new branch 'production'
+
+git add .
+
+git commit -m "awesomePlugin is even more awesome"
+[production (root-commit) a3885a4] awesomePlugin is even more awesome
+ 1 file changed, 1 insertion(+)
+ create mode 100644 awesomePlugin.php
+
+git push origin production
+Counting objects: 3, done.
+Writing objects: 100% (3/3), 240 bytes | 240.00 KiB/s, done.
+Total 3 (delta 0), reused 0 (delta 0)
+remote: Ref refs/heads/production received. Deploying production branch to production...
+remote: /===============================
+remote: | DEPLOYMENT COMPLETED
+remote: | Target branch: /var/www/htdocs/wp-content/plugins/awesomePlugin
+remote: | Target folder: /var/git/awesomePlugin.git
+remote: | Tag name : release_12072018-1110
+remote: \==============================
+To ssh://git_ssh:/var/git/awesomePlugin.git
+ * [new branch] production -> production
+{{< /highlight >}}
+
+And that's it, now my new plugin is ready to go live as soon as I activate it inside my WordPress admin area.
+
+## Conclusion
+
+That's it for now, I'll add to this post as soon as I decide whether I want my code to be visible or not, but for now this is my setup and it's working greatly for me so far.
+
+If you made it this far I hope you'll spend a couple more minutes to let me know what you think about this setup, if you use something similar or if you had any problems setting this up, I'll try and help you as much as I can of course.
+
+[1]: https://joeyh.name/code/moreutils/
--- /dev/null
++++
+title = "haiku"
+author = "Danilo M."
+type = "life"
+date = "2011-01-09T23:15:01+00:00"
+excerpt = "an haiku I wrote."
+categories = ["blogging"]
+tags = ["haiku", "loneliness", "love", "quotes"]
+format = "quote"
++++
+{{< quote source="yours truly" >}}
+il suo profumo.<br />
+il piacere dei sensi.<br />
+fine di un sogno.
+{{< /quote >}}
--- /dev/null
++++
+title = "haiku"
+author = "Danilo M."
+type = "life"
+date = "2010-12-02T10:33:50+00:00"
+excerpt = "An haiku by Jack Kerouac."
+categories = ["blogging"]
+tags = ["haiku", "quotes"]
+format = "quote"
++++
+
+{{< quote source="Jack Kerouac" >}}
+Gli uccelli cantano<br />
+nel buio.<br />
+Alba piovosa.
+{{< /quote >}}
\ No newline at end of file
--- /dev/null
++++
+title = "Imagine."
+author = "Danilo M."
+type = "life"
+date = "2015-01-11T01:38:25+00:00"
+image = "/uppies/2015/01/imagine_colors.jpg"
+categories = ["freedom", "musica"]
+tags = ["imagine", "john lennon"]
+format = "image"
++++
+{{< figure class="align-center" src="https://danix.xyz/wp-content/uploads/2020/10/imagine_colors.jpg" />}}
+
+via [http://www.filmsforaction.org/articles/john-lennons-imagine-made-into-a-comic-strip/](http://www.filmsforaction.org/articles/john-lennons-imagine-made-into-a-comic-strip/)
+
--- /dev/null
++++
+title = "Mario Congiusta candidato al Consiglio Regionale calabrese"
+author = "Danilo M."
+type = "life"
+date = "2010-03-05T09:17:55+00:00"
+excerpt = "voglio segnalarvi la candidatura di Mario Congiusta alle prossime Elezioni per il Consiglio Regionale Calabrese."
+categories = ["blogging", "freedom", "itaglia"]
+tags = ["calabria", "candidato", "congiusta", "consiglio", "elezioni", "incensurato", "libertà di stampa", "mario", "regionale"]
++++
+Vi voglio segnalare un avvenimento molto importante per me. Premesso che io non mi interesso molto di politica, mi guardo intorno e mi rendo conto che la situazione in Calabria e in Italia sta cadendo vertiginosamente in un baratro senza fondo.
+
+La corruzione c'è sempre stata, ma ultimamente la nostra politica sembra diretta sempre più verso un'idea totalitaria, verso un futuro che non voglio nemmeno immaginare. Chi è al potere cerca di accentrare sempre più potere su se stesso, non esistono più schieramenti, tutti le parti politiche collaborano tra loro di nascosto, si scambiano favori in modo da ottenerne altri, e tutto questo uccide la democrazia, tutto questo uccide la voce che il popolo ha in merito alle questioni dello Stato.
+
+<!--more-->
+
+Io non mi occupo di politica dicevo, però sento che intorno a noi c'è bisogno di maggiore chiarezza, c'è bisogno di trasparenza, io voglio poter dire che le persone che ricoprono una qualsiasi carica pubblica, o che aspirano a ricoprirla, sono persone oneste, sono persone che aspirano a quella carica **per esprimere le proprie idee**, non per guadagnare di più. Io voglio partecipare ai concorsi pubblici senza dovermi preoccupare del fatto che ci saranno persone sleali che otterranno risultati migliori dei miei perchè “spinti” da questo o quel potente. :vangry:
+
+Mi rendo conto che queste potrebbero sembrare considerazioni utopistiche, ma se non miriamo ad un traguardo più alto, più nobile, stiamo solo facendo un favore a chi è già al potere, **se continueremo a giocare secondo le loro regole, non potremo mai vincere**.
+
+Per questo voglio segnalarvi la **candidatura di Mario Congiusta** alle prossime Elezioni per il Consiglio Regionale Calabrese.
+
+E' di persone come Mario che la Calabria, l'Italia intera ha bisogno in questo momento.
+
+Bisogna partire da persone come Mario Congiusta perchè l'onestà e la trasparenza delle cariche politiche non dev'essere un valore aggiunto, l'onestà deve essere la norma, i valori aggiunti di un politico sono le idee ed in base a quelle i politici vanno confrontati.
+
+Come ho detto, non mi occupo di politica, però sono un accanito sostenitore dell'onestà, dalle piccole cose a quelle più importanti, e spero un giorno di poter vivere in uno Stato democratico che non sia tale soltanto a parole ma che assicuri ai suoi cittadini una pacifica convivenza, senza sotterfugi...
+
+Voi la chiamerete utopia, io la chiamo **speranza**.
\ No newline at end of file
--- /dev/null
++++
+title = "Katsushika Hokusai"
+author = "Danilo M."
+type = "life"
+date = "2011-07-27T20:35:16+00:00"
+excerpt = "'A few images by japanese artist Katsushika Hokusai (1760-1849), author of the famous series of 36 pictures portraying Mt. Fuji '"
+image = "/uppies/2011/07/The-Great-Wave-Off-Kanagawa-1823-large.jpg"
+categories = ["art", "blogging"]
+tags = ["great wave", "hokusai", "katsushika", "mt fuji", "paintings"]
+format = "gallery"
++++
+I just wanted to share a few images by one of my favourite artists with you.
+
+{{< quote source="katsushikahokusai.org" src="http://www.katsushikahokusai.org/" >}}
+**Katsushika Hokusai** (葛飾北斎, Katsushika Hokusai 1760–May 10, 1849) was a Japanese artist, ukiyo-e painter and printmaker of the Edo period. In his time he was Japan&'s leading expert on Chinese painting. Born in Edo (now Tokyo), Hokusai is best-known as author of the woodblock print series Thirty-six Views of Mount Fuji (c. 1831) which includes the iconic and internationally recognized print, The Great Wave off Kanagawa, created during the 1820s. Hokusai created the "Thirty-Six Views" both as a response to a domestic travel boom and as part of a personal obsession with Mount Fuji. It was this series, specifically The Great Wave print and Fuji in Clear Weather, that secured Hokusai’s fame both within Japan and overseas. As historian Richard Lane concludes, “Indeed, if there is one work that made Hokusai&'s name, both in Japan and abroad, it must be this monumental print-series...” While Hokusai&'s work prior to this series is certainly important, it was not until this series that he gained broad recognition and left a lasting impact on the art world. It was The Great Wave print that initially received, and continues to receive, acclaim and popularity in the Western world.
+{{< /quote >}}
+
+Enjoy.
+
+{{< gallery >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/Boy-on-Mount-Fuji-large.jpg" alt="Boy on Mount Fuji" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/Choshi-in-Shimosa-Province-Soshu-Choshi-large.jpg" alt="Choshi in Shimosa Province" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/Hibiscus-and-Sparrow-large.jpg" alt="Hibiscus and Sparrow" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/Mt.-Fuji-in-the-Sunset-large.jpg" alt="Mt. Fuji in the Sunset" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/Yoro-Waterfall-in-Mino-Province-Mino-no-kuni-Yoro-no-taki-large.jpg" alt="Yoro Waterfall in Mino Province Mino no kuni Yoro no taki" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/White-Shell-Shiragai-large.jpg" alt="White Shell Shiragai" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/Waterfall-where-Yoshitsune-Washed-his-Horse-at-Yoshino-in-Yamato-Province-Washu-Yoshino-Yoshitsune-uma-arai-no-taki-large.jpg" alt="Waterfall where Yoshitsune Washed his Horse at Yoshino in Yamato Province Washu Yoshino Yoshitsune uma arai no taki" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/The-Great-Wave-Off-Kanagawa-1823-large.jpg" alt="The Great Wave Off Kanagawa" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/The-dragon-on-Smoke-Escaping-from-Mt-Fuji-large.jpg" alt="The dragon on Smoke Escaping from Mt Fuji" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/Surimono-Totsuka-large.jpg" alt="Surimono Totsuka" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/South-Wind-at-Clear-Dawn-Gaifu-kaisei-large.jpg" alt="South Wind at Clear Dawn Gaifu kaisei" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/Shower-Below-the-Summit-Sanka-hakuu-large.jpg" alt="Shower Below the Summit Sanka hakuu" >}}
+ {{< gal-img divClass="col-3 gtr-uniform" src="/uploads/2011/07/Plum-Blossom-and-the-Moon-large.jpg" alt="Plum Blossom and the Moon" >}}
+{{< /gallery >}}
+
+I hope you liked them. I'll see you on the next one.
--- /dev/null
++++
+title = "La giornata del pi Greco"
+author = "Danilo M."
+type = "life"
+date = "2010-03-14T11:55:45+00:00"
+excerpt = "Festeggiamo insieme la giornata del pi greco"
+categories = ["Uncategorized"]
+tags = ["celebrazione", "festa", "lerry shawn", "pi greco"]
++++
+Buona giornata del pi Greco a tutti… :D
+
+Dal 1988 si festeggia il 14 Marzo la giornata del pi Greco, la data è stata scelta in base alla scrittura anglosassone di questo giorno, 3.14 che ricorda l’approssimazione per 3 cifre del pi Greco.
+
+<!--more-->
+
+Il primo a festeggiare questa ricorrenza fu il fisico Lerry Shawn che organizzò un corteo circolare attorno ad uno degli edifici dell’[Exploratorium di San Francisco][1] e la vendita di torte alla frutta decorate con le cifre decimali di questo magico numero. In seguito il fisico venne insignito del titolo di **Principe del pi Greco**.
+
+Tutt’oggi nei dipartimenti di matematica di numerose università si organizzano delle feste per celebrare questo numero.
+
+Per maggiori informazioni e qualche altro link interessante vi rimando alla [pagina][2] che wikipedia italia dedica a questo evento.
+
+Happy 3.14 a tutti :D
+
+[1]: http://it.wikipedia.org/wiki/Exploratorium "Exploratorium di San Francisco"
+[2]: http://it.wikipedia.org/wiki/Giorno_di_pi_greco "giorno del pi greco su wikipedia"
\ No newline at end of file
--- /dev/null
++++
+title = "le email queste sconosciute :)"
+author = "Danilo M."
+type = "life"
+date = "2010-11-06T22:28:43+00:00"
+excerpt = "piccoli comportamenti da seguire quando si invia una email."
+draft = true
+categories = ["blogging"]
+tags = ["attachments", "email", "howto", "mistakes", "privacy", "subject"]
++++
+Prendo spunto da un simpatico quanto tristemente reale [articolo pubblicato][1] sul [blog di barbara sgarzi][2], una giornalista che non conoscevo ma che non mancherò di seguire, per parlarvi di un mezzo di comunicazione variamente utilizzato ma purtroppo spesso sottovalutato come le **email**.
+
+<!--more-->
+
+{{< figure src="/uploads/2010/11/email-at1-300x211.gif" class="align-left" />}}
+Già vi immagino, voi fedeli (3) lettori, subito pronti a dire: "_ma cosa vorrai mai insegnarci sulle email che già non sappiamo?_" beh, iniziamo dalla prima cosa che colpisce l'occhio di chi riceve una mail, l'**oggetto**.
+
+Eh già, si chiama oggetto perchè serve a descrivere ciò di cui l'email parla, l'oggetto del messaggio appunto. Non ha quindi senso lasciare il campo in bianco o scrivere cose senza senso tipo "email da tizio:, "comunicazione da sempronio: eccetera, per sapere chi è il mittente dell'email c'è il campo "From: o "Da: oppure indovinate un po', "Mittente:, l'avreste mai detto?! :)
+
+Un'altra cosa piuttosto bruttina da vedere è il corpo del messaggio vuoto con tutto il contenuto relegato negli allegati, se ricevo una mail così non è che mi precipito a leggere l'allegato, piuttosto la cestino direttamente! Gli allegati servono per allegare qualcosa che non si può mettere nel corpo del messaggio, non per contenere il messaggio!
+
+Un altro problema che affligge spesso chi riceve email è l'invio di foto! Su questo punto potremmo spendere fiumi di parole parlando del fatto che al giorno d'oggi con le adsl super veloci che ci ritroviamo non sia più un problema ricevere allegati pesanti, ma non capisco perchè io debba stare a scaricare una foto da 12 megapixel a 300 <acronym title="dot per inches (punti per pollice)">dpi</acronym> se non dovrò nemmeno stamparla, ma al massimo condividerla sul blog o su facebook; perdete un attimino del vostro <span style="text-decoration: line-through">prezioso</span> tempo anche voi e riducete le dimensioni delle foto che inviate, già ridurre la risoluzione da 300 a 72 [dpi][4] aiuterà notevolmente chi dovrà ricevere la mail oltre che farvi risparmiare molto tempo in invio.. Un altro appunto relativo alle dimensioni delle foto, se state mandando una foto di un tenero cucciolo che dovrà fare da sfondo al piccì del vostro/a amato/a, che senso ha che misuri 4000 pixel sul lato corto?! Una risoluzione decente potrebbe essere 1600 pixel sul lato lungo e il lato corto dimensionato in proporzione, in questo modo le dimensioni scenderanno ulteriormente senza che si perda la qualità del vostro pregevolissimo scatto! ;)
+
+{{< figure class="align-right" src="/uploads/2010/11/url-300x197.jpg" />}}
+[5]Il punto successivo di questa carrellata potrebbe avere un titolo e un articolo a se, "_come inviare link. Il modo corretto di condividere i famigerati [URL][6]_"; fin dagli albori di internet si è avvertita infatti la necessità di condividere link interessanti con i nostri contatti, e sopratutto negli ultimi tempi i link sono diventati sempre più lunghi e complessi, cose tipo:
+
+```
+http://www.example.net/test/sample_page.php?variable00=aldsgfqeworslkdf2934523&variable01=abbecceddario&variable02=tomorrow+will+rain#bookmark539
+```
+
+e nonostante io capisca che condividere i link sia fondamentale proprio non riesco a concepire il fatto che chi invia i link non si prenda la briga di controllare che siano quantomeno funzionanti prima di inviare la mail, il copia/incolla è una conquista stupenda, ma perchè fare la figura dei <span style="text-decoration: line-through">pirla</span> (a dir poco) inviando link chilometrici spezzettati in 20 parti che per ricostruirli si impiega più tempo che a leggere il resto della posta, col rischio poi che ci si dimentichi di un minuscolo carattere tipo un punto e il link non funzioni?! Per ovviare a questo tipo di inconvenienti, si può fare più attenzione riguardando la mail prima di inviarla, oppure si può utilizzare uno dei tanti servizi di URL shortening presenti sul web, ~~come ad esempio [uri.danixland.net][7],~~ in questo modo i link diventeranno molto più brevi e semplici da gestire, e si eviteranno tanti problemi per chi legge le email!
+
+Ancora un altro consiglio, **ricontrollate ciò che avete scritto**, no seriamente, consegnereste mai un compito senza averlo nemmeno riguardato? E allora perchè prima di inviare una mail che vi sarà costata probabilmente meno tempo per scriverla, non le date una rilettura veloce?! Sono fantastiche le email con l'oggetto ma senza il testo, o quelle con il testo "_Allegato pronto per la spedizione_: ma senza l'allegato! Suvvia, che ci vuole a soffermarsi un attimo su ciò che si sta facendo?!
+
+Per ultimo mi lascio probabilmente la madre di tutti i comportamenti sbagliati quando si invia un'email, il disrispetto della privacy! di cosa sto parlando?! Avete presente quelle stupende catene di S. Antonio che vanno tanto di moda nei periodi di festa? Quelle con allegate le presentazioni strappalacrime in PowerPoint che "_se non le inoltri a 140 amici entro i prossimi 7 minuti non hai cuore e ti morirà il gatto strozzandosi mentre sta mangiando il pesce rosso e morendo cadrà in testa al cane al quale si spezzerà una gamba e per la tristezza l'uccellino non mangerà più e si lascerà morire?_" Bene, quelle catene sono l'eden degli spammer, ricevere una di quelle email è come ricevere in regalo tutta la lista dei propri amici su facebook moltiplicata per tutti gli amici di ogni singolo amico, a volte sono più lunghe le liste di indirizzi email che il corpo stesso del messaggio.. Questo accade perchè probabilmente non si conosce bene il mezzo di comunicazione che si sta usando, il campo "A:: dovrebbe contenere il destinatario dell'email, e fin qui non ci piove, ma come comportarsi quando ci sono più destinatari? Ecco che ci viene in aiuto il campo "[Bcc:][8]: altrimenti detto "<acronym title="Copia carbone nascosta">Ccn:</acronym>". Questo campo viene utilizzato per inserire i destinatari secondari dell'email e far si che il loro indirizzo non sia visibile ai destinatari principali specificati nel campo "To:; quando ci sono tantissimi destinatari e non tutti si conoscono tra loro, è buona norma evitare che gli indirizzi email siano visibili onde evitare che qualcuno possa accusarvi di violazione della privacy! Io personalmente sono spesso tentato di denunciare i mittenti di email del genere :/
+
+Mi sembra di aver esaurito gli argomenti riguardo le email, mi auguro di ricevere tante comunicazioni da voi, e spero proprio che farete tesoro di ciò che vi ho consigliato, altrimenti potete anche risparmiarvi il tempo di scrivermi, tanto probabilmente non leggerò mai ciò che mi mandate ;)
+
+Vi lascio nuovamente il link da cui ho attinto per scrivere questo articolo, dategli un'occhiata, come anche al resto del blog, è ben scritto e l'ho trovato variamente interessante. [http://uri.danixland.net/e](2)
+
+[1]: http://uri.danixland.net/e "decalogo per gli uffici stampa - blimunda.net"
+[2]: http://uri.danixland.net/d "Il blog di blimunda"
+[3]: /uploads/2010/11/email-at11.gif
+[4]: http://uri.danixland.net/f "punti per pollice - wikipedia"
+[5]: /uploads/2010/11/url1.jpg
+[6]: http://uri.danixland.net/g "uniform resource locator - wikipedia"
+[7]: http://uri.danixland.net "URL shortening made in danixland"
+[8]: http://uri.danixland.net/h "Blind carbon copy - wikipedia"
\ No newline at end of file
--- /dev/null
++++
+title = "Manage your passwords with password-store"
+author = "Danilo M."
+type = "life"
+date = "2021-05-27T15:08:05+00:00"
+excerpt = "Today I'll guide you on how to safely manage all your passwords with password-store"
+image = "/uppies/2021/05/vault-door1.jpg"
+categories = ["android", "blogging", "diy", "linux"]
+tags = ["android", "gnupg", "management", "password", "password-store"]
++++
+Hello everyone,
+
+lately I’ve decided not to use the password manager offered by all major browsers nowadays, but instead try to manage all my passwords using some open source software in order to have a better control over my passwords.
+
+I’ve decided to write this article after reading this <a rel="noreferrer noopener" href="https://alien.slackbook.org/blog/sync-and-share-your-chromium-and-more-browser-data-among-all-your-computers/" target="_blank">blog entry by AlienBob</a> where he speaks of KeepassXC, and since I’ve used it, I wanted to give a valid alternative to some downsides that I’ve stumbled upon while using it.
+
+The first approach I’ve attempted, as I said, was using <a rel="noreferrer noopener" href="https://keepassxc.org/" target="_blank">KeepassXC</a>, quoting their website:
+
+<blockquote class="wp-block-quote">
+ <p>
+ KeePassXC – Cross-Platform Password Manager
+ </p>
+
+ <p>
+ Never forget a password again.<br />Securely store passwords using industry standard encryption, quickly auto-type them into desktop applications, and use our browser extension to log into websites.
+ </p>
+
+ <cite><a rel="noreferrer noopener" style="" href="https://keepassxc.org/" target="_blank">KeepassXC website</a></cite>
+</blockquote>
+
+What I did was install keepassXC on my Slackware64-current, export all my passwords from my main browser, save them as CSV and import them inside keepassXC. Now I have to remember just one password to access my database and I can install the browser integration add-on for chromium (or firefox) to have all my passwords readily available. Neat!!
+
+To share my passwords between my devices, I simply made a private git repository on my server and synced the password database with it. I then went and installed <a rel="noreferrer noopener" href="https://github.com/bpellin/keepassdroid" target="_blank">KeePassDroid</a>, which is an Android implementation of keepassXC.
+
+Since keepassdroid doesn’t sync automatically from a remote server, I had to use git on my phone to pull/push to my remote in order to keep the password database up to date, and even if that’s not a big deal, I wasn’t happy with my password workflow so, while still using this approach, I was looking for alternatives.
+
+<!--more-->
+
+## Meet password-store
+
+I stumbled upon <a rel="noreferrer noopener" href="https://www.passwordstore.org" target="_blank">password-store</a>, which claims to be the standard unix password manager.
+
+The way it works is simple yet brilliant in my opinion, each password is kept secure in a gpg encrypted text file inside a known directory structure, the file itself as well as the directory containing it can have whatever naming convention you want, and everything can be manipulated with standard unix tools (cp, mv, rm, etc.). <acronym title="Keep It Simple, Stupid">KISS</acronym> rule, am I right?!
+
+Here’s how it looks like, standard tree view from the shell:
+
+<pre class="wp-block-code language-bash"><code>.password-store/
+[...]
+├── facebook/
+│ └── facebook-username
+├── twitter/
+│ └── twitter-username
+├── www.instagram.com/
+│ └── instagram-username
+[...]</code></pre>
+
+In this example, facebook is a directory, containing a gpg encrypted text file named “facebook-username”, in that file is written my password for that user on facebook, pretty straightforward.
+
+The beauty of the pass program, is that it also includes git subcommands, so you can use it to sync your password database to a remote. Here’s how it works:
+
+The first thing you want to do is create a remote repository on your git server, there’s a million ways to do so, and it depends on your git provider. If you want to host a git server I have an howto on this site, <a href="https://danix.xyz/2018/07/git-setup-own-server/" data-type="post" data-id="3748">give it a look</a>.
+
+After creating the remote repository, you want to clone it in `~/.password-store`, the default directory where pass will store all your credentials, and to do so you’ll do:
+
+<pre class="wp-block-code language-bash"><code>git clone myserver.com:git-repository ~/.password-store</code></pre>
+
+Assuming you already have a gpg key pair for johndoe@youremailaddress.com, you’ll have to initialize the password repository like this:
+
+<pre class="wp-block-code language-bash"><code>pass init johndoe@youremailaddress.com</code></pre>
+
+Now pass will use the gpg key pair for that email address when encrypting and decrypting your passwords. Since it also understands when the directory is a local clone of a git repository, after initializing with the previous command, it created a commit ready to be pushed, so all you have to do is
+
+<pre class="wp-block-code language-bash"><code>cd ~/.password-store && git push
+# or you can use pass internal git capabilities with:
+pass git push</code></pre>
+
+and your password database will be synced.
+
+From there you can simply invoke pass to see all your passwords, you can search your database, add or remove passwords, modify them etc. For more info you can check the manual where you also have advanced examples on how to use git with pass.
+
+On my android phone I’ve installed the mobile version of <a rel="noreferrer noopener" href="https://play.google.com/store/apps/details?id=dev.msfjarvis.aps" target="_blank">Password Store</a>, I’ve setup my ssh key in order to be able to pull/push from my git remote, and now I have all my passwords syncronized to my mobile as well.
+
+## On the phone
+
+The process for installing password-store on the phone is a bit tricky, but nothing really difficult. The two apps we need are:
+
+ * <a href="https://play.google.com/store/apps/details?id=dev.msfjarvis.aps" target="_blank" rel="noreferrer noopener">Password-store</a>
+ * <a href="https://play.google.com/store/apps/details?id=org.sufficientlysecure.keychain" target="_blank" rel="noreferrer noopener">OpenKeyChain</a>
+
+After installing both those apps, we’ll need to go on our computer and export our public and private gpg keys in order to import them inside OpenKeyChain, to do so we’ll go in the terminal and type away:
+
+<pre class="wp-block-code language-bash"><code>gpg --export-secret-keys --armor johndoe@youremailaddress.com > private.asc
+gpg --export --armor johndoe@youremailaddress.com > public.asc</code></pre>
+
+now we have both our private and public key stored in a file, which we can transfer to the phone and import inside OpenKeyChain. I’ve imported the private key first and then the public one, and while importing the latter, OpenKeyChain confirmed that the key was updated, so both are essentially on the same keypair.
+
+One important note regarding git, depending on how your git repository is setup, you might be needed to import your ssh key inside password-store on your phone in order to access the repository, that’s really easy as the app will ask for your git configuration the first time you open it.
+
+Once you’ve setup your git access, it will ask you to allow OpenKeyChain to manage your gpg key pair whenever you use password-store, and that’s it! You have now your passwords securely stored through GnuPG and synced between your devices with git.
+
+## Bonus note
+
+password-store is a command line program that you can access via it’s command `pass`, but there are also graphical interfaces to access it.
+
+One of them is <a rel="noreferrer noopener" href="https://qtpass.org/" target="_blank">qtpass</a>, you should find it in most distros, on Slackware I found it on <a rel="noreferrer noopener" href="https://slackbuilds.org/repository/14.2/desktop/qtpass/?search=qtpass" target="_blank">SBo</a> and compiled it without any problems. It performs very well, allows you to manipulate your password repository from a graphical interface, performs push/pull operations on git and makes it easier to create complex passwords whenever you need. Just a headsup, if you install this setup on raspbian, remember to install one of the pinentry programs to be able to insert your passkey when you are not in the terminal.
+
+I hope you’ll find this article useful, remember to drop me a [comment][1] if you need any help and I’ll be happy to help you as best as I can.
+
+Cheers!!
+
+[1]: #comment
\ No newline at end of file
--- /dev/null
++++
+title = "Money for indipendence"
+author = "Danilo M."
+type = "life"
+date = "2013-04-30T08:58:25+00:00"
+excerpt = "Quoting Henry Ford"
+categories = ["blogging", "life"]
+tags = ["hope", "indipendence", "money", "quotes"]
+format = "quote"
++++
+{{< quote source="Henry Ford" >}}
+If money is your hope for independence you will never have it.
+{{< /quote >}}
--- /dev/null
++++
+title = "myself as a droid.."
+author = "Danilo M."
+type = "life"
+date = "2011-02-14T13:31:08+00:00"
+draft = true
+categories = ["web"]
+tags = ["android", "droidify", "market"]
+format = "image"
++++
+<figure style="width: 500px" class="wp-caption aligncenter"><img loading="lazy" style="margin-right: auto; margin-left: auto;" src="http://danixland.net/wp-content/uploads/2011/02/wpid-android21.png" alt="image" width="500" height="500" /><figcaption class="wp-caption-text">che ve ne pare? il mio autoritratto in stile android!!</figcaption></figure>
+
+l’ho creato usando [droidify yourself][1], un’app di google per il market di android.. ;-)
+
+ [1]: https://market.android.com/details?id=com.google.android.apps.androidify
\ No newline at end of file
--- /dev/null
++++
+title = "nerdness"
+author = "Danilo M."
+type = "life"
+date = "2011-08-31T09:57:22+00:00"
+excerpt = "We are nerds, Resistance is futile"
+categories = ["blogging"]
+tags = ["john green", "nerds"]
++++
+{{< figure class="align-center" caption="We are nerds. Resistance is futile" >}}
+{{< img src="/uploads/2011/08/nerdslikeus.png" alt="nerds like us" >}}
+{{< /figure >}}
+
+
+via [ipstenu.org][1]
+
+[1]: http://ipstenu.org/blog/2011/nerds-like-us/ "ipstenu's website"
\ No newline at end of file
--- /dev/null
++++
+title = "new home server ideas"
+author = "Danilo M."
+type = "life"
+date = "2019-10-30T13:22:48+00:00"
+image = "/uppies/2019/10/server.jpg"
+excerpt = "Here's a short list of components for what will possibly be my future home server."
+categories = ["diy", "linux"]
+tags = ["build", "flying dutchman", "server"]
++++
+I'm thinking about building a new home server, so I picked some parts I think might work well for what I need to do. Here's the list for future reference:
+
+PCPartPicker Part List: [part list on PCPartPicker][1]
+
+ * **CPU**: AMD Ryzen 3 3200G 3.6 GHz Quad-Core Processor
+ * **CPU Cooler**: Cooler Master MasterLiquid ML240L RGB 66.7 CFM Liquid CPU Cooler
+ * **Thermal Compound**: Thermal Grizzly Kryonaut 1g 1 g Thermal Paste
+ * **Motherboard**: Gigabyte B450 AORUS M Micro ATX AM4 Motherboard
+ * **Memory**: Corsair Vengeance LPX 16 GB (2 x 8 GB) DDR4-3200 Memory
+ * **Case**: Antec VSK10 MicroATX Mid Tower Case
+ * **Power Supply**: EVGA BT 450 W 80+ Bronze Certified ATX Power Supply
+ * **Case Fan**: 2x be quiet! Pure Wings 2 140 PWM 61.2 CFM 140 mm Fan
+
+Total around €445.00 on amazon as suggested by [PCPartPicker][2].
+
+What do you guys think?
+
+[1]: https://it.pcpartpicker.com/user/danixland/saved/r7dQZL
+[2]: https://it.pcpartpicker.com/
\ No newline at end of file
--- /dev/null
++++
+title = "Of Being Lonely"
+date = "2025-10-04T12:50:17+02:00"
+draft = true
+type = "life"
+author = "danilo 'danix' m."
+format = "post"
+excerpt = "How do you deal with the reality of living with yourself?"
+image = "/uppies/2025/10/loneliness.jpg"
+categories = ["life"]
+tags = ["life", "responsibility", "loneliness", "introspection"]
+typora-root-url = "../../static"
++++
+
+How do you deal with the reality of living with yourself?
+
+What does
\ No newline at end of file
--- /dev/null
++++
+title = "outside of the box"
+author = "Danilo M."
+type = "life"
+date = "2011-08-31T08:05:35+00:00"
+excerpt = "'the right thing to do outside of the box.. '"
+image = "/img/default_article.jpg"
+categories = ["blogging", "life"]
+tags = ["quotes", "think outside of the box"]
+format = "quote"
++++
+{{< quote source="Tim Ferriss" >}}
+It isn’t enough to think outside the box. Thinking is passive. Get used to acting outside the box.
+{{< /quote >}}
--- /dev/null
++++
+title = "playing with colors"
+author = "Danilo M."
+type = "life"
+date = "2016-02-14T17:52:21+00:00"
+image = "/uppies/2016/02/palette.jpg"
+categories = ["code", "diy"]
+tags = ["colors", "github", "html5", "palette", "php", "viewer"]
++++
+{{< figure src="https://danix.xyz/wp-content/uploads/2016/02/palette-1.jpg" class="image fit" link="https://github.com/danixland/palette-viewer" caption="palette-viewer on github" />}}
+
+{{< dropcap >}}
+Today I decided I wanted to have a little "old school" fun, so instead of working on some WordPress theme/plugin, I went for the "lemme write some php from scratch" approach.
+{{< /dropcap >}}
+
+I was having a look at some color palettes for _**I'm not gonna tell ya**_, and it was quite hard for me to mix them together in my mind and decide which color goes where and how to use it, so after thinking about it for a while, I decided I'd narrow my options to 6 colors per palette, and in order to better visualize them, I wrote a small php page to help me.
+
+It's actually very simple, there's a large preview where you can modify each color on the fly, and then you can send them to a fake page preview. that's it.
+
+I put it on <a href="https://github.com/danixland/palette-viewer" target="_blank" rel="noopener noreferrer">github</a>, just in case you want to give it a look.
+
+Let me know what you think about it. Cheers ;)
\ No newline at end of file
--- /dev/null
++++
+title = "poker time.."
+author = "Danilo M."
+type = "life"
+date = "2010-12-19T21:07:04+00:00"
+draft = true
+categories = ["fotografia"]
+tags = ["feste", "gioco", "natale", "poker"]
+format = "image"
++++
+<figure style="width: 500px" class="wp-caption aligncenter"><img loading="lazy" style="margin-right: auto;margin-left: auto" src="http://danixland.net/wp-content/uploads/2010/12/wpid-2010-12-19-21.45.121.jpg" alt="image" width="500" height="375" /><figcaption class="wp-caption-text">seratina relax a base di poker.. ovviamente senza soldi veri :-) il modo migliore per passare le serate quando non si ha voglia di uscire..</figcaption></figure>
+
+
\ No newline at end of file
--- /dev/null
++++
+title = "pure nerdgasm"
+author = "Danilo M."
+type = "life"
+date = "2011-10-01T07:28:14+00:00"
+excerpt = "An EPIC video of two floppy disks playing the imperial march.. nerdgasm.."
+image = "/uppies/2011/10/vader.jpg"
+categories = ["blogging", "web"]
+tags = ["floppy disks", "imperial march", "nerdgasm", "nerds", "star wars", "youtube"]
+format = "video"
++++
+<figure class="wp-block-embed-youtube aligncenter wp-block-embed is-type-rich is-provider-embed-handler wp-embed-aspect-4-3 wp-has-aspect-ratio">
+
+<div class="wp-block-embed__wrapper">
+</div><figcaption>can’t get nerdier than this…</figcaption></figure>
\ No newline at end of file
--- /dev/null
++++
+title = "R.I.P. Steve Jobs"
+author = "Danilo M."
+type = "life"
+date = "2011-10-06T10:51:17+00:00"
+excerpt = "Goodbye Steve Jobs.. One of the few people I really wanted to meet at least once in my life."
+image = "/uppies/2011/10/jobs.jpg"
+categories = ["blogging", "life"]
+tags = ["Steve Jobs"]
+format = "image"
++++
+<figure id="attachment_3691" aria-describedby="caption-attachment-3691" style="width: 1024px" class="wp-caption aligncenter"><img loading="lazy" class="wp-image-3691 size-large" src="https://danix.xyz/wp-content/uploads/2011/10/jobs-1024x741.jpg" alt="" width="1024" height="741" srcset="https://danix.xyz/wp-content/uploads/2011/10/jobs-1024x741.jpg 1024w, https://danix.xyz/wp-content/uploads/2011/10/jobs-300x217.jpg 300w, https://danix.xyz/wp-content/uploads/2011/10/jobs-768x556.jpg 768w, https://danix.xyz/wp-content/uploads/2011/10/jobs.jpg 1500w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption id="caption-attachment-3691" class="wp-caption-text">Today a truly beautiful mind has left our world. Today is a very sad day.</figcaption></figure>
\ No newline at end of file
--- /dev/null
++++
+title = "responsibility"
+author = "Danilo M."
+type = "life"
+date = "2011-09-26T14:24:45+00:00"
+excerpt = "Accept responsibility for your life. Know that it is you who will get you where you want to go, no one else."
+categories = ["blogging", "life"]
+tags = ["life", "responsibility"]
+format = "quote"
++++
+<blockquote class="wp-block-quote">
+ <p>
+ Accept responsibility for your life. Know that it is you who will get you where you want to go, no one else.
+ </p>
+</blockquote>
\ No newline at end of file
--- /dev/null
++++
+title = "sasso, carta, forbice, lucertola, spock!"
+author = "Danilo M."
+type = "life"
+date = "2010-11-10T14:08:19+00:00"
+image = "/uppies/2010/11/nimoy-spock.jpg"
+categories = ["blogging"]
+tags = ["game", "lizard", "paper", "rock", "scissors", "spock"]
++++
+Chi di voi miei fedeli (3) lettori non ha giocato almeno una volta nella vita a Sasso, Carta, Forbice? Beh, se ci avete giocato, avrete notato che tra giocatori che si frequentano assiduamente, c’è l’80% di probabilità di un pareggio causato dalla scarsità di alternative…
+
+Ecco che vi viene in aiuto l’espansione del classico gioco: **Sasso, Carta, Forbice, Lucertola, Spock!**
+
+In quest’espansione sono aggiunti 2 ulteriori simboli, la mano a forma di lucertola (un po’ come il serpente delle ombre cinesi) e il classico saluto vulcaniano (indice e medio da una parte e anulare e mignolo dall’altra).
+
+Le interazioni e quindi le regole si moltiplicano di conseguenza e diventano:
+
+ * La **forbice** taglia la **carta**.
+ * Il **sasso** schiaccia la **lucertola**.
+ * La **lucertola** avvelena **Spock**.
+ * **Spock** rompe la **forbice**.
+ * La **forbice** decapita la **lucertola**.
+ * La **lucertola** mangia la **carta**.
+ * La **carta** smentisce **Spock**.
+ * **Spock** vaporizza il **sasso**.
+ * Il **sasso** rompe la **forbice**.
+
+Mi sembra abbastanza più divertente, no!? :D
+
+Pensate che quest’espansione del gioco classico è stata menzionata addirittura in un articolo del times del 2005. L’invenzione si dice sia stata attribuita a [Sam Kass e Karen Bryla][1] e risalga addirittura alla metà degli anni ’90.
+
+Quindi adesso, tutti a giocare ;)
+
+ [1]: http://uri.danixland.net/l "RPSSL webpage"
\ No newline at end of file
--- /dev/null
++++
+title = "Speak to Me"
+author = "Danilo M."
+type = "life"
+date = "2013-03-19T20:29:57+00:00"
+categories = ["blogging"]
+tags = ["mad", "pink floyd"]
+format = "quote"
++++
+<blockquote class="wp-block-quote">
+ <p>
+ I’ve always been mad, I know I’ve been mad, like the most of us are. It’s very hard to explain why you’re mad, even if you’re not mad.
+ </p>
+
+ <cite>Pink Floyd – Speak to Me</cite>
+</blockquote>
+
+Credo che questo sarà il mio primo tattoo.. :)
\ No newline at end of file
--- /dev/null
++++
+title = "sunset in Siderno"
+author = "Danilo M."
+type = "life"
+date = "2016-01-25T17:31:56+00:00"
+image = "/uppies/2016/01/dx_0013.jpg"
+categories = ["nature"]
+tags = ["gopro", "kdenlive", "siderno", "sunset", "timelapse", "youtube"]
+format = "video"
++++
+
+{{< youtube ku9JVNK6rLU >}}
+
+my first video, an experiment with a GoPro Hero+ LCD and Kdenlive.
+
+enjoy!
\ No newline at end of file
--- /dev/null
++++
+title = "Vulnerabilities for PGP and emails"
+author = "Danilo M."
+type = "life"
+date = "2018-05-15T10:04:06+00:00"
+excerpt = "A series of vulnerabilities was discovered which affect emails encrypted with PGP and GnuPG, follow @EFF to understand more about this topic."
+image = "/uppies/2018/05/og-efail-resized_3.png"
+categories = ["security"]
+tags = ["efail", "eff", "electronic frontier foundation", "gnupg", "pgp", "security", "vulnerability"]
++++
+following a series of tweets from the Electronic Frontier Foundation, I’m reblogging their article to give it even more visibility on a topic that many don’t seem to know, which is email encryption.
+
+A group of researchers has found out [and published][1] a series of vulnerabilities affecting the use of PGP for email encryption (you can read more in depth coverage on this topic on the [EFF website][2])
+
+From what I understand the problem is related to those plugins that rely on PGP or GnuPG to automatically decrypt emails. This vulnerability could allow an attacker to read not only an encrypted message but even older messages encrypted with the same key.
+
+while the various vendors are fixing their software EFF recommendation right now is to disable all plugins that allow to decrypt emails automatically and not to decrypt messages inside the mail software but instead, export them and decrypt them offline.
+
+Here you can find a list of good procedures to disable the affected plugins and how to export encrypted emails to be read using offline tools: [**Pretty Good Procedures for Protecting Your Email**][3]
+
+
+
+ [1]: https://efail.de/
+ [2]: https://www.eff.org/deeplinks/2018/05/not-so-pretty-what-you-need-know-about-e-fail-and-pgp-flaw-0
+ [3]: https://www.eff.org/deeplinks/2018/05/pretty-good-procedures-protecting-your-email
\ No newline at end of file
--- /dev/null
++++
+title = "Walt quote"
+author = "Danilo M."
+type = "life"
+date = "2015-06-10T02:41:58+00:00"
+categories = ["disney", "life"]
+tags = ["inspiring", "quote", "Walt Disney"]
+format = "quote"
++++
+{{< quote source="Walt Disney">}}
+all our dreams can come true if we have the courage to pursue them
+{{< /quote >}}
\ No newline at end of file
--- /dev/null
++++
+title = "wp_patcher – un metodo per aggiornare WordPress"
+author = "Danilo M."
+type = "life"
+date = "2009-07-22T13:37:40+00:00"
+excerpt = "Ecco un metodo molto semplice per aggiornare la vostra installazione di WordPress, wp_patcher!!"
+categories = ["diy", "linux", "WordPress"]
+tags = ["bash", "svn", "update", "WordPress"]
++++
+Ciao a tutti,
+
+purtroppo si sa, l’estate è molto dannosa ai contenuti del mio blog, in questa stagione diventa difficile rimanere a casa a scrivere al pc, la tastiera del portatile si trasforma in una piastra su cui si potrebbe tranquillamente arrostire la carne per un picnic e starci vicino e come accendere il caminetto con 40 gradi di temperatura ambientale, praticamente un supplizio…
+
+<!--more-->
+
+Tuttavia gli sviluppatori di WordPress continuano alacremente a sfornare novità, ed è risaputo che bisogna aggiornare sempre la propria installazione di WP per non incorrere in spiacevoli inconvenienti come la perdita dei dati o l’hacking del proprio sito web. Per venire incontro ai blogger dalle ultime versioni di WP è possibile aggiornare automaticamente la propria installazione utilizzando una voce nel pannello di controllo. Questa possibilità, almeno per me, non ha funzionato nelle ultime 2 revisioni della versione 2.8, quindi ho deciso di provare un’altra strada :)
+
+chiacchierando su [slacky.eu][1], mi è stato suggerito di usare svn per recuperare le varie versioni di WP e poi di prendere solo le differenze in modo da andare a sostituire solo i files che effettivamente sono stati modificati. A questo punto mi son detto, perchè non scrivere uno script bash che mi chieda solo la mia versione attuale e quella verso cui voglio aggiornare, e poi mi crei un archivio contenente solo i files che mi servono??
+
+Detto fatto, mi sono messo a giocare un po’ con Vim e ho tirato fuori **wp_patcher.sh**, uno script bash che scarica le 2 revisioni richieste di wordpress, controlla le differenze e crea un archivio tar.bz2 pronto per essere installato ;)
+
+Questo è lo script:
+
+<pre class="wp-block-preformatted language-bash"><code>#! /bin/bash
+# WP-patcher - script che si occupa di recuperare le differenze
+# tra 2 versioni differenti di WordPress, scaricando le revisioni
+# tramite svn.
+
+# Autore: Danilo 'danix' Macrì - http://danixland.net
+# Licensed under the statements of the GPL v3 - http://www.gnu.org/licenses/gpl-3.0.html
+
+# exit status
+E_NOARGS=171
+
+# variabili
+workdir="wp_patch"
+old_vrs=$1
+new_vrs=$2
+sane_old_vrs=`echo $1 |sed s/[.]//g`
+sane_new_vrs=`echo $2 |sed s/[.]//g`
+patchdir="${sane_old_vrs}_to_${sane_new_vrs}_patch"
+
+#funzione di aiuto (viene mostrata in caso di errore nell'avvio del programma)
+showhelp () {
+ echo "USO: `basename $0` vecchia_versione nuova_versione"
+ echo "dove 'vecchia_versione' è la tua attuale versione di WordPress"
+ echo "e 'nuova_versione' è la versione verso cui vuoi upgradare"
+ exit $E_NOARGS
+}
+
+# controllo che siano presenti gli argomenti in modo da avere
+# le versioni di WP da scaricare
+if [ -z $1 ];then
+ showhelp
+elif [ -z $2 ];then
+ showhelp
+fi
+
+# inizio l'esecuzione dei comandi
+mkdir $workdir
+cd $workdir
+echo "sto recuperando le 2 versioni svn"
+svn co http://core.svn.wordpress.org/tags/$old_vrs
+echo "ho recuperato la versione $old_vrs"
+svn co http://core.svn.wordpress.org/tags/$new_vrs
+echo "ho recuperato la versione $new_vrs, adesso saranno esportate."
+svn export $old_vrs wp_$sane_old_vrs
+svn export $new_vrs wp_$sane_new_vrs
+rm -rf $old_vrs $new_vrs
+echo "ho esportato correttamente le 2 versioni di wordpress"
+echo "adesso procedo alla creazione della patch"
+diff -qr wp_$sane_old_vrs wp_$sane_new_vrs |cut -d" " -f4 > patch_file.txt
+mkdir $patchdir
+mods=`cat patch_file.txt`
+for i in $mods;do
+ cp --parents $i $patchdir
+done
+echo "compressione in corso..."
+cd $patchdir
+mv wp_$sane_new_vrs wp_$new_vrs
+tar -jcvf ../wp_${patchdir}.tar.bz2 wp_$new_vrs
+cd ../
+mv wp_${patchdir}.tar.bz2 ../
+echo "patch creata"
+echo "ripulisco la directory di lavoro"
+cd ../
+rm -rf $workdir
+echo "l'archivio contenente i files da sostituire"
+echo "è il file 'wp_${patchdir}.tar.bz2"
+# fine :)
+exit 0</code></pre>
+
+E’ molto semplice e non dovrebbe essere difficile modificarlo secondo le vostre necessità…
+
+Lo script va salvato con un nome a vostro piacimento (io l’ho chiamato wp_patcher.sh) e poi va lanciato in questo modo:
+
+`wp_patcher.sh vecchia_versione nuova_versione`
+
+In una directory qualsiasi nella vostra home, ovviamente è consigliabile che lo lanciate in una directory vuota in modo da evitare conflitti con i files e le dir che il programma crea durante il suo funzionamento…
+
+Nell’esempio che vi ho riportato ‘vecchia\_versione’ sarà la vostra attuale versione di WordPress, e ‘nuova\_versione’ sarà la versione verso cui vorrete aggiornare.
+
+Perchè lo script funzioni è necessario che nel sistema sia installato svn, tar, e tutti i comandi di base come mv, cp, rm ecc… ma dubito che stiate utilizzando una qualsiasi distribuzione Linux e non abbiate questi programmi installati ;) .
+
+Una volta creato l’archivio con i files da aggiornare vi basterà decomprimerlo e caricare i files sul vostro spazio web sovrascrivendo quelli già presenti. Nel caso in cui fosse necessario un aggiornamento del database di WordPress vi basterà lanciare dal browser la pagina **http://urldelblog/wp-admin/upgrade.php**.
+
+<blockquote class="wp-block-quote alert">
+ <p>
+ <strong><em>Come sempre vale il consiglio, prima di aggiornare WordPress, di effettuare un backup dei files e del database, in modo da poter ripristinare una situazione funzionante in caso di problemi.</em></strong>
+ </p>
+</blockquote>
+
+Questo script come potete vedere è rilasciato sotto la GPL v3, quindi è liberamente utilizzabile e modificabile entro i termini di questa licenza appunto.
+
+Se vi dovesse tornare utile, o anche semplicemente se voleste dirmi che lo avete provato o che non ha funzionato o farmi i complimenti o mandarmi a cagare :) non fatevi problemi e lasciatemi un commento…
+
+A presto
+
+ [1]: http://www.slacky.eu "La comunità italiana di utenti slackware"
\ No newline at end of file
--- /dev/null
++++
+title = "xrandr e dual head su slackware 12.2 e intel"
+author = "Danilo M."
+type = "life"
+date = "2009-06-29T17:05:13+00:00"
+excerpt = "'In questo breve articolo vi spiegherò come ottenere un desktop ultra wide che si espande su ben 2 monitor, ingredienti: una scheda video con 2 uscite e un editor di testo...'"
+categories = ["diy", "linux"]
+tags = ["dual head", "extended desktop", "monitor setup", "slackware", "xorg", "xrandr"]
++++
+Oggi mi è capitato sottomano un monitor 17″ e mi è venuta la curiosità di provare a collegarlo all’uscita vga esterna del mio laptop. Detto fatto ho provato a fare qualche ricerca su internet per vedere se riuscivo a tirare su un sistema dual head in cui i 2 schermi formassero un unico desktop più grande.
+
+<!--more-->
+
+Dopo qualche tentativo ho trovato la soluzione quasi perfetta, cioè uno schermo complessivo di 2560×1024. Per ottenerlo è bastato mettere questa semplice riga nel mio xorg.conf:
+
+`Virtual 2560 1024`
+
+all’interno della SubSection “Display” nella sezione “Screen”. Quella riga non fa altro che istruire X sulle dimensioni complessive del desktop virtuale, i 2 valori si ottengono sommando la risoluzione del primo schermo, che nel mio caso era di 1280×1024, alla risoluzione del secondo schermo, che è nel mio caso quello del laptop e cioè 1280×800. La larghezza totale è quindi diventata 2560 mentre per l’altezza ho dovuto prendere quella dello schermo più grande, cioè quello esterno e quindi 1024.
+
+Ovviamente facendo in questo modo ho una superficie del desktop di circa il 120% rispetto a quella effettiva dei 2 monitor, però X tiene conto di questo problemino, infatti se io massimizzo una finestra nello schermo grande, questa si adatta alla dimensione maggiore, se la massimizzo nello schermo del laptop si adatta alla dimensione wide e non mi da problemi di scrolling. L’unico fastidio è che non arrivo a vedere la fine della barra di lxde se la lascio posizionata in basso, ma anche questo si risolve facilmente mettendola in alto…
+
+A questo punto, ogni qualvolta io voglia attivare il doppio desktop, mi basterà lanciare questo script che mi sono creato, l’ho chiamato **dualhead.sh**:
+
+<pre>#! /bin/bash
+
+case $1 in
+ start ) xrandr --output LVDS --mode 1280x800 \
+ --output VGA --mode 1280x1024 --left-of LVDS
+ ;;
+ stop ) xrandr --output VGA --off
+ ;;
+ * ) echo "USAGE: `basename $0` start | stop"
+ exit 1
+ ;;
+esac
+exit</pre>
+
+lanciandolo con flag “start” avvierà il dualhead mentre lanciando lo script con “stop” tutto il desktop ritornerà sul solo schermo del laptop in quanto xrandr spegnerà l’uscita vga esterna.
+
+Adesso potete godervi il vostro splendido desktop esteso, magari usando uno degli sfondi ultra wide presenti su [compiz-themes.org][1], io sto usando una splendida foto della baia di Melbourne, il bello è che comincia su uno schermo e finisce sull’altro, ma se non provate non potete capire… ;)
+
+Buon divertimento…
+
+ [1]: http://www.compiz-themes.org/index.php?xcontentmode=6110&PHPSESSID=593590581b90557a2f710adca3e82d40 "skydomes su compiz-themes.org"
\ No newline at end of file
--- /dev/null
++++
+title = "About Loneliness"
+date = "2011-08-11T18:09:41+00:00"
+draft = true
+type = "quote"
+tags = ["loneliness", "solitude"]
+image = "/uppies/2011/08/loneliness.jpg"
+author = "Danilo 'danix' M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "baking programs"
+date = "2019-01-02T15:36:49+00:00"
+draft = false
+type = "life"
+tags = ["slackbuild"]
+image = "/uppies/2019/01/bake-a-cake.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Bash Notes"
+date = "2023-04-07T11:20:20+02:00"
+draft = true
+type = "life"
+tags = []
+image = "/img/default_article.jpg"
+author = "danilo 'danix' m."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "CAD designing in GNU/Linux"
+date = "2021-05-01T17:51:58+00:00"
+
+type = "tech"
+tags = ["3D printing", "cad", "cura", "fusion360", "slicer", "solvespace"]
+image = "/uppies/2021/05/PXL_20210501_114542849.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Ceasar quote"
+date = "2011-07-28T19:03:39+00:00"
+
+type = "life"
+tags = ["Caesar", "quote"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Come Funziona Questo Sito"
+date = "2024-11-12T11:12:25+01:00"
+draft = true
+type = "life"
+tags = ["web", "development"]
+
+author = "danilo 'danix' m."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "conquista la folla.."
+date = "2013-04-21T08:17:11+00:00"
+draft = true
+type = "life"
+tags = ["gladiator", "massimo decimo meridio"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "convertire file video in mp3"
+date = "2012-05-25T15:42:02+00:00"
+
+type = "life"
+tags = ["audio", "convert", "mp3", "video"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "gify.sh – back to bash scripting"
+date = "2016-01-25T12:41:06+00:00"
+
+type = "tech"
+tags = ["bash", "convert", "gif", "imagemagik", "mogrify", "script"]
+image = "/uppies/2016/01/G0092546.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Git – how to setup your own server pt 2"
+date = "2018-12-17T07:39:08+00:00"
+draft = true
+type = "life"
+tags = ["automation", "do it yourself", "flask", "git", "howto", "python", "ssh"]
+image = "/uppies/2018/12/gitout.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Git Setup Your Own Server"
+date = "2021-06-13T12:07:49+02:00"
+
+type = "life"
+tags = ["git", "server", "setup", "howto", "do it yourself", "ssh"]
+image = "/uppies/2021/06/gitout.jpg"
+author = "danix"
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "haiku"
+date = "2011-01-09T23:15:01+00:00"
+
+type = "life"
+tags = ["haiku", "loneliness", "love", "quotes"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "haiku"
+date = "2010-12-02T10:33:50+00:00"
+
+type = "life"
+tags = ["haiku", "quotes"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Imagine."
+date = "2015-01-11T01:38:25+00:00"
+
+type = "life"
+tags = ["imagine", "john lennon"]
+image = "/uppies/2015/01/imagine_colors.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Mario Congiusta candidato al Consiglio Regionale calabrese"
+date = "2010-03-05T09:17:55+00:00"
+
+type = "life"
+tags = ["calabria", "candidato", "congiusta", "consiglio", "elezioni", "incensurato", "libertà di stampa", "mario", "regionale"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Katsushika Hokusai"
+date = "2011-07-27T20:35:16+00:00"
+
+type = "life"
+tags = ["great wave", "hokusai", "katsushika", "mt fuji", "paintings"]
+image = "/uppies/2011/07/The-Great-Wave-Off-Kanagawa-1823-large.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "La giornata del pi Greco"
+date = "2010-03-14T11:55:45+00:00"
+
+type = "life"
+tags = ["celebrazione", "festa", "lerry shawn", "pi greco"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "le email queste sconosciute :)"
+date = "2010-11-06T22:28:43+00:00"
+draft = true
+type = "life"
+tags = ["attachments", "email", "howto", "mistakes", "privacy", "subject"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Manage your passwords with password-store"
+date = "2021-05-27T15:08:05+00:00"
+
+type = "life"
+tags = ["android", "gnupg", "management", "password", "password-store"]
+image = "/uppies/2021/05/vault-door1.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Money for indipendence"
+date = "2013-04-30T08:58:25+00:00"
+
+type = "life"
+tags = ["hope", "indipendence", "money", "quotes"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "myself as a droid.."
+date = "2011-02-14T13:31:08+00:00"
+draft = true
+type = "life"
+tags = ["android", "droidify", "market"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "nerdness"
+date = "2011-08-31T09:57:22+00:00"
+
+type = "life"
+tags = ["john green", "nerds"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "new home server ideas"
+date = "2019-10-30T13:22:48+00:00"
+
+type = "life"
+tags = ["build", "flying dutchman", "server"]
+image = "/uppies/2019/10/server.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Of Being Lonely"
+date = "2025-10-04T12:50:17+02:00"
+draft = true
+type = "life"
+tags = ["life", "responsibility", "loneliness", "introspection"]
+image = "/uppies/2025/10/loneliness.jpg"
+author = "danilo 'danix' m."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "outside of the box"
+date = "2011-08-31T08:05:35+00:00"
+
+type = "life"
+tags = ["quotes", "think outside of the box"]
+image = "/img/default_article.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "playing with colors"
+date = "2016-02-14T17:52:21+00:00"
+
+type = "life"
+tags = ["colors", "github", "html5", "palette", "php", "viewer"]
+image = "/uppies/2016/02/palette.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "poker time.."
+date = "2010-12-19T21:07:04+00:00"
+draft = true
+type = "life"
+tags = ["feste", "gioco", "natale", "poker"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "pure nerdgasm"
+date = "2011-10-01T07:28:14+00:00"
+
+type = "life"
+tags = ["floppy disks", "imperial march", "nerdgasm", "nerds", "star wars", "youtube"]
+image = "/uppies/2011/10/vader.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "R.I.P. Steve Jobs"
+date = "2011-10-06T10:51:17+00:00"
+
+type = "life"
+tags = ["Steve Jobs"]
+image = "/uppies/2011/10/jobs.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "responsibility"
+date = "2011-09-26T14:24:45+00:00"
+
+type = "life"
+tags = ["life", "responsibility"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "sasso, carta, forbice, lucertola, spock!"
+date = "2010-11-10T14:08:19+00:00"
+
+type = "life"
+tags = ["game", "lizard", "paper", "rock", "scissors", "spock"]
+image = "/uppies/2010/11/nimoy-spock.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Speak to Me"
+date = "2013-03-19T20:29:57+00:00"
+
+type = "life"
+tags = ["mad", "pink floyd"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "sunset in Siderno"
+date = "2016-01-25T17:31:56+00:00"
+
+type = "life"
+tags = ["gopro", "kdenlive", "siderno", "sunset", "timelapse", "youtube"]
+image = "/uppies/2016/01/dx_0013.jpg"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Vulnerabilities for PGP and emails"
+date = "2018-05-15T10:04:06+00:00"
+
+type = "life"
+tags = ["efail", "eff", "electronic frontier foundation", "gnupg", "pgp", "security", "vulnerability"]
+image = "/uppies/2018/05/og-efail-resized_3.png"
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "Walt quote"
+date = "2015-06-10T02:41:58+00:00"
+
+type = "life"
+tags = ["inspiring", "quote", "Walt Disney"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "wp_patcher – un metodo per aggiornare WordPress"
+date = "2009-07-22T13:37:40+00:00"
+
+type = "life"
+tags = ["bash", "svn", "update", "WordPress"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
--- /dev/null
++++
+title = "xrandr e dual head su slackware 12.2 e intel"
+date = "2009-06-29T17:05:13+00:00"
+
+type = "life"
+tags = ["dual head", "extended desktop", "monitor setup", "slackware", "xorg", "xrandr"]
+
+author = "Danilo M."
+
++++
+
+TODO: Tradurre questo articolo dall'inglese all'italiano.
pointer-events: none;
}
+.visible {
+ visibility: visible;
+}
+
.invisible {
visibility: hidden;
}
+.static {
+ position: static;
+}
+
.fixed {
position: fixed;
}
right: 0.75rem;
}
+.right-4 {
+ right: 1rem;
+}
+
.top-0 {
top: 0px;
}
top: 0.75rem;
}
+.top-4 {
+ top: 1rem;
+}
+
.z-10 {
z-index: 10;
}
margin-right: auto;
}
+.my-4 {
+ margin-top: 1rem;
+ margin-bottom: 1rem;
+}
+
.my-6 {
margin-top: 1.5rem;
margin-bottom: 1.5rem;
margin-top: 4rem;
}
+.mt-2 {
+ margin-top: 0.5rem;
+}
+
.mt-3 {
margin-top: 0.75rem;
}
display: inline-flex;
}
+.table {
+ display: table;
+}
+
.grid {
display: grid;
}
width: 100%;
}
-.max-w-2xl {
- max-width: 42rem;
-}
-
.max-w-3xl {
max-width: 48rem;
}
padding-right: 2rem;
}
+.py-0\.5 {
+ padding-top: 0.125rem;
+ padding-bottom: 0.125rem;
+}
+
.py-1 {
padding-top: 0.25rem;
padding-bottom: 0.25rem;
text-align: right;
}
+.font-mono {
+ font-family: JetBrains Mono, monospace;
+}
+
.font-oxanium {
font-family: Oxanium, monospace;
}
color: rgb(255 255 255 / var(--tw-text-opacity, 1));
}
+.line-through {
+ text-decoration-line: line-through;
+}
+
.antialiased {
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale;
color: var(--accent);
}
+.first-letter\:text-3xl::first-letter {
+ font-size: 1.875rem;
+ line-height: 2.25rem;
+}
+
.hover\:bg-surface:hover {
background-color: var(--surface);
}
--- /dev/null
+<span class="text-2xl font-bold first-letter:text-3xl">{{ .Inner }}</span>
--- /dev/null
+<em>{{ .Inner }}</em>
--- /dev/null
+{{- $src := .Get "src" -}}
+{{- $alt := .Get "alt" -}}
+{{- $class := .Get "class" -}}
+<figure class="my-6 {{ $class }}">
+ {{- if $src -}}<img src="{{ $src }}" alt="{{ $alt }}" class="w-full" />{{ end -}}
+ {{- .Inner -}}
+ {{- if .Get "caption" -}}<figcaption class="text-sm text-text-dim mt-2">{{ .Get "caption" }}</figcaption>{{ end -}}
+</figure>
--- /dev/null
+<div class="{{ .Get "divClass" }}">
+ <img src="{{ .Get "src" }}" alt="{{ .Get "alt" }}" class="image fit" />
+</div>
--- /dev/null
+{{- $lang := .Get 0 -}}
+{{- $opts := .Get 1 | default "" -}}
+{{ highlight .Inner $lang $opts }}
--- /dev/null
+<img src="{{ .Get "src" }}" alt="{{ .Get "alt" }}" class="w-full my-4" />
--- /dev/null
+<s>{{ .Inner }}</s>
--- /dev/null
+<iframe class="w-full aspect-video my-6" src="https://www.youtube.com/embed/{{ .Get "id" }}" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
