Hello, just a brief news that @wpn's fediverse client instance, powered by phanpy, has finally got (working) translations since the latest release, which I have built a few minutes ago. You do also keep the other features which were already available, like the GIFs picker. If you happen to run into any issue, let me know. Thanks
It's officially pimped!! Can't believe the time I spent fixing "homarr" progressive layout, almost breaking at each smallest change. New @wpn's home is running "glance" and the whole site is just 1 .yml file, plus some custom CSS rules and assets (images). Took me ~2 evenings to set it up and it's looking quite good, in my opinion. It's light (actually it's dark-only 😀 ), fast, fully featured. Unfortunately, you always have to touch it first hand to understand the wrong choices and remedy them; better late than never though!
Hello, this is going to be a little how-to configure aerc (a console mail client) in your @wpn shell - applies to other shells / mail servers as well, but it will be tailored for @wpn users. aerc configuration is interactive as soon as you start it for the first time, but it will store your mail password in clear text inside ~/.config/aerc/accounts.conf file. We want instead to use the standard Unix password manager, pass, to encrypt it. First you need a GPG key, which will be used to encrypt imap/smtp passwords. There are 2 ways: Import an existing private key Create a new keypair on @wpn and use that Let's start: $ gpg-connect-agent /bye # initializes the gpg-agent If you see the following lines (you should), everything is good. gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent' gpg-connect-agent: waiting for the agent to come up ... (5s) gpg-connect-agent: connection to agent established GOTO 1) to import an existing key GOTO 2) to create a new key GOTO 3) when…
Hello! Last "real" post was about 2 months ago.. I got busy with stuff at home but also made a lot of adjustments here and there at @wpn. Let me list the most important ones: Set up shell and email users' homes backup: archives are still stored on the VPS for the time being, till when I'll find another proper backup location. Cleaned up /var/www/ and nginx virtualhosts; also removed "Shaarli", since I wasn't really using it anymore. Added a new board on the main site for BitTorrent, reachable here Upgraded XMPP Prosody server to 13.0.0 and isolated anon webchat even more, so that those users won't be able to connect to Biboumi IRC gateway. Upgraded all #slixmpp powered bots to 1.10, released only yesterday Formatted (again) the 2 pdf files regarding @wpn's Term of Use and Privacy Notice (no rules updates though) I think that's about it.. probably 😀 I'm definitely forgetting something. Some other news: a few new users joined XMPP and more than a few logged…
I'll update this post whenever I see fits, A.K.A. when I have other bits of information which don't require a whole post. Operations on files and directories Move files to the current/parent directory in Linux Current dir find . -type f -exec mv {} . \; Parent dir find . -type f -exec mv {} .. \; Recursive chmod on files and dirs To change all the directories to 755 (-rwxr-xr-x): find /var/www/blog -type d -exec chmod 755 {} \; To change all the files to 644 (-rw-r--r--): find /var/www/blog -type f -exec chmod 644 {} \; Certbot Certbot cli /etc/letsencrypt/cli.ini When renewing, use the same private key as the existing certificate. (default: False): reuse-key = True Common commands Register single domain: certbot certonly --standalone -d domain.tld --dry-run Remove “–dry-run” when ok. Renew single domain: certbot renew --cert-name domain.tld --dry-run Remove “–dry-run” when ok. Delete single domain: certbot delete --cert-name domain.tld Cannot use "--dry-run" in this case…
Busy Days, Exciting Progress 🚀 It’s been a couple working months, busy and sometimes hard but in the best way possible! For starters, today the "GD" website went officially online, after we completed its migration from ZOPE to Wordpress and I couldn't be happier 😉 Another thrilling update is with COMMutiny, our social network project. The converse.js anonymous chat, originally set up for @wpn’s support room, has now found its own space within COMMutiny. This is a big step forward, and we’re inviting everyone interested in #XMPP, gaming, and social networks to join the conversation, anonymously or not. On top of that, we’ve launched a brand-new freelance website, powered by Hugo. It’s sleek, fast, and everything we hoped it would be — hooray for #Hugo! If you’re passionate about decentralized communication, gaming communities, or just want to connect with like-minded folks, we’d love to see you in COMMutiny! See you soon 👋
