Welcome

menu

Detik Pos Indonesia

Jumat, 20 Juli 2012

Detik Pos Indonesia


Panwaslu: Politik Uang Jokowi Tak Terbukti

Posted: 19 Jul 2012 11:24 PM PDT

DETIKPOS.net - Tudingan tim sukses Foke-Nara terhadap tim sukses Jokowi-Ahok atas praktik politik uang telah diselidiki Panitia Pengawas Pemilu (Panwaslu) DKI Jakarta. Namun, tuduhan itu kemungkinan besar gugur karena tidak ada saksi atau bukti yang kuat.

Ketua Panwaslu DKI Jakarta, Ramdansyah, mengatakan bahwa pihaknya telah melakukan konfirmasi pada tertuduh, yaitu tim sukses Jokowi-Ahok mengenai tudingan politik uang ini. Pihak Jokowi-Ahok mengakui bahwa memang ada pemberian uang sebesar Rp75.000.

"Memang ada pemberian uang Rp 75.000 tapi itu untuk honor saksi dan 43 orang yang menjadi saksi ini menerima bayaran sehari sebelum hari H," kata Ramdansyah, di Kantor Panwaslu, Jalan Suryopranoto, Jakarta, Jumat, 20 Juli 2012.

Menurut dia, pemberian uang untuk membayar saksi ini dilakukan pada 10 Juli sekitar pukul 15.00 WIB. Sementara serangan fajar yang dituduhkan terjadi pada 11 Juli sekitar pukul 03.00 WIB sampai 06.30 WIB di RW 007 Kelurahan Pegangsaan.

"Ini saksinya bukan yang menerima juga bukan yang melihat. Dia hanya bilang 'katanya'. Bukti foto yang diberikan juga tidak menggambarkan adanya transaksi politik uang itu," ujar Ramdansyah.

Menurut dia, aduan ini kemungkinan besar akan digugurkan karena tidak ada bukti dan saksi yang kuat. Setelah dilakukan penelusuran, bukti yang mendukung tuduhan tim Foke-Nara juga tidak ditemukan.

Sebaliknya, tim sukses Jokowi-Ahok memberikan bukti berupa catatan pembayaran honor saksi berjumlah 43 orang dengan besaran Rp 75.000 untuk masing-masing saksi. Bukti ini untuk menjawab kecurigaan dari penuduh.

Sebelumnya, anggota tim sukses Foke-Nara wilayah Jakarta Pusat, Jan Awalisi dan Ketua RW 07 Kelurahan Pegangsaan, Jakarta Pusat, Mahmuri mendapat laporan dari warga yang didatangi seseorang yang membagikan uang Rp 50.000-Rp 75.000.

Uang itu, menurut laporan tersebut, diselipkan dalam baju kotak-kotak sehingga yang memberikan diduga sebagai anggota tim sukses pasangan calon nomor urut tiga. (ren)

Sumber : http://us.metro.news.viva.co.id/news/read/337233-panwaslu--politik-uang-jokowi-tak-terbukti

Blog Berita Indonesia


Rilis Shollu 3.09.. Program pengingat Sholat gratis

Rilis Shollu 3.09.. Program pengingat Sholat gratis


Rilis Shollu 3.09.. Program pengingat Sholat gratis

Posted: 19 Jul 2012 10:05 AM PDT

Setelah lebih dari 4 tahun belum ada perkembangan atau Update terbaru, saat ini Alhamdulillah, di awal (menjelang) Ramadhan 1433 H ini, Shollu versi baru berhasil di rilis. Shollu 3.09 ini menyertakan berbagai perbaikan penting serta penggantian file atau suara adzan dengan kualitas yang lebih baik dari sebelumnya. Rilis ini juga sebagai hadiah Ramadhan kepada penunjung [...]

[ Ini merupakan ringkasan artikel , selengkapnya silahkan klik judul link diatas ]


Belajar Ngeblog di BLOG kurnia septa

Rabu, 18 Juli 2012

Belajar Ngeblog di BLOG kurnia septa

Link to Belajar Ngeblog di BLOG

Cara Setting Permalink di Blogspot Agar SEO

Posted: 18 Jul 2012 06:12 AM PDT

Sudah tahu belum? Blogger.com atau blogspot memberikan fitur baru di layanan ngeblog gratisannya, yaitu kita bisa menentukan sendiri permalinknya. Jika dulu kita tidak bisa menyetting permalink dan sering terpotong. Permalink adalah URL (link) permanen yang mengarah pada halaman posting kita. Dulu, permalink ini sudah ditentukan oleh blogspot berdasarkan judul, yang panjangnya terbatas sehingga


Official Google Webmaster Central Blog

Selasa, 17 Juli 2012

Official Google Webmaster Central Blog

Link to Google Webmaster Central Blog

On web semantics

Posted: 16 Jul 2012 10:42 AM PDT

Webmaster level: All

In web development context, semantics refers to semantic markup, which means markup used according to its meaning and purpose.

Markup used according to its purpose means using heading elements (for instance, h1 to h6) to mark up headings, paragraph elements (p) for paragraphs, lists (ul, ol, dl, also datalist or menu) for lists, tables for data tables, and so on.

Stating the obvious became necessary in the old days, when the Web consisted of only a few web sites and authors used tables to code entire sites, table cells or paragraphs for headings, and thought about other creative ways to achieve the layout they wanted. (Admittedly, these authors had fewer instruments at their disposal than authors have today. There were times when coding a three column layout was literally impossible without using tables or images.)

Up until today authors were not always certain about what HTML element to use for what functional unit in their HTML page, though, and "living" specs like HTML 5 require authors to keep an eye on what elements will be there going forward to mark up what otherwise calls for "meaningless" fallback elements like div or span.

To know what elements HTML offers, and what meaning these elements have, it's necessary to consult the HTML specs. There are indices—covering all HTML specs and elements—that make it a bit simpler to look up and find out the meaning of an element. However, in many cases it may be necessary to check what the HTML spec says.

For example, take the code element:

The code element represents a fragment of computer code. This could be an XML element name, a filename, a computer program, or any other string that a computer would recognize.

Author-controlled semantics

HTML elements carry meaning as defined by the HTML specs, yet ID and class names can bear meaning too. ID and class names, just like microdata, are typically under author control, the only exception being microformats. (We will not cover microdata or microformats in this article.)

ID and class names give authors a lot of freedom to work with HTML elements. There are a few basic rules of thumb that, when followed, make sure this freedom doesn't turn into problems:

Advantages of using semantic markup

Using markup according to how it's meant to be used, as well as modest use of functional ID and class names, has several advantages:

  • It's the professional thing to do.
  • It's more accessible.
  • It's more maintainable.

Special cases

"Neutral" elements, elements with ambiguous meaning, and presentational elements constitute special cases.

div and span offer a "generic mechanism for adding structure to documents." They can be used whenever there is no other element available that matches what the contents in question represent.

In the past a lot of confusion was caused by the b, strong, i, and em elements. Authors cursed b and i for being presentational, and typically suggested a 1:1 replacement with strong and em. Not to stir up the past, here's what HTML 5 says, granting all four elements a raison d'être:

b "a span of text to be stylistically offset from the normal prose without conveying any extra importance, such as key words in a document abstract, product names in a review, or other spans of text whose typical typographic presentation is boldened" <p>The <b>frobonitor</b> and <b>barbinator</b> components are fried.
strong "strong importance for its contents" <p><strong>Warning.</strong> This dungeon is dangerous.
i "a span of text in an alternate voice or mood, or otherwise offset from the normal prose, such as a taxonomic designation, a technical term, an idiomatic phrase from another language, a thought, a ship name, or some other prose whose typical typographic presentation is italicized" <p>The term <i>prose content</i> is defined above.
em "stress emphasis of its contents" <p><em>Cats</em> are cute animals.

Last but not least, there are truly presentational elements. These elements will be supported by user agents (browsers) for forever but shouldn't be used anymore as presentational markup is not maintainable, and should be handled by style sheets instead. Some popular ones are:

  • center
  • font
  • s
  • u

How to tell whether you're on track

A quick and dirty way to check the semantics of your page and understand how it might be interpreted by a screen reader is to disable CSS, for example using the Web Developer Toolbar extension available for Chrome and Firefox. This only identifies issues around the use of CSS to convey meaning, but can still be helpful.

There are also tools like W3C's semantic data extractor that provide cues on the meaningfulness of your HTML code.

Other methods range from peer reviews (coding best practices) to user testing (accessibility).

Do's and Don'ts

Don't Do Reason
<p class"heading">foo</p>
<h1>foo</h1>
For headings there are heading elements.
<p><font size="2">bar</font></p>
<p>bar</p>    p { font-size: 1em; }
Presentational markup is expensive to maintain.
<table>    <tr>      <td class="heading">baz</td>    </tr>    <tr>      <td>scribble</td>    </tr>  </table>
<h1>baz</h1>  <p>scribble</p>
Use table elements for tabular data.
<div class="newrow">foo</div>  <div>1</div>  <div class="newrow">bar</div>  <div>2</div>
<table>    <tr>      <th>foo</th>      <td>1</td>    </tr>    <tr>      <th>bar</th>      <td>2</td>    </tr>  </table>
Use table elements for tabular data.
foo bar.<br><br>baz scribble.
<p>foo bar.</p>  <p>baz scribble.</p>
Denote paragraphs by paragraph elements, not line breaks.

Lihat informasi lebih detail PC (Komputer) dg Sys Information

Lihat informasi lebih detail PC (Komputer) dg Sys Information


Lihat informasi lebih detail PC (Komputer) dg Sys Information

Posted: 16 Jul 2012 04:27 PM PDT

Sebagai pemilik komputer (PC atau laptop), sebaiknya kita juga lebih tahu informasi (spesifikasi) lebih detail komputer yang kita miliki. Saya dahulu sudah pernah membahas tentang Speccy yang cukup praktis untuk hal ini, tetapi ada alternatif lain yang tidak kalah bagus untuk dicoba, yaitu Sys Information. Sys Information merupakan program gratis (juga open source) untuk melihat [...]

[ Ini merupakan ringkasan artikel , selengkapnya silahkan klik judul link diatas ]


Belajar Ngeblog di BLOG kurnia septa

Jumat, 13 Juli 2012

Belajar Ngeblog di BLOG kurnia septa

Link to Belajar Ngeblog di BLOG

Membuat Widget RSS Newsfeed Blog

Posted: 13 Jul 2012 06:01 AM PDT

Apa itu RSS? RSS adalah sebuah file berformat XML untuk sindikasi yang digunakan situs web berita dan blog. RSS mengizinkan kita untuk berlangganan kepada situs web atau blog yang menyediakan umpan (feed) RSS. Blog yang dikelola biasanya isinya selalu diperbarui secara reguler dalam bentuk postingan. Untuk memanfaatkan teknologi ini kita membutuhkan layanan pengumpul. Pengumpul bisa dibayangkan


Official Google Webmaster Central Blog

Official Google Webmaster Central Blog

Link to Google Webmaster Central Blog

New Crawl Error alerts from Webmaster Tools

Posted: 12 Jul 2012 03:12 PM PDT

Webmaster level: All

Today we're rolling out Crawl Error alerts to help keep you informed of the state of your site.

Since Googlebot regularly visits your site, we know when your site exhibits connectivity issues or suddenly spikes in pages returning HTTP error response codes (e.g. 404 File Not Found, 403 Forbidden, 503 Service Unavailable, etc). If your site is timing out or is exhibiting systemic errors when accessed by Googlebot, other visitors to your site might be having the same problem!

When we see such errors, we may send alerts –- in the form of messages in the Webmaster Tools Message Center –- to let you know what we've detected. Hopefully, given this increased communication, you can fix potential issues that may otherwise impact your site's visitors or your site's presence in search.

As we discussed in our blog post announcing the new Webmaster Tools Crawl Errors feature, we divide crawl errors into two types: Site Errors and URL Errors.

Site Error alerts for major site-wide problems

Site Errors represent an inability to connect to your site, and represent systemic issues rather than problems with specific pages. Here are some issues that might cause Site Errors:
  • Your DNS server is down or misconfigured.
  • Your web server itself is firewalled off.
  • Your web server is refusing connections from Googlebot.
  • Your web server is overloaded, or down.
  • Your site's robots.txt is inaccessible.
These errors are global to a site, and in theory should never occur for a well-operating site (and don't occur for the large majority of the sites we crawl). If Googlebot detects any appreciable number of these Site Errors, regardless of the size of your site, we'll try to notify you in the form of a message in the Message Center:

Example of a Site Error alert
The alert provides the number of errors Googlebot encountered crawling your site, the overall crawl error connection rate for your site, a link to the appropriate section of Webmaster Tools to examine the data more closely, and suggestions as to how to fix the problem.

If your site shows a 100% error rate in one of these categories, it likely means that your site is either down or misconfigured in some way. If your site has an error rate less than 100% in any of these categories, it could just indicate a transient condition, but it could also mean that your site is overloaded or improperly configured. You may want to investigate these issues further, or ask about them on our forum.

We may alert you even if the overall error rate is very low — in our experience a well configured site shouldn't have any errors in these categories.

URL Error anomaly alerts for potentially less critical issues

Whereas any appreciable number of Site Errors could indicate that your site is misconfigured, overloaded, or simply out of service, URL Errors (pages that return a non-200 HTTP code, or incorrectly return an HTTP 200 code in the case of soft 404 errors) may occur on any well-configured site. Because different sites have different numbers of pages and different numbers of external links, a count of errors that indicates a serious problem for a small site might be entirely normal for a large site.

That's why for URL Errors we only send alerts when we detect a large spike in the number of errors for any of the five categories of errors (Server error, Soft 404, Access denied, Not found or Not followed). For example, if your site routinely has 100 pages with 404 errors, we won't alert you if that number fluctuates minimally. However we might notify you when that count reaches a much higher number, say 500 or 1,000. Keep in mind that seeing 404 errors is not always bad, and can be a natural part of a healthy website (see our previous blog post: Do 404s hurt my site?).

A large spike in error count could be because something has changed on your site — perhaps a reconfiguration has changed the permissions for a section of your site, or a new version of a script is crashing regularly, or someone accidentally moved or deleted an entire directory, or a reorganization of your site causes external links to no longer work. It could also just be a transient spike, or could be because of external causes (someone has linked to non-existent pages), so there might not even be a problem; but when we see an unusually large number of errors for your site, we'll let you know so you can investigate:

Example of a URL Error anomaly alert
The alert describes the category of web errors for which we've detected a spike, gives a link to the appropriate section of Webmaster Tools so that you can see what pages we think are problematic, and offers troubleshooting suggestions.

Enable Message forwarding to send alerts to your inbox

We know you're busy, and that routinely checking Webmaster Tools just to check for new alerts might be something you forget to do. Consider turning on Message forwarding. We'll send any Webmaster Tools messages to the email address of your choice.

Let us know what you think, and if you have any comments or suggestions on our new alerts please visit our forum.