Automatic Remote Connection through Deluge WebUI in Debian/Ubuntu-based Systems

In search for good bittorrent clients on ‘Nixes, one name could come up on your mind if you ever knew about these things:

Deluge is one of the most customizable and feature-rich torrent clients out in the woods. Mostly used in the most popular platform which is Windows Linux, most servers/torrent boxes used it for daily business. You can use remote shell and clients to shape and manipulate your Deluge remotely, to suit your carnal needs.

To enable remote connections to deluge through clients, there are two separate components at the backside of the program that handles this task.

These components are the daemon and web interface, called deluged and deluge-web, respectively.

There are clients that connect directly through the daemon, a prominent example of this is deluge (the client) itself, with classic interface option off. There are also clients that connect through the web interface deluge-web instead, which in turn connects to the daemon deluged. This approach might have been prefered to enable usage of web security technologies, SSH for example. Clients using this approach must have required the web interface to be configured before communication is possible through the daemon.

Deluge can be run and configured easily and out of the box on ‘nix systems after installation. But to configure telekinesis, normally you need to download and install two separate packages. You might not be able to guess the package names because you have low IQ. After somehow figuring it out, you can enable them on your deluge client, and set things ready for remote hook-up.

Now, suppose you want to connect remotely to deluge in your LAN network using other devices for lulz. You need clients that supports this feature.

But luckily, you have an android because iPhone sucks. You used Transdroid. It connects to deluge through the web interface. So, the web interface needs to be connected to the daemon. So, in every instance you start your deluge, you need to login through your web interface to connect it to the daemon. This is fine in the first run. But when your box that serves deluge is not an everlasting server, that is turned off regularly, you need to set things up again! Why can’t they just meet automatically in the usual place and hook-up already?

The solution is simple.

Assuming you have set up deluged and deluge-web on the local machine, your deluge is running, disabled classic interface and enabled WebUI plugin.
You’ll connect to the web interface for the first time. With default settings, you’d use the Port 8112. So, in your web browser you type:


Enter the default password, which is deluge,and connect to the local
daemon (or a remote daemon, if you have, for whatever reasons, like illegal ones).

Now, close your deluge client and daemon.

Open up your favorite text editor, in my case nano, and open web.conf:

nano ~/.config/deluge/web.conf

find the line that says “default_daemon”, and edit it accordingly. Assuming default port and localhost:


"default_daemon": "",

Save the file. Start deluge and deluged, and that’s the solution. Everytime deluge starts, so does deluge-web, which now automatically connects to the daemon, so when you open the WebUI, you don’t need to connect to the daemon manually. So does your remote client. Short, sweet and simple.


First Look on Rage of Bahamut: Genesis

IMAGE HEAVY. Scroll at your own discretion.

Spoilers may unintentionally be written.

Attack on Rage of Bahamut: Genesis (Shingeki no Bahamut: Genesis) is a surprise this season. Not really expecting anything from a mobile game adaptation, not to mention, a card game, not the physical one (oftentimes video game adaptations suck ass, like Yu-gi-oh!), it somehow delivers its first episodes gracefully.

Synopsis from the Internet:

Mistarcia is a magical world where humans, gods, and demons mingle together. In the past, the black-and-silver winged Bahamut has threatened to destroy the land, but humans, gods, and demons overcame their differences to fight together and seal its power. The key to that seal was split in two, one half given to the gods and the other to demons, so that they would never be united and Bahamut never released. Now, two thousand years later, the world is in an era of peace—until the day a human woman steals the gods’ half of the key.

The story follows the adventures of three characters. Amira, a demon chick who stole the half of the God’s key (I know it said above a human woman… Free spoilers!), must embark north with the “help” of the perm-haired bounty hunter Favaro, who always cross paths with his apparent arch-rival Kaisar, also a bounty hunter that came from a lineage of Knights. What would their fate have to do with the war between the gods and the demons and the threat possessed by the raging Bahamut, the destroyer of the world, is yet to be seen. And what does Amira intend to do with the God’s Key?

Let’s talk about the art. Character design is great and with a style reminiscent of those film-grade drawing style. Because of this, it certainly has the vibe of film animations (which, I insist, is a very welcomed feeling against a plethora of standard anime!) It has superb animation; fluid and consistent. It also has good utility of foreground effects and lighting, which is sported in good amount throughout the current episodes.



Now, the opening and ending songs. Every anime ought to have one. It is a very crucial part of the overall quality of the show, and I admit I sometimes skip over it. But good, very fitting, thematic, catchy OP/ED? They become part of the 23-minute episode. It becomes part of the soul. You just couldn’t skip it, if not, a glimpse of it. Bahamut’s OP rocks. It still sticks to me. I like alternative post-rock. You can’t blame me.

How about the ED song? I do like the art sequence there though. But the ED itself isn’t out of ordinary. I was skipping it most of the time. Where’s the speech about becoming part of the soul…

The soundtrack is, well, good. Nothing outstanding in particular, but it fits with the theme and genre. Not bad, I guess.

I may have one problem with one technical sector of the show, the sound FX.
It doesn’t have enough amplification and impact on some areas (like falling rocks). I don’t know if it is in part of Funimation (they were known for shitty eccentric re-encodes), but in the end, it is just a minor problem, and the good aspect of the show have already compensated for it.

The first two episodes took a great job of introducing the universe and characters, especially of Amira. I really like how they showed the possibilities of how Amira’s outfit can become (I thought I’m talking about a better point?). I haven’t personally played the game, or even knew about it, but I guess lore from the game appears here. And they did a good representation of the cards here, by the way (if I’m not wrong).

But I’m sad that they were not keeping the long hair Amira sports earlier (Twin-tails doesn’t hurt, though). Really.


However, now in episode 3, things may have started to get stale – at least that’s what I feel. The quality is still consistent – but the problem may lie in the pacing.

Nothing happened that really advanced the plot in this episode. Granted that it is not episodic in nature, it should have done something to keep expectations and interest for the next episode.

We do have some goodies though. Rita enters the scene.



Amira and Perm-hair still goes on the journey. They met up with the guy that screams Favaro. Let’s call him Favarro!!(screams). Favarro!!(screams) gets himself the Loli. (laugh)




Anyway, that’s all I can say for this episode. This was supposed to be a first look, alright?



With all the points above (I hope there are), it is worthy checking it out. Don’t get me wrong; it may have problems but so do other great anime. It’s not bad nor it is a masterpiece, but it is still better than your average anime.

Will be looking forward for the next episodes.

Unlimited Blade Works Ep. 2


Image heavy. Spoilers are kept minimal as possible.

I was quite sad that the show returned to the usual 23-minute format (no more 47± minutes episodes )-:), but as long as the episode has the right pace and consistent quality, I’m okay with it. I mean, we can’t really do anything with their scheduling, right?

I really like the fate/ series. It has this… Unique storytelling. A unique setting with unique characters, it was a unique fantasy with dark subtleties. You won’t find anything like it. And its universe is quite rich. It took a timeline and generations to show the journey in this epic story. I won’t dive deeper unto it, because it would defeat the purpose of watching the show and knowing it for yourself, you know?

As the usual, the studio ufotable did an excellent job with the art quality. The backgrounds are awesomely detailed. Even minor details are perfected. Hair movement without a doubt received the blessing from the heaven. Characters look great in this episode. Rin (pictured above) looked great. I’ve got used to her new look now.

Saber also looks great. She is portrayed here better than Fate/Zero in my opinion. If you’ve played the game (which is great), you’d find her bust to be faithful to the original source material. No, I didn’t noticed her chest first.


What I really do like is Shirou’s improved character design. He looks better and is more aligned to his character in my opinion, compared to the 2006 Deen attempt.
And as usual, the animation is top notch. Especially with this scene:


DAT ASS. Seriously, ufotable, that is a fine job for fan service. I don’t usually like fan service especially on a series with a meat and story like this, but it raised my spirits up. I liked it. Good job.

I like how they emphasized this scene, showing the pendant again. If you’re interested, this is a very important plot device.
This episode, following the source material faithfully, would feature the appearance of a recurring important character, Kotomine Kirei. Now, if you’ve watched Fate/Zero already, you will know this character and his likely role and motivation in this chapter. If you didn’t, the better. If you’re planning to watch the prequel, do it after finishing this sequel. Trust me, it will make more sense and you’ll appreciate the story more.





The scene’s lighting, if I remember from the visual novel, is quite different. It was much more brighter. But I’m fine with subtle changes; after all this is an adaptation. And I liked the change. It adds more to the dark atmosphere. It fits the aura that Kirei brings when he enters the spotlight. It is important to note that subtle notions in the character conversations here are important. The dialogue here is important to remember. You can be patient in the infodump here; infodumps are the necessary evil to be immersed in and understand this epic story.


That face though. I actually like how they portrayed Rin here. It emphasizes her character more.


But what makes this episode great (aside from Rin) is the cliffhanger at the end of the episode. God I hate love cliffhangers! Damn you ufotable for delaying berserker I can’t wait for the fight scene Ilya appears along with Berserker.


Overall, absolutely great episode. Even though it doesn’t feature a battle unlike the first prior two episodes, the great animation, attention to details and conversation already makes up for it. Expect Ilya and Berserker next episode in action. Next episode will be great, and must not be missed.

Late look on episodes 0 and 1 coming up.


Thoughts: Lollipop Madness

Just last week if I remember correctly, Google announced the next version of the Android Operating System, Android 5.0 Lollipop. It follows last years’ KitKat, which is somewhat like Windows 8 in Microsoft analogy. Lollipop, is the next major overhaul change since Ice Cream Sandwich, boasting more flatter design called Material design (this trend must have started 2-3 years ago… so familiar…), performance and stability boost, better notification handling, “better” multitasking (which is just, you know, a visual upgrade), and other small, under-the-hood improvements. This update can be like Windows 10 in Microsoft analogy.

Now, let me talk about a couple of things concerning this news.

The name. I was kinda bummed here. They obviously chose the most obvious of all sweet things! I thought Key Lime Pie was already great, which turned out to be version 4.4 KitKat. They should have continued the trend that starts with Gingerbread, Honeycomb, Ice Cream Sandwich and Jellybean. Not only those are not that remotely popular (for all around the world; reality check), they are also unique, so Lollipop broke that sacred naming convention. About KitKat, don’t ask why.

This part is terrible. Why the heck is it that when it comes to its design, the irony is that it doesn’t even come to the low-end devices, and more importantly, those old flagship devices, where it is needed the most? It was designed to be more optimized in lesser memory, have a more efficient, faster binary runtime that requires lesser memory (in the form of ART), better battery optimization in the form of baked-in greenify-like feature in the system, and for ART that’s supposed to lessen processing load.

So, clearly it carried the banner that started with KitKat that said lesser fragmentation and uniformity across devices. Wait, that is the supposed intention? Then why is my Galaxy Nexus isn’t supported? They missed a great chance to explore the power and possibilities of these new operating systems by making them available to those not-so-old, capable devices.

Now, reasons for these are apparently obvious – Galaxy Nexus having no updated drivers for the kernel, OEM and carriers not updating older devices, unavailability of support for third-party hardwares, low storage spaces for older devices because ART takes more space (which can be solved through external storage), money and profitability – but not taking the chance to let these perfectly capable devices, these very same devices that gets the most benefit, to get a lick and suck to the oh, so delicious Lollipop (It wasn’t made intentionally perverse in anyway), felt kinda frustrating. It could have cement more footings for android; it could have benefit Google and its partners, the developers, the whole freaking ecosystem.

Community developers had made KitKat to work with Galaxy Nexus, and I wouldn’t be surprised if they did the same thing for Lollipop.

And, some of the initial roll-up for Lollipop is the new devices that come with it (obviously) which is the Nexus 6 and Nexus 9, and coming weeks later are Nexus 5, Nexus 4, Nexus 10, Moto X, and even freaking Nexus 7. Yeah, that device from 2 years ago, earlier than Nexus 4. See the possibility?

This is a long post, actually a rant post, which is unusual for me, but this is just a side effect of my excitement on this Android release. Especially on the thought that my Galaxy Nexus could get Lollipop after it was given a new breath of life lately through community developed updated kernel and drivers. I’d continue to watch the community from the shadows and maybe I can share more information regarding these events.


Hello Citizen

As you can see, citizen, the site is still under construction. Blog posts will be composed of my thoughts about anime-tion (News, episodes and series I watch, and related things), around things I stumble around the vast Network, together with topics about PC games, softwares, Linux, Windows, programming, linguistics, Japanese, tutorials on things, music, uhh J-music, philosophy, random thoughts, randoms and randoms, the Life, etc., so look forward for it? Your choice, citizen, visitor.