Saya hanya pernah membaca pengalaman mereka yang pernah mencoba mendapatkan paket layanan telemedisin dari Kementerian Kesehatan RI. Ada yang bilang lancar, ada yang bilang lambat. Dan, saya putuskan untuk mencoba mendapatkannya.
Berbekal NIK ini, akan ditentukan apakah hasil pemeriksaan sudah ada ada dalam database layanan ini atau belum. Saya masukkan NIK saya, ternyata NIK saya ditemukan, lengkap dengan status bahwa saya masuk dalam kriteria untuk mendapatkan layanan telemedisin.
Sesuai instruksi, saya lakukan konsultasi secara daring melalui aplikasi. Saya pakai aplikasi Halodoc, karena beberapa opsi yang sudah ada, Halodoc memang cukup sering saya gunakan.
Last week, I finally decided to upgrade my iPhone 5 to iOS 8 Beta 4. When the iOS Beta 1 was available, I took the risk to have it installed. But, it was too disappointing for too many bugs and errors. I'm excited about the upcoming iOS 8 features, and I want to try some of the features. There is a discussion thread at MacRumors Forum which lists the application compatibility on iOS 8. Anyway, I have lots of apps installed right now. If you're not sure about having the iOS Beta, you can wait for the official release.
I have some applications that are not running well, and one of them was WhatsApp. It keeps crashing. I can accept the fact that some other applications are broken or crashed. But, WhatsApp is an app that I use on daily basis. After searching for solutions, there are two popular ways to fix this issue:
The main reason for the crashes is typographic ligature. For those of you who didn't get what it is, don't fret, we didn't either. Turns out it has something to do with two letters being read as one syllable. Ex: letter combos like ff, fi, ffi, fii, will make WhatsApp crash.
What I found was that WhatsApp crashed when I typed some words or there are some words that are already in the databasefile. So, I followed the instructions and had everything solved. I want to reproduce the solution based on my experience.
I need to download two applications: iExplorer and Navicat for SQLite. Both are paid applications but the trial version are available. After I had it installed, these are steps I did. Anyway, WhatsApp iCloud setting should be turned off.
Open iExplorer — your iPhone should be connected, of course — and navigate to Apps > WhatsApp > Documents. Export the ChatStorage.sqlite file by right-clicking on the file and choose the export destination of your choice. You will need this file later. Having the backup for this file is advisable. So, after exporting this file, duplicating this file won't hurt.
Open Navicat for SQLite and import the ChatStorage.sqlite from the previous step. Navigate to Query and add a new query. Paste the query below, and Run it.
set ZTEXT = replace( ZTEXT, 'ff', 'f f')
where ZWAMESSAGE.ZTEXT like '%ff%';
set ZTEXT = replace( ZTEXT, 'fi', 'f i')
where ZWAMESSAGE.ZTEXT like '%fi%';
set ZTEXT = replace( ZTEXT, 'fl', 'f l')
where ZWAMESSAGE.ZTEXT like '%fl%';
CREATE TRIGGER insert_Ff AFTER INSERT ON ZWAMESSAGE
SET ZTEXT = replace( ZTEXT, 'ff', 'f f')
WHERE ZWAMESSAGE.ZTEXT like '%ff%';
CREATE TRIGGER insert_Fi AFTER INSERT ON ZWAMESSAGE
SET ZTEXT = replace( ZTEXT, 'fi', 'f i')
WHERE ZWAMESSAGE.ZTEXT like '%fi%';
CREATE TRIGGER insert_Fl AFTER INSERT ON ZWAMESSAGE
SET ZTEXT = replace( ZTEXT, 'fl', 'f l')
WHERE ZWAMESSAGE.ZTEXT like '%fl%';
Your ChatStorage.sqlite has been updated. The next thing you need to do is bring the file back to the iPhone using iExplorer. Move it to the same place and if you're asked to replace the file, just replace the file.
My previous errors with WhatsApp was fixed immediately. But, it seems that the errors still occur under different situation. The most common problem is that WhatsApp still keep crashing when I type some words in the window. For now, the temporary solution works, and let's wait the official update from WhatsApp team. I'm sure they will fix it once iOS 8 is available.
A month ago, I migrated this blog commenting system to DISQUS and I notice that I got zero spam. Great! Previously, I used Akismet and it also worked great. Akismet can identify comment spams but the they still entered the system database.
I know, this blog doesn't have a huge amount of traffic. But for a low traffic website, Akismet detected hundreds (and sometime thousands) of comment spams — according to the Akismet statistics in my blog. Not good. Thinking of using DISQUS for my other blogs I maintain.
Today, Yahoo! and Nokia announced a worldwide strategic alliance to extend the reach of their industry leading online services and offer people rich experiences that keep them connected to their world and the world around them.
Building on more than five years of collaboration, Nokia and Yahoo! ® will leverage each others' strengths in e-mail, instant messaging and maps and navigation services, to provide consumers with access to world-class experiences on both PC and mobile devices.
I use Flickr — and I'm really enjoying it. Sometime, I take advantage of its geo-location feature. I can put my photos into map. You can do it manually, or automatically using geo-location meta data captured from your mobile device. I did it using my mobile device. Flickr photos with geo-location information will be integrated with Yahoo! Map. You can see my Flickr map page to see it in action. Is it good? Yes, but not that good. Why?
When I had my photos with location information, they're not placed at the correct information. So, I have to edit their location in the map.
Yahoo! Map does not have much details about my hometown, Jogjakarta. Especially, when it comes to street names. For example, my photo taken in Malioboro Street, it's detected as it was taken in other area, and it's not even close.
I remembered that I have put my photos into correct location. But for some reasons — I don't know why — the location was changed. I hope I'm wrong with this. The zoom effect or something, I don't know.
With the new partnership I mention above, I hope I can see improvements. Ovi Maps has a great database of location, and it works really well. I know, sometime it has some mistakes on the street naming, but… still, it's a great tool.
Today, I tried the upcoming WordPress 3.0 distribution. It's not yet released. I installed WordPress 3.0 Beta 2. I do this because I want to know whether I will have some WordPress installations upgraded or not, to find the possibilities and considerations.
The installation process is similar to the previous versions, but I think it's improved now. After you fill in the database information, usually you will need to provide website name/title, and email address. The installation process will create “admin” as the first user, with randomly generated password. Here are some new fields during the installation process.
Better? Better. Previously, I usually modify the “admin” username directly from database manager — I'm using phpMyAdmin. Some people think that it's a good practice to remove/change the default administrator login in the system. Now, you can have whatever username for the administrator.
Previously, the first thing you will need to do after you have your WordPress installed is changing the randomly generated password, since it's not easy to remember. Setting up password during installation should be a time saver.
I haven't dug any other features like the multi-site, custom menus, and other things offered in this distribution. Later.
Today, I tried another WordPress plugin called “Automatic WordPress Backup”. This plugin will help blog owners to create backup remotely to Amazon S3 service. Since I'm using it and pretty satisfied with the billing usage, I installed it at some WordPress-powered blogs I maintain.
I use one of the available buckets under my account. For this bucket, I set its ACL (Access Control List) to private, of course. After this plugin installed and activated, I only needed to put my Access Key ID and Secret Access Key.
I decided not to include all files for my backup. I only need the database and uploaded contents. After the settings were saved, I simply hit the backup button. The process depends on the disk and database usage. I found that it was pretty fast. One of my backup files was around 300 MB, and it only took less than 5 minutes to complete the process. Also, the backup file was compressed. This should be useful to cut the usage process as you only need to store a single file for each backup.
The backup files will be automatically delivered to my Amazon S3 bucket and when the process completed, I can see the backup history. To download the backup, I only need to click on the backup links.
The backup links are built using pre-signed URLs so that only the account holder (or someone who knows the URLs) can download them.
Now, the question: Is it — deleting its Twitter — a smart move? Is it the best option? I think, it's not. Let's figure out why the account was closed.
VIVAnews wanted to get another account, and announce it as its official account. When it was published, I couldn't find any link of it at their site, or something mentioned that it was official.
They (people at VIVAnews?) want to do it better in the future.
They want to “remove” people's comment.
I think, rather than closing/deactivated its account, the account holder should stop the auto-update and show that they're listening. They can do it by removing its feed(s) from Twitterfeed. Then, they give respond also via Twitter. Why? Because it's the medium. They can ask for feedback, and how they can make it better next time.
It can be a better counter for the negative comments on Twitter. If they think that closing account will remove the negative comments, they're wrong. It's still accessible in Twitter database, unless people who wrote tweets delete them. See these screenshots: one and two. Those screenshots were taken, even the referenced account has been deleted.
Now, will they join Twitter again? I'm curious.
I'm maintaining a pretty big forum. It has a great amount of traffic, AND huge database size. Right now, it has a remote backup server. The optimization is always challenging. Anyway, vBulletin upgrade process was easy. The forum I maintain used vBulletin 3.6.x when it was firstly installed. Right now, it's using the latest stable release.
The first thing I did before upgrading is to backup its database. Using web-based database management tool like phpMyAdmin is easy. We can export and store it in minutes. BUT, in some cases, it takes more time if we have a large database. So, I use the other method: using the backup script.
When we download vBulletin, there is a backup script included in the distribution. It's under do_not_upload directory. The file is vb_backup.sh. The first thing we need to do is to edit this script, to locate the configuration file. After that, we only need to execute this command: ./vb_backup.sh backup
It will generate a backup file using this pattern: databasename-dd-mm-yy.sql.gz. Just keep the file into the safe place (outside public directory always recommended), and start upgrading. All done.
I have Greasemonkey installed on my Firefoxbrowser. After I heard the news about inserting Twitter real-time search directly on Google search page, I gave it a try. Visit userscripts.org to get the Greasemonkey script.
What about the results? It seems that this script is useful. Having search results from two different sources: Google and Twitter. Twitter is known for its social search because people really involved in giving answers, solution and other info.
On the other hand, Google has numerous search results — of cours, it's the search engine. But, who gives the most relevant results? Is it Google, or Twitter? Well, both will give search results only if they find the matching keywords/phrases. Twitter might be more updated because our search is pulled out from its database. Google might not give the best search query results, but it offers more data.
Google might win, Twitter too. Who's the winner? We decide.
So, if you're using WordPress for your blog/website, it is time to upgrade. You'll love it. :) As usual, if you do not want to take risk, backup your database first. Just in case you want to go back to your “current” WordPress version. After that, get WordPress 2.7. Anyway, related to this new version, if you have time, there are some notes. At least, these are for me. It might work for you too.
I have been dealing with vBulletin for almost a year now. I manage a vBulletin installation for my friend at Fashionese Dailyforum. Anyway, Fashionese Daily forum have used other forum/discusion engines like punBB and MyBB. It's now using vBulletin 3.7.3 Patch Level 1.
It's a pretty busy-traffic forum anyway. In average, there are 1,000 new posts everyday. According to forum stats, there are 500 – 600 online users during the prime ours (registered and guests). From the very beginning, I try to maintain its performance so that the forum is available.
Based on many articles about vBulletin optimization, here are what I did: