Weechat has been updated to version 2.5, to take
advantage of various bug and security fixes, after
it was brought to my attention in IRC.
If you have a running Weechat (in tmux or something),
then you can run
to update the running binary in-place.
Over the last two weeks I've been developing a homegrown
twtxt registry server for tilde.institute. I'm happy to
announce that it's now running publicly:
Instructions are available on the main page of the registry,
including how to add your own data to the registry using curl.
If you're not familiar with twtxt, it's a decentralized
microblogging platform "for hackers". You can install the client
via pip (pip install twtxt), and then after setting it up, issue:
$ twtxt follow institute https://twtxt.tilde.institute/api/plain/tweets
To add the registry data to your personal 'timeline'. Don't forget
to add your own info to the registry to help it grow! Your statuses
will be periodically scraped and viewable from the registry server.
This allows many users' statuses to be available from a single
For more info:
I've run into a bit of a snag with the upgrade.
It appears that, with the current partition layout
and disk size, there isn't enough space to do
an in-place upgrade.
This brings to the forefront another issue that
I knew would come up eventually: the need to move
tilde.institute to a new server.
This started out as a very tiny project that has
grown faster than I initially expected. The
current server is a bit underpowered and its disk
space is insufficient for the current utilization
level and growth trends.
It's a good thing, in my opinion. It means more
people than I initially thought find this concept
appealing and this space useful. I'm so glad
everyone is taking part in this project.
Kneezle and myself will come up with a plan to
migrate tilde.institute, both to a new server and
to OpenBSD 6.5, in a way that will minimize
downtime or service disruptions. Then, one of us
will send an email notification out with a timeline.
Hi folks !
I was thinking about writing some documentation about email (and maybe
more) encryption using GnuPG. The target would be not-so-techy tilde
users. And the objective would be that anybody can use public key
encryption if they want to with minimal hassle.
I would like to know what people use for handling email, as I've been
using mutt for so long I don't really know what other folks do.
Please answer to this post (I'll publish it also on bbj and maybe
tilde.news) with your combo of OS/email agent or simply with a "not
That way I'll have an idea of what config examples to include on the
docs or that perhaps there's no interest at all in this and I can use my
time on other stuff ...
That's it, please take a couple of minutes to answer this ;-)
Have a nice day !
GnuPG key: https://onna.be/44CA735E.asc
Initially, I'd put the 6.5 upgrade on the back-burner
because of the recurrent inspIRCd issues. I didn't
want to cause any more service disruptions too soon
after the v2->v3 move.
I'm going to be upgrading a test environment, smoothing
out the kinks, then upgrading the production tilde.institute
server. My plan is to do the production upgrade on
Monday, 11 June, 2019, around 22:00 US Eastern Time,
which is 2:00 AM UTC, Tuesday, 12 June, 2019.
If anything changes, I'll send out another email. I'll
also send out at least one reminder email in between now
and Monday, and a warning email about an hour before
I begin the upgrade.
Let me know if you have any questions!
I've been using the native mail(1) MUA on tilde.institute. It
would be nice to have 's-nail' installed as an updated version
of mail(1). Also, is there any plans to mail email available
via imap/imaps ? That would be my preference though I understand
that adds an extra load on the sysadmins WRT security and maint.