You can add the RSS feed of a youtube channel with the Tiny Tiny RSS bookmarklet, it's working for most channels, but not all for a reason I don't understand yet.
If you don't know it, take a look at Shaarli[1], it's a bookmarking web app that allows you to share your bookmarks via RSS, you can add tags and comments, but you can also have "notes" without a link that can be used as microblogging posts.
It's a project from Sebsauvage[2] (an old school french blogger), who wanted to build a social network around the RSS technology.
I know there are projects around it to aggregate multiple shaarli and use it as an actual social network based around sharing links with RSS. I didn't search about it, but it seems that shaarlo[3] is one of them. EDIT: actually, projects like this are listed in shaarli's documentation[4].
EDIT2: tt-rss-shaarli seems to be what you want, Tiny-Tiny RSS with Shaarli, an aggregator with a sharing/commenting functionality.
You should try undo tree (http://www.dr-qubit.org/undo-tree.html), it's a must have extension which brings proper undo-redo and a tree visualisation of history with diffs and many other options.
I use zim (but planning to switch to org-mode which seems a lot more powerful), but any good note taking software should do it.
I put most of the things in my homepage with a tree of check-boxes (tasks) divided in 3 sections:
- To-plan : idea dumping, less than 5 words or just an URL for example
- To-do : tasks to do
- Urgent : tasks with a close deadline, should contain not many tasks, or be empty if possible.
When I start a project (moving a task from "to plan" to "to do"), I add a page with multiple mostly static info on it, like a small summary, final goals, commands I need to be up as fast as I can, important URLs.
When I add tasks to a project, I try to make them as small as possible (maximum a few hours for a task), most of the tasks are broken into multiple sub-tasks, that sometimes lead to a new project. Like with git, commits (tasks) should be atomic and when done it must still compiles (no "work in progress" state when I'm done with a task). It's also easy then to find common sub-tasks or sub-projects.
The first tasks on a project are almost always research, compare the solutions to pick the best, prepare and document the working environment, and are often longer than the rest.
New tasks/projects go on top on my tree, so when I have to pick one, I read my list from bottom to up.
I sometimes rearrange sub-trees to prioritize them.
When I want to do things, I pick tasks I will work on with these criteria :
- What I'm motivated to do right now (most important actually)
- How useful it will be (for other projects, to ease my life, ...)
- How fast it will be, regarding the free time I might have in the near future.
That way, my (too many) projects all go forward at the same time, I optimize the time I spend on them (with "how to get up to work" instructions), and I always have something to do that I like.
Some of my projects get done from time to time. But most do not and it's OK, because I always come up with new ideas so there is always things to add, and the project is never really over.
I don't personally need it, but one way to be stimulated with this flow is to keep your done tasks checked, in an archive page to not pollute your main page for example, and with dates if you are organized, so you can look back at what you achieved from time to time.
PS: I think it's close to GTD, but I didn't take time to read about it to be sure.
I used to install Arch by hand, then I discovered ArchFI and ArchDI scripts. They do every basic step of the install wiki, and if you need you can do some things manually from another console.
With those, I go from an empty machine to a fully functional system with total control/feedback on what is installed (Arch way) in about one hour (most of the time is waiting for packages to download and install).
Setting up your own email server will bring you into the wonderful world of big email corporations not delivering your emails until you subscribe to their whitelist with, for some of them, subscription fee.
Back in the time, I had this problem with sending emails from my private server to yahoo or microsoft (hotmail, live.com, etc...), both refusing to deliver my emails to their clients as I could be a potential evil spammer.
For the subscription fees, a few weeks ago I saw a price chart for <I don't remember which company, probably Microsoft> about how much you have to pay them depending on your situation and how many emails you plan to send to their servers. Unfortunately I didn't find this page again.
I think the best option is to go for a paid service with a good privacy policy. It will cost you a lot less in time and probably in money. Also, they will probably be more reactive than you in case of problem, and more aware about security.