.codingthings.[com]. software things.
I have those domains listed below expiring soon. If you are interested in one or more of them, let me know. There might be a tiny little fee involved (most likely, I will give them away for free).
I had a few minutes of nothingness in my hands today and decided to extract a list(actually a set) of English words ending with some tlds [com, us, co, ws, ca, org, biz, me, net].
Of course, many of the good ones are taken, but someone may find something useful out of this list.
You will find 4800+ almost meaningful domain names below.
The word list is from http://www.orchy.com/dictionary/index.html
i.e. “afri.ca”
(TLD, WORD, DOMAIN)
biz,showbiz,show
ca,abaca,aba
ca,acustica,acusti
ca,africa,afri
ca,alpaca,alpa
ca,america,ameri
ca,anasarca,anasar
ca,angelica,angeli
ca,Antarctica,Antarcti
ca,aponeurotica,aponeuroti
ca,areca,are
ca,Arica,Ari
ca,armonica,armoni
ca,Armorica,Armori
ca,arnica,arni
ca,asarabacca,asarabac
ca,aspca,asp
ca,atlantica,atlanti
ca,Attica,Atti
ca,ayahuasca,ayahuas
ca,bacca,bac
ca,Barca,Bar
ca,barranca,barran
ca,basilica,basili
ca,bibliotheca,bibliothe
ca,boca,bo
ca,Boudicca,Boudic
ca,brassica,brassi
ca,britannica,britanni
ca,Broca,Bro
ca,bucca,buc
ca,ca,
ca,cachuca,cachu
ca,caduca,cadu
ca,caeca,cae
ca,cahinca,cahin
ca,cainca,cain
ca,Calderca,Calder
ca,Capablanca,Capablan
ca,carica,cari
ca,carioca,cario
ca,Casablanca,Casablan
ca,Cauca,Cau
ca,ceca,ce
ca,circa,cir
ca,Cirenaica,Cirenai
ca,cloaca,cloa
ca,coca,co
ca,Corsica,Corsi
ca,coulibiaca,coulibia
ca,Cuenca,Cuen
ca,Cuernavaca,Cuernava
ca,Cyrenaica,Cyrenai
ca,Dacca,Dac
ca,decca,dec
ca,diptyca,dipty
ca,Dominica,Domini
ca,econometrica,econometri
ca,elastica,elasti
ca,erica,eri
ca,erotica,eroti
ca,exotica,exoti
ca,fanatica,fanati
ca,felucca,feluc
ca,fica,fi
ca,Fonseca,Fonse
ca,formica,formi
ca,franca,fran
ca,gastrica,gastri
ca,Gorica,Gori
ca,Guernica,Guerni
ca,harmonica,harmoni
ca,helvetica,helveti
ca,hemorrhagica,hemorrhagi
ca,hepatica,hepati
ca,hippobosca,hippobos
ca,Huesca,Hues
ca,ileoceca,ileoce
ca,Inca,In
ca,indica,indi
ca,informatica,informati
ca,ithaca,itha
ca,Jamaica,Jamai
ca,japonica,japoni
ca,jessica,jessi
ca,judaica,judai
ca,karyotheca,karyothe
ca,koulibiaca,koulibia
ca,Legnica,Legni
ca,lexica,lexi
ca,Lorca,Lor
ca,lorica,lori
ca,Lucca,Luc
ca,maiolica,maioli
ca,majolica,majoli
ca,Majorca,Major
ca,Malacca,Malac
ca,Mallorca,Mallor
ca,maraca,mara
ca,marasca,maras
ca,mathematica,mathemati
ca,Mecca,Mec
ca,medica,medi
ca,melaleuca,melaleu
ca,Menorca,Menor
ca,Merca,Mer
ca,mesoceca,mesoce
ca,mica,mi
ca,minorca,minor
ca,mollusca,mollus
ca,monica,moni
ca,Musca,Mus
ca,myrica,myri
ca,noctiluca,noctilu
ca,Oaxaca,Oaxa
ca,oca,o
ca,onchocerca,onchocer
ca,ootheca,oothe
ca,opaca,opa
ca,orca,or
ca,paca,pa
ca,Pachuca,Pachu
ca,pacifica,pacifi
ca,paralytica,paralyti
ca,phthisica,phthisi
ca,pica,pi
ca,pinacotheca,pinacothe
ca,plica,pli
ca,Podgorica,Podgori
ca,polacca,polac
ca,polonica,poloni
ca,portulaca,portula
ca,publica,publi
ca,rca,r
ca,Rebecca,Rebec
ca,replica,repli
ca,republica,republi
ca,rica,ri
ca,Roca,Ro
ca,Salamanca,Salaman
ca,santonica,santoni
ca,sca,s
ca,sciatica,sciati
ca,sclerotica,scleroti
ca,seneca,sene
ca,silica,sili
ca,spca,sp
ca,spermatheca,spermathe
ca,spica,spi
ca,spirocerca,spirocer
ca,Subotica,Suboti
ca,Tacna-Arica,Tacna-Ari
ca,Talca,Tal
ca,tapioca,tapio
ca,theca,the
ca,theriaca,theria
ca,Titicaca,Titica
ca,Toluca,Tolu
ca,tunica,tuni
ca,turcica,turci
ca,Utica,Uti
ca,uwca,uw
ca,veronica,veroni
ca,verruca,verru
ca,vesica,vesi
ca,viatica,viati
ca,vinca,vin
ca,vomica,vomi
ca,ymca,ym
ca,yucca,yuc
ca,ywca,yw
co,acapulco,acapul
co,alfresco,alfres
co,alnico,alni
co,amoco,amo
co,Angelico,Angeli
co,arco,ar
co,Armco,Arm
co,banco,ban
co,beccafico,beccafi
co,bianco,bian
co,bronco,bron
co,bunco,bun
co,calamanco,calaman
co,calico,cali
MiaCMS yet had another release a few days ago. MiaCMS 4.6.5 release has a few cool additions to it. Here is a list of things happened in the latest MiaCMS release.
The MiaCMS team is pleased to announce the immediate availability of version 4.6.5. This release fixes old bugs and adds a good bit of new and/or enhanced functionality. In addition to the release itself we have launched the new miacms.org site and the redesigns of our forum and wiki.
Here are the release cliff notes:
1. Cache Fixes & Enhancements
2. Enhanced Statistics & Poll Result Charting
3. New Templates, Site Designs, & the Official Logo
4. External Library Updates
5. Enhanced Commenting & Akismet (Spam Blocker)
6. Performance Improvements & Dynamic YUI Loader
If you’re using MiaCMS 4.6.4, or a Mambo 4.6x family CMS, I would surely recommend you upgrade to Mia 
Here are a few screen shots;
http://miacms.org/index.php?option=com_wrapper&Itemid=46
Yesterday, I exchanged a few emails with a G1 user, who contacted me through Android Market Application. Here goes the short but to the point email chain;
from Thndr <his email>
to my email here
date Tue, Dec 9, 2008 at 8:06 PM
subject Txtract – SMS BackupWtf is so good about ths shit fone? It can’t download crap. Going back to. My real fone. A waste of money.
from my email here
to Thndr <his email>
date Tue, Dec 9, 2008 at 8:12 PM
subject Re: Txtract – SMS BackupSorry, but you’re barking at the wrong tree. We’re not with Google, or with the Android Team, or affiliated with your GSM Operator
You can voice your concerns about G1 at http://forums.t-mobile.com/tmbl/
Here comes the best part.
from Thndr <his email>
to my email here
date Tue, Dec 9, 2008 at 8:19 PM
subject Re: Txtract – SMS BackupDoesn’t matter. Wtf kind of crap fone is this when you wait for geeks to develop programs? Going back to my real fone. This shit is worthleaa.
Whatever many may think, I think and believe Android platform is great and G1 is a good phone. And really doesn’t require that much of a brain power to operate that device.
I recently across this post on http://forum.mambo-foundation.org. I’ve been keeping a close eye on the project after I stripped myself off my official Mambo Foundation duties. The post below is truly saddening and it’s not even funny for someone who has some idea of what’s going on inside.
Informal Survey – what can we do to improve the team and community?
In April 2001, Mambo became open source under the GPL – its our foss birthday month right now! Over time, and particularly in the last three years, Mambo has undergone a lot of changes. 2 1/2 years ago we went through the biggest change of all with the Joomla! fork.At the moment, the team is going through a restructuring so that we are set up properly to take Mambo forward into the future. The way the team worked in 2005 worked well for bringing Mambo back from potential disaster. We have made a few changes along the way but we know we can do better.
One of the things we are looking at doing is taking development discussions out into a mailing list that anyone can join and can contribute ideas to (and even code suggestions). Do you think this is a good idea? If you are a developer, would doing this encourage you to participate?
What else should we look at doing? Are there any barriers to your contributions that we may not be aware of?
The team works hard at being here, on the forums and part of our community. We want Mambo to be inclusive and friendly, and to encourage contributions. How can we improve this?
Share your thoughts here please (constructive only – we want this thread to be something of value that we can use for improving things, not an opportunity for criticism that would only discourage the team).
I’ve been an active member of the Mambo Foundation, QA & Release Team Lead at some point, and took over the Core Development Team Lead after Chad‘s departure. Being known as a patient person, Mambo’s internal political dynamics even got to me, resulting in a not so nice resignation letter. Funny it is, I personally and with Chad collaboratively accomplished more than six months of work if we were to stay with the foundation, in a week.
Al takes over the reigns after my core team departure, and in less than a month, he gives up too. And knowing Al, his resignation letter was probably a bit more colorful than mine.
Now, let’s go back to the drawing board for a second and pop two questions.
Why would three Team Leads depart a big FOSS project in 4 months?
And why the board is still looking for a solution by doing informal public surveys?
I guess, we’ll all just sit tight and watch the fireworks.
Application Market Place for Android based phones is a funky place. The commenting system is truly jacked up. I saw many nasty and disturbing comments left by users. Many discussions around the matter can be seen here, just search for “comments”.
From a developer’s perspective it’s extremely sad to be trashed by a bunch of bozos. Almost feel lucky that our stuff was not trashed that bad. Fingers crossed. The interesting part on the matter is Google’s reluctance. It looks like they recently started cleaning up some of those comments; I see less and less. Come on Google, how difficult could it possibly be to integrate a profanity filter !
I didn’t intend to bitch about the epic fail of Google’s Android Market commenting system. It is what it is and it will stay as it is until they fix it.
This one, on the right is a recent comment which is left for Txtract . I find it sorta amusing and witty. A different kind of compliment (if it really is a compliment). “victory and female genitalia to you“ . Oh well! Thanks to you “punkofevil”, for your good wishes. Wishing the same back at ya
And Joanna, sorry that you have to do something like that.
Google, Google; when will you implement the “paid” applications in the Android Market !
Here is some piece-meal code for folks looking for information about how to implement a sort-of-a-timer and GUI update in Android based applications.
Some initial definitions;
1 2 3 | private Handler handlerTimer = new Handler(); private static final int UPDATE_STUFF_ON_DIALOG = 999; //this is a true arbitrary number. |
Init the timer at some point. Perhaps on “onCreate”, or where ever you need it.
1 2 | handlerTimer.removeCallbacks(taskUpdateStuffOnDialog ); handlerTimer.postDelayed(taskUpdateStuffOnDialog , 100); //set a 100 milisecond delay for the initial post |
The Runnable thread that will possibly do some lengthy operation;
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | private Runnable taskUpdateStuffOnDialog = new Runnable() { public void run() { /* Do some lengthy stuff here !!! */ // handling be in the dialog // don't mess with GUI from within a thread Message msg = new Message(); msg.what = UPDATE_STUFF_ON_DIALOG; handlerEvent.sendMessage(msg); //Do this again in 30 seconds handlerTimer.postDelayed(this, 30000); } }; |
taskUpdateStuffOnDialog task will post the message to the main dialog’s event handler, where we will finally do some GUI stuff.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | private Handler handlerEvent = new Handler() { @Override public void handleMessage(Message msg) { switch (msg.what) { case UPDATE_STUFF_ON_DIALOG: { // have a go at your GUI stuff here. enable/disable stuff, flash things, change text... } break; default: { super.handleMessage(msg); } break; } } }; |
That’s it.
A quick update on the blog URL.
I changed http://wp.ocszone.com to http://blog.ocszone.com . “wp” subdomain did stand for WordPress, and didn’t connect well with the current concept of the site. It was once intended to be a WordPress extensions demo site. Not anymore. I intend to use this site as a full-time blog. Thus the name change
Link exchange between the sites just don’t cut it anymore. “Cross-site information sharing” paradigm is growing into a greedy monster requiring new ways to expose your content. RSS has been holding up really good in that front. Given that you can put together – mash up- a website filled with thousands of articles in a matter minutes; it seems like, RSS over-accomplished its task. So what’s next ?
Today, core Mambo and Joomla! are both lacking good RSS facilities. You can only share your “Front page content” via RSS in Mambo (probably the same for J!). If you are keeping only one content item with some “never-updated-flashy” short content, your RSS feed is technically useless to the rest of the world. You can find a good RSS extension, which would cover that scenario.
What if you want to expose more from your CMS site ?
Answer:
With the addition of the Brilaps REST API, MiaCMS, Mambo, Joomla! will allow for advanced external interaction. Meaning that interaction with the site and its content no longer has to occur directly through normal browsing methods. For the first time you can start to consume Mambo’s internals as external services via the data type of your choosing (i.e.) JSON, XML, or Serialized PHP.
Brilaps REST API, MOStlyREST provides the com_rest as a base library that takes care of the message receipt and packaging back to the caller. Brilaps also released a few other goodies that goes along with the base implementation that the other 3rd party developers can use as samples or extend from those. com_rest_content and com_rest_stats components sit on top of the base component(com_rest) and expose your “top ranked”, “most popular” articles, or articles for certain sections/categories, or your site stats to any application that’s capable of parsing some simple XML.
Why do want to REST enable your Mambo or Joomla! site? One simple answer to that is, larger audience. Larger audience is both audience as in visitors and utilizing applications.
A few examples:
that you can distribute to your visitors to track or search your site at the comfort of a desktop application. I believe, REST enabled MiaCMS, Mambo and Joomla! sites will change the landscape of the content management landscape covered by MiaCMS, Mambo and Joomla!. Indeed, that’s a pretty large landscape. I guess, we just sit back and watch what’s gonna happen next…
For questions and comments about the REST API for MiaCMS, you can visit http://forum.brilaps.com
*Same article is also posted on Chad’s site; http://www.opensourcepenguin.net . If you’d like a take a peek at some other cool stuff, browse on.
I recently started writing this article study about Free Open Source Projects and their ways; internally and externally.
My initial goal was to analyze the internal and external dynamics of a FOSS project, especially constitutionalizing the internals, the identify the issues being faced, possible recommendations, outcomes and such.
Now, I am wiping what I’ve done so far, and opening this into a collaborative article. Feel free to add your opinions in the comments section. Once it’s ready to become an actual article/case study, I will contact the posters individually asking for their blessing about adding their pieces in the finalized paper.
Thanks in advance for your input.
