Someone asked me if it’s possible to buy a Blinkenshell T-shirt earlier today, this has not been available earlier but I think it’s a great idea. I’m not the best with graphical design however so I might need some help with creating a nice motif for the shirts (a cool tagline would also be nice!). If you have an idea and know your way around vector graphics please give it a try!
The graphic has to be in vector format (preferrably SVG), and there are some limitations on how small the lines etc can be: Spreadshirt Vector Graphics Recommendations
If you want you can use the Blinkenshell logotype (modified to have thicker lines) in the graphics
Email me your submissions before the 10th of August (23.59 CET) and then we will let the community vote on the best design. I’ll buy one T-shirt and send it to the winner for free! 🙂
The Blinkenshell merch shop will look something like this (you can see what T-shirt models, colors and sizes are available in the shop now or on Spreadshirt.com)
Update1: The contest deadline has been pushed forward to the 25th of August
There has been some discussions on IRC on how to change the vouching system to make it more fair and to minimize abuse. I’ve implemented some initial changes to take care of the most immediate problems that I see, but we might need to make more changes in the near future. Please join the discussion on IRC if you have any input regarding this 🙂
Changes as of 2014-06-27:
- No more “IRL-vouch” (+2 point vouch)
- You will need three vouches instead of two to pass step 4. Since the community has grown and there are more people who can vouch, and it’s easier to get vouched than before. This change makes it a bit harder to pass step 4 again.
- You will not receive vouch tokens if you don’t have a score of at least +2 vouch points yourself. This means that old-timers and people who pays to get past step 4 will not be able to vouch others until they get +2 points themselves.
- You can easily change your vouch from negative to positive or the other way around in the signup program.
I’m also planning a place where you can easily see who vouched for whom, possibly via the signup list webpage.
Thanks to everyone for bringing this to my attention and suggesting changes!
It’s time for Blinkenshells second Top vouchers giveaway where where the three users who has vouched most new members since the last giveaway are awarded with some extras for their Blinkenshell account. Vouching is very important too keeping the community alive. I want to show my appreciation to the people who spend some time on getting to know the new users. The rewards are the same as last time, you can choose one of the following:
The winners are:
- lmca (tidalwaters)
Thank you and everyone else who vouches newcomers! The winners can contact me via IRC or email to receive their award.
The maintenance went very well I think, but it did take a long time. Triton was back online at around 23.00 on Friday, and Web and Mailservices was not online until Saturday. I’ve been at the computer all waking hours for the last two days, not stepping outside my appartment until today (apparently it started snowing some time during the weekend, who knew…), but it has been a lot of fun! It’s been a long time since sat down to do some serious work on Blinkenshell, it’s mostly been the day-to-day stuff since last spring basically (200 days uptime). I think I’ve missed getting my hands dirty with the details of the Linux kernel configuration options and such 🙂
So, what has actually changed then? I guess most of the stuff is not very visible to the end user. Some programs on Triton are running new versions, there is a new kernel witch has the new reworked OOM-killer which might affect how/which programs gets killed when you run out of memory, but most of the things are behind-the-scene things. I’ve upgraded the hypervisor, the fileserver, I’ve replaced 4 harddrives and a CPU fan. I’ve installed a UPS and changed some logging and monitoring stuff. I’ve upgraded the web and mail servers, including anti-spam settings and some security things. One of the changes I’m personally most excited about is the new server-side mail filtering options via Sieve. You can for example automatically move spam messages to the Junk folder serverside or filter senders to specific folders etc. Previously I’ve had to do this in my Email client, and that is not very neat if you run a lot of different clients (Alpine/textmode, Webmail, standalone client, smartphone etc).
I’ve also cleared out a few bugs, but there’s probably a few new bugs in there somewhere as well. I’ve also updated some wiki pages, and I’ve created Bitcoin wallet if you want to donate something 😉
Yesterday there was some unexpected downtime on Triton during the afternoon, this was because someone actually hijacked the IP-space that Triton and a lot of other servers use. Someone on AS62196 started announcing a /21 prefix containing Tritons public IP, which caused all the traffic to get routed towards Iran. This also happened to Youtube a few years back, but I didn’t think it was anything common to occur. It was sorted in a few hours though 🙂
Okay, I think that’s all for now (well, maybe we’re going to upgrade the IRCd soon also). Thanks for using Blinkenshell, see you on IRC!
I’m planning on taking the system down for maintenance, Triton has an uptime of almost 200 days and it’s time for a new kernel as well as some other updates. I will also take this opportunity to upgrade/replace some hard drives in the server.
I will take down Triton/SSH, web and mail services. Since it’s some hardware replacement and upgrade of Triton (compiling stuff on Gentoo) this will probably take almost a full day. I’m planning on starting at 10.00 CET on Friday January the 10th. I’m going to try and post some updates as I’m going along on the Blinkenshell twitter account if you’re interested in following the progress/see when the services are going to be back up again.
Please make a (mental) note about this so you won’t be surprised when you can’t log in on Friday or when your screen session has been killed when you get back 🙂
I wanted to show my appreciation for the awesome Blinkenshell members who take their time to get to know newcomers and vouch for them so they so we can grow our great community, and therefore I’m arranging this little giveaway. I’ve looked up the three members who vouched the most new users during the last 6 months (I’ll exclude anyone who vouched for a users who got banned, thankfully none of the top three vouched for someone who got banned this time!)
The three most active vouchers are:
Thank you! You can contact me (via IRC or email) to get one of the following bonuses:
I want to make this a recurring thing so there will most likely be a similar announcement during the fall. 🙂
If you’ve been having problems compiling programs on Triton you’ll be glad to know that there is now a new server where you can compile things with more relaxed resource/memory limits. The idea is that you can use much more memory than on Triton, but only for a short while. The server does not allow any outgoing network connections, and you can’t have any long-running or background processes. There are also more debugging tools installed, like Valgrind.
Try it out by connecting via SSH from Triton: ssh buildserver
More info on the wiki: Info/Compiling
It’s been a while since I wrote anything here, but I thought I might summarize the past year and tell you a bit about what’s been happening behind the scenes at Blinkenshell. The service is much the same, but there has been some changes that you might not be aware of.
In August I moved from Linköping to Stockholm, and the main server moved with me. There was quite a long downtime here, but everything went well overall. I’ve also started a new job in Stockholm, so I’ve not put very much time into Blinkenshell this autumn.
In November when I was just about to start my one week vacation to go to Dreamhack and help build the network infrastructure, something happened with the server I use to tunnel IPv4 traffic. This was ofcourse on a friday, so the service provided did not respond until monday. It tunrned out that the server had rebooted, and the harddrive was not ok. They helped me install a new server the next week I tried to recreate the configuration from old backups and some from memory. Everything did come back up online, but it was a long downtime of several days.
Everything seemed to work fine for some weeks, but on the 21st of December the new server I had been moved to stopped responding. Since this was also on a Friday, and there was Christmas holidays after that, the service provider has still not responded to me about why the server went down. A friend of mine helped me set up a new server for tunnelling the IPv4 traffic now, so everything is back online. This was however an even longer downtime than the one in November.
The new server means we do have a new IPv4 address, and some IRC networks has not updated their I-lines yet so we’ve had issues connecting to Freenode and IRCnet for a couple of days for example. I do however think this new server should help improve response times since it has better connectivity in general.
I believe the new server will be more stable then the old was was this last autumn, but I can’t guarantee anything as usual. I hope you will stick around and see what happens in 2013, and a big welcome to all the new members that continue to join this great community! 🙂
If you’re a mobile SSH user, you might want to take a look at Mosh
You can run mosh on Blinkenshell only if you have a supporter account (since it requires an open UDP port).
Tomorrow, Saturday the 11th of August, I’m going to take down all Blinkenshell services to move the physical server to a new location. I’m going to shut the server down at around 14.00 CET, and it’s probably going to be offline until late evening. I’m also going to install some new harddrives and perform the regular software updates etc. I’ll try to keep you updated on twitter as the maintanance is going along.