4 April 2017
For web browser:
- Install addons: uBlock Origin, Google search link fix, DownThemAll!, Disconnect, Zotero.
- Install new browser: Qupzilla.
4 April 2017
For web browser:
I copied here some first lines from that page:
The GNOME Desktop project (GNU Network Object Model Environment) http://bananoid.nuclecu.unam.mx/gnome
End of copying.
Ade Malsasa Akbar <email@example.com>
I am not a lawyer, and here I act only as a regular computer user that just mentioning texts from Microsoft Windows 10 license. This article lists the restrictions on the users from Windows 10 license (retail or oem). In other words, this article collects what you are forbidden to do towards Windows according to Windows 10 license. I try to show the restrictions as many as possible here but not complete of course, because I avoid the things I don’t know here. I accept comments here but please stand for the users freedom, not merely absolute monopoly for the sake of the vendor. Continue reading
Ade Malsasa Akbar <firstname.lastname@example.org>
I am not a security expert, I am just a regular user of GNU/Linux operating systems. I want to revive this blog again with much more intense free software awareness materials than before. And in this article I want to explain in a very simple way why free software is secure to non-technical users of GNU/Linux and free software.
I want to emphasize generally two questions here, “is free software secure?” and “is nonfree software secure?” to give any newcomer in GNU/Linux community understand why they need to reject nonfree software because of its insecurity nature. Continue reading
Let us promote Open Document Format (ODF). The only reason I write this article is because the confusions of Microsoft Document Format (OOXML) brought by Microsoft Office against Open Document Format (ODF) brought by LibreOffice (and companions). The another reasonable reason for me is no exact match in search engine I found for “support open document format” keywords even until today. So I need to explain shortly why it is important to support ODF (and another open formats) followed by mentioning many important link resources for that. So please use ODF, use LibreOffice (or its companions), use them as far as we can. Then promote them. Propagate them so another one will use them either. I hope this article will be widely useful.
This article is a short collection of the reasons why ODF is important and why we need to avoid OOXML usages. Why we need to use LibreOffice (or its companions) and why we need to avoid Microsoft Office usage. I’m talking in Free Software (and Open Source) scope. So keep inside this scope if you want to comment please.
Open Document Format (ODF, OpenDocument) is an open format for digital documents. It consists of ODT for word processor, ODS for spreadsheet, ODP for presentation, and some more. It is popular to be LibreOffice’s default document format. It is open format comparable to Microsoft Document OOXML (DOCX/XLSX/PPTX). This is non-technical description.
Open Document Format for Office Applications (ODF) is an OASIS Consortium‘s standard format based on XML for word processor, spreadsheet, and presentation applications which has been accepted as ISO standard ISO/IEC 26300. ODF is based on Sun Microsystem’s document format for OpenOffice.org. Technical documentation of Open Document Format is can be downloaded below. Technical specification of ODF can be downloaded below. This is technical description.
For more detailed explanation about ODF, refer here:
Because ODF is the most vendor-neutral open format for digital documents[TDF, OOXML]. It means no one patented the format specification, it is royalty-free format, no single vendor can lock the format of the document files, it means anyone permitted to create any software without patent risk forever, and it means it is readable/writable in any application worldwide.
LibreOffice and its companions. They are Free Software, such as:
They are safe to use. And their native document formats are safe also.
Office Open XML (OOXML) is digital document format from Microsoft for word processors, spreadsheets, and presentations. It consists of mainly three formats: DOCX, XLSX, and PPTX. They are popular for being default document format in Microsoft Office 2007 and later. This is non-technical description.
Office Open XML (OOXML) is a XML-based document file format from Microsoft for mainly word processors, spreadsheets, and presentations applications. This format standardized by ECMA (ECMA-376) then by ISO & IEC (ISO/IEC 29500). Technical specification of Office Open XML can be downloaded in http://www.ecma-international.org/publications/standards/Ecma-376.htm. This is technical description.
For more detailed explanation, see below or see section 1 above.
Please read more appropriate links stated below explaining how dangerous patent is. I suggest you to read sequentially number by number below.
No. Every big community and company in GNU/Linux scope aware about this problem. Please read their defense policies against software patents.
Outside them, there are also organizations to dealing with patent problems against Free Software/Open Source. These are not all, but just what I can collect for now.
No. There are many special organizations formed to face these problems. Whether they are developing software to support ODF, or they do fundamental things about ODF, or they do educational purposes to promote ODF. They are:
I maintain about a dozen of blogs, both in Indonesian and English, and all of them talk about GNU/Linux. As a real newbie, I have written probably more than 500 articles (including ebooks) about GNU/Linux within them and outside of them. Recently I found many of my GNU/Linux friends in Indonesia excited about using Archlinux. They love Archlinux bleeding edge style of distributing software packages, they said it is rolling release. Apparently I was excited too in the way of AUR, where my friends can get newest version of same program I use directly. Archlinux gave them more advantages than Ubuntu (official or PPA) in this case. Archlinux’s bleeding edge style, I describe it personally as forever LTS, not waiting (not freezing) for stable package to release a new package. I take that concept into my new writing style. I call it bleeding edge posting. This article is also a bleeding edge post.
After seeing bleeding edge way of Archlinux, recently I thought I must take that way to write. So I fire up my old blog (restava) to bear my new style of writing. I call this style bleeding edge posting. I don’t wait my writing for long-time editing. I post my posts directly. A bleeding edge post of me is an article which is containing at least a title and a sentence. But every post contains exactly one single idea, any new idea I find, so I don’t need to be frustrated when I find an idea and I must post it quickly. A bleeding edge post is usually finished in one time sitting duration. The main advantage of bleeding edge posting is I don’t need to wait to post any new idea where waiting is a very frustrating thing for a writer like me. It is a big win, where I can provide myself ideas collection in one place so I can make more long-editing posts in another blogs based on bleeding edge posts in bleeding edge blog. It is just similar thing between Fedora (bleeding edge*) and Red Hat Enterprise Linux (conservative edge**). My restava blog is “Fedora”, and my another blogs are “Red Hat Enterprise Linux”. Another advantage is I will never forget any of new ideas anymore. Another advantage of doing bleeding edge posting is I can fill my blog with more posts every month. If you are a writer, especially in GNU/Linux scope, bleeding edge posting saves your time so much.
Well, I coined my own style bleeding edge posting about one year ago. It starts with my restava. I proofed I like this style so much. It gives me more convenient way of writing. I felt comfortable so much with this style. So, I began to spread this style into my another blog. Not just restava. I did it on desaininkscape, I did it here and inside this article too.
Yes, I admit that tutorial needs more times to write. So basically I can’t write tutorial in bleeding edge style. I must write tutorials in a very careful way, very comprehensive way. Every tutorial should be correct, should be free from errors. Yes, I place my tutorials in my conservative edge blogs especially my main blog. My main blog is just one. But because I have already accustomed with bleeding edge style, I can write long articles as technical GNU/Linux tutorials. Actually they are intended to be personal notes only but anyone can consider them as tutorials. I have few examples here and here. Yes, bleeding edge style can be used as a way to write comprehensive tutorials. Surprise.
If you are a distribution developer, you probably will laugh at me. I know it’s funny, though. But truly Archlinux bleeding edge style is the source of this style. Probably you have more proper terms than bleeding edge posting and have using it before me. Please, you can let me know.
*) I describe Fedora as bleeding edge to compare quickly, to make sense quicker. I know Fedora prefer to be credited as leading edge. To sum it up, bleeding edge = risky while leading edge = not risky. Thanks for alunux @ #ubuntu-indonesia to point me.
**) I describe Red Hat Enterprise Linux as conservative edge just because I don’t know the antonym of bleeding edge. I don’t find it anywhere. If you know, please let me know.
Yes, because WordPress is open source software.
Open source software = free of charge.
Free of charge = I don’t need to pay.
I don’t need to pay = less stress in my mind.
Less stress in my mind = easy to use.
So WordPress is very easy to use. I have used WordPress since 2008 for blogging and enjoyed. Have fun!