억양 기호라고도 불리는 발음 구별기에 색을 추가하는 방법이 있는지 궁금하다면, 여러분은 올바른 위치에 있습니다! 왜요? 정답은 ‘예’이기 때문입니다. 그리고 제가 그 방법을 보여드리겠습니다.
다음과 같은 CSS 스타일을 만듭니다:
|
|
분음 부호를 diacritics
클래스 내에 배치합니다
|
|
알았어요!
다음은 예입니다:
|
|
CodePen를 통해서도 이용할 수 있습니다. 또는 test-repo: Noto Diacriticals Git 지점에서 간단한 테스트 페이지를 복제할 수 있습니다.
주의사항 : 네이버 파파고 신경번역
]]>링크 아이콘은 훌륭합니다. 링크가 무엇인지 독자에게 알립니다. 외부인가? 아니면 아마도 비디오? 링크를 클릭하면 다운로드가 시작됩니까? 아니면 기본 메일 프로그램이 열립니까? 링크 아이콘은 또한 개발자 또는 콘텐츠 작성자가 링크 또는 링크가 없는 것을 쉽게 찾도록 도와줍니다.
링크 아이콘은 10년 전에 Wikipedia로 시작되어 대중화되었습니다 1. 모두가 자신의 웹사이트와 블로그에 링크 아이콘을 추가할 CMS 플러그인을 찾고 있었습니다. 당시 방식은 작은 ‘.png’ 이미지 파일을 아이콘으로 사용하는 것이었다. 근데 오늘? Unicode 이모티콘을 사용하고 적절한 이모티콘을 사용할 수 없는 경우에만 .svg
를 사용합니다.
이 포스트에서는 MARKDOWN 링크를 통해 HUGO에서 지원하는 링크 아이콘을 추가합니다. 렌더 후크의 기능 덕분에 단축 코드가 필요하지 않고 일반 일반 [text](https://example.com "Title")
링크만 있으면 됩니다 2.
2022년 6월 17일:
sftp://
프로토콜이 ftp 범주로 이동됨findRE
로 전환[text](./path/to/content/)
및 [text.ext](./path/to/file.ext)
구문2022년 5월 27일:
링크 아이콘을 추가하려면 다음 단계를 따르세요.
이 디렉토리 /layouts/_default/_markup/
에 render-link.html
이라는 파일을 만듭니다.
이 코드를 복사하여 붙여넣습니다.
|
|
스타일시트 파일에 다음을 추가합니다.
|
|
.svg
아이콘 다운로드: link-icons.7z
출처(모두 공개 도메인):
나열된 소스에서 핫링크할 수 있습니다. 그러나 설정한 경우 정보가 없습니다.
/static/img/
폴더에서 .svg
파일의 압축을 풉니다.
다음 Markdown 링크
- 외부 링크
- [https://example.com/#fragment](https://example.com/#fragment "https://example.com/#fragment")
- 채팅
- [irc://](irc://example.com "irc://") | [ircs://](ircs://example.com "ircs://") | [irc6://](irc6://example.com "irc6://") | [xmpp://](xmpp://example.com "xmpp://") | [jabber://](jabber://example.com "jabber://") | [discord://](discord://example.com "discord://") | [skype://](skype://example.com "skype://")
- FTP
- [sftp://](sftp://example.com "sftp://") | [ftp://](ftp://example.com "ftp://") | [aftp://](aftp://example.com "aftp://")
- Magnet
- [magnet://](magnet://example.com "magnet://")
- Mail
- [mailto:](mailto:noreply@example.com "mailto:")
- 원격
- [telnet://](telnet://example.com "telnet://") | [ssh://](ssh://example.com "ssh://") | [git://](git://example.com "git://") | [svn://](svn://example.com "svn://") | [bzr://](bzr://example.com "bzr://")
- Tel
- [tel:](tel:123-456-7890 "tel:")
- 서적
- [doi://](doi://example.com "doi://") | [.epub](https://example.com/file.epub ".epub") | [.mobi](https://example.com/file.mobi ".mobi") | [.pdf](https://example.com/file.pdf ".pdf")
- 문서
- [.odt](https://example.com/file.odt ".odt") | [.sdw](https://example.com/file.sdw ".sdw") | [.sxw](https://example.com/file.sxw ".sxw") | [.uof](https://example.com/file.uof ".uof") | [.uot](https://example.com/file.uot ".uot") | [.doc](https://example.com/file.doc ".doc") | [.docx](https://example.com/file.docx ".docx")
- 텍스트
- [.txt](https://example.com/file.txt ".txt") | [.csv](https://example.com/file.csv ".csv")
- 프레젠테이션
- [.odp](https://example.com/file.odp ".odp") | [.fodp](https://example.com/file.fodp ".fodp") | [.sdd](https://example.com/file.sdd ".sdd") | [.sdp](https://example.com/file.sdp ".sdp") | [.sxi](https://example.com/file.sxi ".sxi") | [.uop](https://example.com/file.uop ".uop") | [.ppt](https://example.com/file.ppt ".ppt") | [.pptx](https://example.com/file.pptx ".pptx")
- 스프레드시트
- [.ods](https://example.com/file.ods ".ods") | [.fods](https://example.com/file.fods ".fods") | [.sdc](https://example.com/file.sdc ".sdc") | [.sxc](https://example.com/file.sxc ".sxc") | [.uos](https://example.com/file.uos ".uos") | [.xls](https://example.com/file.xls ".xls") | [.xlsx](https://example.com/file.xlsx ".xlsx")
- 오디오
- [.flac](https://example.com/file.flac ".flac") | [.aac](https://example.com/file.aac ".aac") | [.mka](https://example.com/file.mka ".mka") | [.ogg](https://example.com/file.ogg ".ogg") | [.oga](https://example.com/file.oga ".oga") | [.opus](https://example.com/file.opus ".opus") | [.mp3](https://example.com/file.mp3 ".mp3") | [.mpa](https://example.com/file.mpa ".mpa") | [.mid](https://example.com/file.mid ".mid") | [.midi](https://example.com/file.midi ".midi") | [.wav](https://example.com/file.wav ".wav") | [.wave](https://example.com/file.wave ".wave") | [.wma](https://example.com/file.wma ".wma")
- 동영상
- [.av1](https://example.com/file.av1 ".av1") | [.webm](https://example.com/file.webm ".webm") | [.xvid](https://example.com/file.xvid ".xvid") | [.mkv](https://example.com/file.mkv ".mkv") | [.mk3d](https://example.com/file.mk3d ".mk3d") | [.ogm](https://example.com/file.ogm ".ogm") | [.ogv](https://example.com/file.ogv ".ogv") | [.divx](https://example.com/file.divx ".divx") | [.avi](https://example.com/file.avi ".avi") | [.mp4](https://example.com/file.mp4 ".mp4") | [.mpeg4](https://example.com/file.mpeg4 ".mpeg4") | [.mpv](https://example.com/file.mpv ".mpv") | [.mpeg](https://example.com/file.mpeg ".mpeg") | [.mpg](https://example.com/file.mpg ".mpg")
- 부제
- [.vtt](https://example.com/file.vtt ".vtt") | [.ttml](https://example.com/file.ttml ".ttml") | [.dfxp](https://example.com/file.dfxp ".dfxp") | [.srt](https://example.com/file.srt ".srt") | [.sub](https://example.com/file.sub ".sub") | [.sbv](https://example.com/file.sbv ".sbv") | [.scc](https://example.com/file.scc ".scc") | [.mks](https://example.com/file.mks ".mks")
- 실행 파일
- [.deb](https://example.com/file.deb ".deb") | [.apk](https://example.com/file.apk ".apk") | [.exe](https://example.com/file.exe ".exe") | [.com](https://example.com/file.com ".com") | [.msi](https://example.com/file.msi ".msi")
- 스크립트
- [.bat](https://example.com/file.bat ".bat") | [.sh](https://example.com/file.sh ".sh")
- 글꼴
- [.woff](https://example.com/file.woff ".woff") | [.woff2](https://example.com/file.woff2 ".woff2") | [.otf](https://example.com/file.otf ".otf") | [.ttf](https://example.com/file.ttf ".ttf") | [.ttc](https://example.com/file.ttc ".ttc")
- 압축 파일
- [.7z](https://example.com/file.7z ".7z") | [.7zip](https://example.com/file.7zip ".7zip") | [.tar](https://example.com/file.tar ".tar") | [.gz](https://example.com/file.gz ".gz") | [.gzip](https://example.com/file.gzip ".gzip") | [.bz2](https://example.com/file.bz2 ".bz2") | [.bzip2](https://example.com/file.bzip2 ".bzip2") | [.zip](https://example.com/file.zip ".zip") | [.rar](https://example.com/file.rar ".rar")
- 디스크 이미지
- [.img](https://example.com/file.img ".img") | [.iso](https://example.com/file.iso ".iso") | [.dmg](https://example.com/file.dmg ".dmg") | [.mds](https://example.com/file.mds ".mds") | [.mdf](https://example.com/file.mdf ".mdf") | [.mdx](https://example.com/file.mdx ".mdx")
- 이미지 편집
- [.xcf](https://example.com/file.xcf ".xcf") | [.psd](https://example.com/file.psd ".psd")
다음과 같이 렌더링됩니다.
URI(Uniform Resource Identifier) 체계의 공식 목록은 IANA 공식 웹사이트에서 확인할 수 있습니다. 3 그러나 discord://
및 bzr://
(2022-05-13 일자 IANA 문서 기준)과 같이 널리 사용되는 모든 URI 체계가 등록 및/또는 제출된 것은 아닙니다. 그럼에도 불구하고 이러한 인기 있는 등록되지 않은 URI 스키마가 위의 코드에 포함되었습니다.
유용하게 사용하시길 바랍니다!
[텍스트](https://example.com#fragment "제목")
에 내부 상호 참조 지원을 추가할 것입니다.]]>Hugo의 덜 일반적으로 사용되는 기능 중 하나는 렌더 후크입니다. 이 게시물에서는 렌더 후크를 사용하여 Markdown의 기본 링크 생성 방식인 [텍스트](https://example.com#fragment "제목")
에 내부 상호 참조 지원을 추가할 것입니다.
Hugo의 내부 상호 참조는 일반적으로 내장 단축 코드 {{< ref >}}
또는 {{% relref %}}
를 사용하여 수행되지만 Hugo 버전 0.62.0부터 1 알고 계셨습니까? 권장되는 방법은 렌더 후크를 사용하는 것입니까 2?
{{< ref >}}
및 {{% relref %}}
또는 그 변형은 과거의 것입니다.2022년 6월 17일:
[text](./path/to/content/)
및 [text.ext](./path/to/file.ext)
구문2022년 5월 27일:
[텍스트](./path/to/content/)
[text.ext](./path/to/file.ext)
이 디렉토리 /layouts/_default/_markup/
에 render-link.html
이라는 파일을 만듭니다.
아래 코드를 추가하세요.
|
|
그게 다야
|
|
[text](./path/to/content/)
형식은 현재 Hugo의 일부가 아닌 동일한 (하위) 도메인 아래 웹사이트의 다른 부분에 대한 링크를 생성하려는 경우에 유용합니다. 프로젝트. 이 형식은 Hugo markdown 링크에 링크 아이콘을 추가하는 방법도 설치된 경우 외부 링크 아이콘을 생성하지 않습니다.
[text.ext](./path/to/file.ext)
는 현재 Hugo 프로젝트 내부 또는 외부에서 동일한 (하위) 도메인에서 호스팅되는 다운로드 링크에 유용합니다.
|
|
|
|
|
|
파일 확장자가 없고 #fragment
가 있는 내부 링크는 잘못된 링크를 생성합니다.
|
|
또한 다음 형식에 유의하십시오.
|
|
위 대신 [텍스트](./path/to/file.ext)
를 사용하면 [link-icons.7z](./techmagus/dls/link-icons.7z)
가 다음과 같이 렌더링됩니다. link-icons.7z
위의 코드를 자유롭게 개선하고 커뮤니티에 다시 공유하십시오. 귀하의 웹사이트와 이름을 제공하여 적절하게 크레딧을 받으십시오.
Keybase offers a lot of features, there is end-to-end encrypted Chat, a free 250 GB File storage, a signed hosting, and the ability to easily sign any text, images, and the usual document files. However, there is one feature usually ignored and this feature was one of the hottest when Keybase first sent invites to testers. That is what I will guide you through today.
]]>Once again congratulations on creating a Keybase account. You have joined a growing number of people worldwide who have taken their privacy and security to the next level.
Keybase offers a lot of features, there is end-to-end encrypted Chat, a free 250 GB File storage, a signed hosting, and the ability to easily sign any text, images, and the usual document files. However, there is one feature usually ignored and this feature was one of the hottest when Keybase first sent invites to testers. That is what I will guide you through today.
A Keybase identity is a secure online representation of someone (a person) or some entity (an organisation). It lists all the verified online assets (social network accounts, domain names, microblog accounts) of the owner of the Keybase account.
By design, it is near impossible to gain an unauthorised access to any Keybase account without an active “device” (see our previous post). This generally give us the assurance that whoever is updating a particular Keybase account is the actual owner.
However, a bad element can simply create their own Keybase account to impersonate someone. This was solved in two ways by Keybase. The first is by adding third-party identities; and the second is by being followed by other verified Keybase users.
A third-party identity is an account well-known to be under the control of the Keybase account owner. This could be a Twitter account, a domain name, a Mastodon account, or any of the different services supported by Keybase.
By adding multiple third-party identities, a Keybase account’s trust factor—if we can call it that—increases. An impersonator will not be able to add the official Twitter account of their target under their fake Keybase account. They can add their own fake Twitter account or if they successfully gained unauthorised access to the official account. It becomes harder for an impersonator to establish trust to their fake Keybase account when the official one also added a well-known Mastodon account or the domain names he or she owns.
It is impossible for a fake Keybase account to acquire the same level of trust the official account have by that point. Check my Keybase account here and count how many third-party identities are listed. An impersonator will need to have access to all of those social media accounts and domain names before they can add it to their fake Keybase account. Unless they put a gun on my head, they will not be able to do it (especially since I also use two-factor authentication in those accounts).
It is quite simple, follow these steps.
See the verication tweet live.
Repeat the process for every third-party account you have which is supported by Keybase. If a third-party service is a shared account, for example domain names or corporate microblogging accounts, it is possible to have multiple Keybase accounts verified. Check the Mastodon account for the Kolverse Worldbuilding and Writing Project, there are two Keybase accounts which verified ownership of it: @VersesSpace@writing.exchange.
Let’s say your Twitter account was hacked or you no longer have access to it. It is imperative to revoke it from your Keybase account. Simple go back to your Keybase profile, click your Twitter account, and revoke it. What it means is you are officially declaring that Twitter account to be no longer yours and any posts from it did not come from you.
It is true there could be a delay to the timestamp when you disavowed your third-party identity to when it was actually compromised, however, remember that by the time we discover our account was compromised it is always after the fact. There is nothing that can be done in that regard other than to revoke it in your Keybase account so you have an official timestamp for record purposes (especially if later you are accused of the content posted by your compromised third-party identity).
When other Keybase users follows your Keybase account, they are automatically signing your profile or Keybase identity. A follower is virtually saying “I verify this account is who s/he claims to be and the third-party identities s/he added as of this date and time I also verified to be owned by this Keybase user”.
Whenever a Keybase user changed anything in their third-part identities, their followers can optionally verify those changes by visiting the account. If they do, they are signing it effectively saying “I have checked the changes in this account’s third-party identities and have confirmed it as valid”. The more Keybase users who follows and/or verify the changes, the higher the trust factor.
Getting your family & friends to follow your Keybase account and verifying changes in your third-party identities makes it very solid that your Keybase account is actually yours and those third-party identities are also actually yours and have full control. An impersonator or fake account will not be able to build this kind of trust level.
Again, what if a third-party identity was compromised? Revoke it. Your Keybase followers can then visit your profile and confirm the change. By doing so, they are signing or adding their Keybase signature into your revocation update. We can probably say they effectively stand as “witnesses” when you revoked your compromise third-party identity.
There you go. Add all those third-party identities into your Keybase account as a “verified identity” and get your family, friends, and followers to verify those changes. The higher the trust factor of your Keybase account, the stronger and more secure your digital identity becomes.
There are various software, apps, services, available which offers one, two, or maybe three features mentioned. However, there is one which is largely ignored, that is Keybase.
]]>Freedom, anonymity, privacy, & security, are the most important part of our lives, and this is especially true today as we move faster into the digital world. We need to secure our online communications to prevent anyone from listening. We need to prove the identity of the other person we are working with. We need an easy way to use encryption to keep private data from being seen by unauthorised individuals.
There are various software, apps, services, available which offers one, two, or maybe three features mentioned. However, there is one which is largely ignored, that is Keybase.
To put it simply, Keybase is a tool which makes it easier for regular users to do encryption and signing. Private stuff stays private. Accounts are secure against spoofing, phishing, and scamming.
It also helps in establishing which online accounts are officially owned by a Keybase user, effectively nullifying online attacks through impersonation.
In other words, every person who takes their freedom, anonymity, privacy, & security very seriously must have a Keybase account.
The first thing to understand is registration through a web browser is not possible by design and for security reasons. New users must download Keybase which is available in GNU/Linux, Android, iOS, and Windows: download Keybase here.
* We’re using Keybase for Android below, the process is the same regardless of platform.
Congratulations! You have successfully created a Keybase account and have taken your first step in establishing a way for others to prove your online identity beyond any reasonable doubt as well as to chat, share files, collaborate with your team, with a peace of mind everything is automatically end-to-end encrypted and signed.
Establishing a way for others to prove our online identity, chat with family & friends, and collaborate with teams, would be practically useless if we later can not login our account. In Keybase, each [re]-installation is considered a “new device” regardless if it was exactly the same device used.
A “device” in Keybase is simply an access point or a “device” where an account is logged-in.
Registering each devices creates another security layer, if a phone was stolen one can simply “Revoke” the device. If for some reason the account was not automatically logged-out, any actions made from the “Revoked” device is automatically invalid.
Let’s create a new paper key.
A Keybase paper key is technically a “device”. It’s main purpose is to give the account owner a way to confirm a “new device” if a registered literal device is not or no longer available.
Many new Keybase users skip this step, uninstalls Keybase, and later can no longer login because they are stuck in the “new device” process. Without an existing device logged-in to Keybase you can not confirm a “new device”. A paper key acts as an “existing device” to approve a “new device”. The used paper key can be optionally revoked and a new one created (a very good practice); or create a new paper key every three months (an even better practice).
There is another way to recover a Keybase account if a paper key is not available. The catch with this method is your Keybase account will be reset back to start, all confirmed online accounts, domain names, devices, teams, followers, following, will be removed; it is as if you created a new account. The reason behind this is if you no longer have access to any of your “devices” (including your paper keys if you created any), then it is assumed all of your devices were lost and/or compromised.
Welcome to Keybase! Before you start exploring Keybase, noticed how you were not asked to enter a password/passphrase? It is only used if you want to login via a web browser—which is not advisable—and if you prefer to auto-logout when you close the Keybase app (an added security; if you reinstalled Keybase it will be considered a “new device”). We will discuss this another day.
Here is a short guide on how to activate and use Baybayin-Buhid, Baybayin-Hanunoó, Baybayin-Tagalog, and Baybayin-Tagbanwa, using Google’s Gboard app.
Download the Gboard app from the Google Play Store and Apple App Store (not yet available for iOS).
Go to the Gboard settings
Go to Languages
Tap the “ADD KEYBOARD” button at the bottom of the screen
In the “Add keyboard” page, choose:
Optionally, add:
Then remove any other keyboard layouts which were automatically added.
If you can not find the keyboard layouts mentioned above, one possible reason is your Google Play Store account and/or unit is yet to receive an update push. Until then, joining the beta is the only way.
Still no Baybayin related keyboard layouts? The last option is for you to download the latest Gboard APK, which is not advisable. But if it is your cup of tea, then download here. Remember, it may not be compatible with your phone model!
Baybayin in Gboard is now available for everyone.
It was discovered that the Gboard app is automatically disabling the layouts if there are no font support in the system.
For example, manufacturers Samsung and MyPhone deleted the Noto Tagalog font in their Android 7 and Android 8 models but left Noto Buhid, Noto Hanunoó, and Noto Tagbanwa. This is the reason why Samsung and MyPhone users can not see the “Filipino (Baybayin)” Gboard layout.
The best way to test this is to open this article in your favourite mobile browser and check if you can see the following texts.
If you can not see one of those, then your mobile phone is missing the appropriate Noto font support for that script. This in turn will automatically disable Gboard support for it. It means it is time to switch to an “Android One” model.
Since I got my first ever smartphone, Samsung Galaxy Y (S5360), (and Android too) I was having some problems with calibrating phone’s compass. The compass applications I found in the Android Market instructs users to do a figure-8 wave. I did all kinds of figure-8 wave and well, nothing.
Until I found this video showing the one figure-8 method I haven’t tried - wrist movement. It is as simple as that, all I can do is laugh at myself for doing all the silly figure-8 movements I can think of.
Watch the video:
It works for all other phones with compass features like iPhone and Symbian based phones.
Why? Their current IPv6 implementation is currently in its testing phase. All IPv6 access must come from a reliable network that they have to pre-approve, this is the Google over IPv6 project.
]]>Google, the largest search engine today (and the “Microsoft” of the cyberworld), is slowly deploying IPv6 across their sites. But even if you are already connected to IPv6, you will still not get an IPv6 Google.
Why? Their current IPv6 implementation is currently in its testing phase. All IPv6 access must come from a reliable network that they have to pre-approve, this is the Google over IPv6 project.
So unless you are using a DNS with Google over IPv6 enabled, the only IPv6 Google website you will be able to use is ipv6.google.com. That’s sad! Especially if most of the sites you visit are still hosted on non-IPv6 enabled servers.
Fortunately, there are many good-hearted people and corporations in the world today offering free access to their IPv6 DNS. We have Gogo6.com’s Freenet6 DNS and Hurricane Electric’s Tunnelbroker.net DNS.
But how do we use these IPv6 DNS? Let me show you how.
Go to Synaptic (System -> Administration -> Synaptic Package Manager)
Search for “dnsmasq” and install it
Open a Terminal (Accessories -> Terminal)
Type:
|
|
Look for:
|
|
Change it to:
|
|
Look for:
|
|
Add the following after/below it:
|
|
Save and close the file
Still in the Terminal, type:
|
|
Look for:
|
|
Uncomment that line by removing the sharp (’#’) sign
Save and close the file
Still in the Terminal, type:
|
|
Before any other nameserver entries, add this:
|
|
Save and close the file
Still in the Terminal, type:
|
|
What happens is this: we are using dnsmasq to reroute all queries to google.com to HE’s IPv6 DNS which has been confirmed to be Google over IPv6 enabled. Any Google services that are not yet using IPv6 or not yet part of the project will simply use IPv4, like the YouTube entry we added (read: YouTube is the IPv6 team’s number one priority right now).
But if you are not using DHCP, then the DHCP edits you did previously will not work. Or if you are using NetworkManager to manage your connection settings, then it will only overwrite your resolv.conf file. Here’s what you should do to solve this:
Open your NetworkManager and go to your network/connection profile (example: eth0)
Open/edit it and go to the “IPv4 Settings” tab
In the “DNS servers:” field, simply add this before any other DNS entries you may have:
|
|
Click “Apply”, then close it.
This way, every time the NetworkManager connects and overwrites the resolv.conf file, it will always add 127.0.0.1 to the file. Just like in the DHCP edits you did above, it ensures that the listening IP being used by dnsmasq is the first DNS your system will check when you are browsing.
In your terminal type:
|
|
You should see something like this:
|
|
These are the Google sites and services tested to be accessible via IPv6 (as of this article):
Not yet accessible via IPv6:
As far as I know, it is not possible to host a “sub-folder” in another server, thus we can safely assume that all Google sites with this URL format: www.google.com/{sitename} are IPv6 enabled. However, Google sites and services that are using a subdomain.google.com URL or any other, can either be IPv6 already or not. Subdomains can easily be pointed to a totally different server somewhere in cyberspace.
For those who are still using Windows XP, you are out-of-luck. Even if you can add an IPv6 DNS, it will not work, I tried it myself and it was confirmed by Mikael Lind here.
Update for Windows XP users: I found a way to do it and I will be posting it here soon! The life of your too old OS just got a little bit longer.
For Windows 7 users, you will have to wait until I can get a Win7 OS or a machine that I can break. Or better ask the experts in IPv6 like the guys and gals of the gogo6 Community.
Update 2010-02-25: Sorry WinXP users you really have to upgrade to Windows 7. The method works but it is not consistent - sometimes it works, sometimes not. It is also very different per machine (it is weird!) even if you have everything duplicated perfectly.
It will only invite frustration and plenty of questions. Again, I recommend upgrading to Windows 7 if you want a consistent and stable IPv6 capability.
Update 2010-09-20: Google Sites, Google Translate, Google Earth, Google Moderator, and Google FeedBurner, are now all IPv6 enabled.
When this day comes, someone must start finding IP address owners who does not really need a static address and give it to someone who needs it seriously. We may even see owners starting to sell their extra IPs at a price far more expensive that what it is worth today.
]]>IPv6 or Internet Protocol version 6 is the answer to our IPv4 problem. What problem? By 2011 or 2012 (according to estimates), there will be no more IPv4 addresses left. This means that, anyone with a need to have a static IP address will not be able to get any for their project or service.
When this day comes, someone must start finding IP address owners who does not really need a static address and give it to someone who needs it seriously. We may even see owners starting to sell their extra IPs at a price far more expensive that what it is worth today.
But that will not happen, because two decades ago, the powers-that-be already started experimenting with IPv6 which will give us 2128 addresses. That is equivalent to 340,282,366,920,938,463,463,374,607,431,768,211,456 IPv6 Addresses, according to my Einstein brain calculation :p Or simply: 340 with 36 zeroes (I admit, I used a calculator).
Compare that to IPv4 which only have 232 or 4,294,967,296 IP addresses. It is a huge difference! IPv6 which use 128-bit addresses and IPv4 which is only 32-bit. Each computer in the world can now have its own IP Address and we are only scratching the surface of IPv6. In fact, if we subtract the number of IPv4 addresses we have, we still have 340,282,366,920,938,463,463,374,607,427,473,244,160 IPv6 addresses available.
I know you have plenty of questions but time is not on our side. What I am going to answer for you today is how you can start connecting to the IPv6 Internet without waiting for your ISP to start implementing it.
For this tutorial or How-To Guide, I am going to show you how I setup my Ubuntu Linux 9.10 “Karmic Koala” Linux Mint 11 “Katya” 64-bit (based on Ubuntu 11.04 “Natty Narwhal”). So let’s begin!
Go to Synaptic (System -> Administration -> Synaptic Package Manager)
Search for: miredo; gogoc; and radvd and install all three.
Open a terminal (Accessories -> Terminal)
Type:
|
|
Type:
|
|
If your main connection is not eth0
then change if_prefix=
accordingly
If you are setting this up on a workstation computer, then change host_type=router
to host_type=host
Type:
|
|
Update 2010-03-29: Additional step from Ubuntu 10.04 “Lucid Lynx” and up.
Still on your terminal, type:
|
|
Look for # CHECK_KEYFILE="yes"
and change it to CHECK_KEYFILE="no"
Update 2009-12-23: An update from Jeremy Duncan on setting up your Linux box as a router.
Make sure IPV6FORWARDING
is set to yes in /etc/sysconfig/network
like so: IPV6FORWARDING=yes
.
You are done! To test if your IPv6 is working do or visit the following:
In your terminal, type:
|
|
it should show something like this:
|
|
Open up your favorite browser and visit test-ipv6.com
and/or ipv6-test.com
and/or ip6.me
For one, Miredo/Teredo was developed only as a temporary gateway to the IPv6 Internet. In fact, it was set as the last access point when you have other IPv6 implementation like a tunnel broker.
Another reason is to have a static IPv6 address (even if your ISP gives you a dynamic IPv4 address). For this to work, you have to register an account over at Gogo6.com’s Freenet6 service (register here).
Then you have to edit your gogoc.conf, follow the instructions below:
Open a Terminal again
Type:
|
|
Type:
|
|
Adjust your existing gogoc.conf with this one:
|
|
Type:
|
|
You’re done! From now on, you will have the same IPv6 address everytime you connect to Freenet6’s network. However, do note that you still get a different static IP depending on which Freenet6 server you are connected. If you really want to connect to the exact same server simply change this configuration in your gogoc.conf
|
|
to:
|
|
But before you do that, please connect to Freenet6 at least once, so your gogoc daemon will have a list of servers to connect to and be able to choose the “best” one for you. Then set it up as instructed, and you’ll be connecting to that same “best” server everytime the gogoc daemon is (re)-started. Easy?
Welcome to the next generation of the Internet - the IPv6 world.
Firefox 3.6 “Final” was released today and one of the major addition is the support for the Web Open Font Format or “WOFF”. The result of a collaboration between the font designers Erik van Blokland and Tal Leming with help from Mozilla’s Jonathan Kew.
What is it for? How can you use it? By using the CSS2 @font-face (yes CSS2 not CSS3). This new format is promising because of the large number of support from the font creators and font foundries. Hopefully this will be the first font format that Microsoft® will accept for Internet Explorer browser other than their existing Embedded OpenType or “EOT”.
If IE9 supports WOFF, then this format will be the first cross-browser @font-face/webfont format. There is no question when it comes to Chromium/Chrome, Opera, and Safari, the problem with cross-browser technology is always with MSIE.
Update: Microsoft added WOFF support in Internet Explorer 9 Platform Preview 3.
So how can you start using WOFF? Just follow these simple steps:
|
|
And here’s what happens when a browser reads your font stylesheet:
The table below presents which font format is supported by the four major browsers - Chromium/Chrome, Firefox, Internet Explorer, Opera, and Safari. As you will see, no font format is supported across all five browsers except for WOFF… in the near future.
Microsoft’s EOT is out of the race, even though many font creators and foundries support it, the other four browsers are likely never going to support it. Then OTF, SVG, and TTF are out too because Internet Explorer is surely never going to implement it, and font creators/foundries do not like these formats for @font-face use.
That is where WOFF comes in. Commercial font creators and font foundries wants control (or restriction if you want it that way) to the fonts that can be used for the CSS @font-face rule.
Of course there are other advantages to WOFF like compression. WOFF is compressed, which site administrators will like because it eats less bandwidth. You can go check the fonts that came with your FontSquirrel generated font kit, WOFF is the smallest of them.
For now as with all new technologies, we have to wait until all major browsers adds support for WOFF. But that should not stop you from using it today. Just like with CSS3 and some HTML5, you can use it right now. It will save you time later if you do the update now than whenever you feel like to, which you will probably forget.
Chrome (WebKit) |
Firefox (Gecko) |
IE (Trident) |
Opera (Presto) |
Safari (WebKit) |
|
---|---|---|---|---|---|
EOT | No | No | v4.0 | No | No |
OTF | No | v3.5 | No | v10.0 | v3.1 |
SVG | v0.3 | No | No | v10.0 | v3.1 |
TTF | v2.0 | v3.5 | No | v10.0 | v3.1 |
WOFF | v5.0 | v3.6 | v9.0 | No | No |
If you see the Baybayin writing script below, then your browser supports one of the font formats - EOT, OTF, SVG, TTF, or WOFF. If not, then you should upgrade your browser because my font stylesheet captures all browsers. (At least from my testing, on two computers without any Baybayin fonts - it displays correctly on all the major browsers.)
Filipino-Baybayin: ᜀᜅ᜔ ᜊᜓᜃᜓ ᜀᜌ᜔ ᜉᜍ ᜐ ᜆᜂ ᜇᜑᜒᜎ᜔ ᜏᜎ ᜈᜅ᜔ ᜉᜓᜏᜒᜇᜒᜅ᜔ ᜋᜁᜈᜓᜋ᜔ ᜈ ᜄᜆᜐ᜔᜶
Filipino-Latin: Ang buko ay para sa tao dahil wala nang puwedeng mainom na gatas.
English: The coconut is for people because there is not enough milk to drink.
Filipino-Baybayin: ᜉᜓᜏᜒᜇᜒ ᜃᜅ᜔ ᜌᜓᜋᜋᜈ᜔ ᜇᜑᜒᜎ᜔ ᜐ ᜊᜄᜓᜅ᜔ ᜍᜓᜎᜒᜆ᜶
Filipino-Latin: Puwede kang yumaman dahil sa bagong roleta.
English: You can be rich because of the new wheel.
Enjoy!
Sources:
이 게시물에서는 콘텐츠의 언어를 올바르게 선언하는 방법에 대해 설명합니다. 이렇게 하면 번역 소프트웨어와 도우미 응용 프로그램, 그리고 종종 당연하게 여겨지는 이 HTML 속성에 의존하는 기타 기술에 친숙해질 수 있습니다. 우리의 이미지에서 볼 수 있듯이 모든 사람이 사용 된 스크립트를 볼 수 있지만 디지털 세계에는 사용 중인 글꼴이 없는 사람들이 있습니다. 당신과 내가 사용하는 것과 같은 브라우저를 사용하지 않는 사람들도 있습니다. 그것은 텍스트 전용 브라우저, 음성 브라우저 또는 점자 브라우저일 수 있습니다.
그런 다음 우리가 사용하는 언어와 스크립트로 콘텐츠에 적절하고 올바르게 태그를 지정하는 것이 적절합니다. LANG 속성을 많이 사용할 준비를 하십시오.
]]>이전 게시물에서 “Baybayin - 잊혀진 필리핀 이전 히스패닉 작문"에 대해 이야기했습니다. Unicode Standard 버전 5.0에서 “Philippine Scripts” 그룹 아래 Buhid, Hanunoo, Tagbanwa와 함께 추가되었습니다. 그러나 다른 언어와 스크립트로 작성된 콘텐츠를 어떻게 적절하게 작성하거나 표시해야 할까요?
이 게시물에서는 콘텐츠의 언어를 올바르게 선언하는 방법에 대해 설명합니다. 이렇게 하면 번역 소프트웨어와 도우미 응용 프로그램, 그리고 종종 당연하게 여겨지는 이 HTML 속성에 의존하는 기타 기술에 친숙해질 수 있습니다. 우리의 이미지에서 볼 수 있듯이 모든 사람이 사용 된 스크립트를 볼 수 있지만 디지털 세계에는 사용 중인 글꼴이 없는 사람들이 있습니다. 당신과 내가 사용하는 것과 같은 브라우저를 사용하지 않는 사람들도 있습니다. 그것은 텍스트 전용 브라우저, 음성 브라우저 또는 점자 브라우저일 수 있습니다.
그런 다음 우리가 사용하는 언어와 스크립트로 콘텐츠에 적절하고 올바르게 태그를 지정하는 것이 적절합니다. LANG 속성을 많이 사용할 준비를 하십시오.
웹 사이트를 만들 때 웹 사이트에서 사용되는 언어를 올바르게 선언하는 것이 중요합니다. 예를 들어 내 사이트에 다음을 사용합니다.
|
|
특히 ASCII 범위를 벗어난 문자를 사용하려는 경우 문자 집합을 선언하는 것도 중요합니다. 다음과 같이 보입니다.
|
|
모든 것을 합치면 기본 HTML이 되어야 합니다.
|
|
이제 파헤쳐보자…
HTML lang 속성은 선언된 요소 내에 포함된 콘텐츠의 언어를 정의합니다. 코드는 subtag 라고 하며 필리핀 독자의 경우 걱정해야 할 하위 태그 유형은 language-Script-REGION의 세 가지뿐입니다. 전체 형식: language-extended_language-Script-REGION-variant-extension-privateuse.
아래 표를 참조하십시오.
암호 | 언어 | 하위 태그 배치 |
---|---|---|
en | (일반) 영어 | language |
en-PH | 필리핀 영어 | language+REGION |
fil-Tglg | Baybayin의 필리핀 | language+Script |
bik-cts-Tglg | Baybayin 스크립트의 Pandan(북부 카탄두아네스) 방언의 Bikolano | language+extended_language+Script |
phi-Tglg-tsg | Baybayin 스크립트로 작성된 Tausug 필리핀 언어 | language+Script+variant |
특정 언어에 대한 하위 태그를 찾으려면 이전에 다른 웹사이트와 많은 공식 코드 목록을 확인해야 했습니다. 시간이 많이 걸리는 작업(일반적으로 한 번만 수행하면 됨), 맞습니까? 이제 최신 공식 하위 태그를 IANA 언어 하위 태그 레지스트리에서 찾을 수 있습니다. 이제 모든 유효한 하위 태그의 범용 소스입니다.
최신 목록(이 글을 쓰는 현재)에 따르면 필리핀과 관련된 하위 태그는 다음과 같습니다.
Tagalog
Bikol
Cebuano
Filipino/Pilipino
Hiligaynon
Iloko
Pangasinan
Pampanga/Kapampangan
Philippine languages
Waray
Buhid
Hanunoo (Hanunóo)
Tagbanwa
Tagalog
이제 필요한 하위 태그가 있으므로 모든 필리핀 언어 및 스크립트에 대해 올바른 lang
값을 코딩할 수 있습니다. 다음 예를 참조하십시오.
lang
값입니다. lang="en-PH"
lang="fil"
lang="tl"
lang="bik"
lang="ceb"
를 사용합니다.lang="hil"
lang="ilo"
를 사용합니다.lang="pag"
lang="pam"
lang="war"
lang="을 사용해야 합니다. 파이"
그런 다음 Baybayin 스크립트로 무언가를 작성하려면 스크립트 하위 태그 “Tglg"로 올바르게 묶어야 합니다. 형식은 다음과 같습니다.
lang="fil-Tglg"
lang="bik-Tglg"
lang="ceb-Tglg"
lang="phi-Tglg"
를 사용해야 합니다.lang="tl-Tglg"
하위 태그 코드가 없는 이유는 무엇인가요? Suppress-Script: Latn 으로 인해 IANA 언어 하위 태그 레지스트리에서 이전에 표시된 대로. 내가 그것을 올바르게 이해했다면 공식 표준에 따라 타갈로그 언어는 항상 라틴 문자로 작성되어야 함을 의미합니다. 그런 다음 lang=“tl-Tglg"가 잘못되었고 응용 프로그램에 이를 무시하거나 “Tglg” 스크립트 하위 태그를 삭제할 수 있는 옵션이 있다고 가정합니다. 이 경우 “fil-Tglg"를 사용하십시오.
dialects and macrolanguages를 타겟팅하려는 경우 배워야 하는 또 다른 하위 태그가 있습니다. ). ISO 표준 ISO-639-3에서 목록을 찾을 수 있습니다. . Bikolano를 예로 들어 보겠습니다. 사용할 형식은 language-extended_language-Script입니다.
lang="bik-bcl"
을 사용하십시오.lang="bik-bhk"
lang="bik-bto-Tglg"
lang="bik-cts-Tglg"
언어-extended_language-스크립트는 이 문서에서 아직 구현되지 않았습니다. lang 속성의 기본은 extended_languages를 포함하도록 업데이트되면 항상 IANA 언어 하위 태그 레지스트리입니다. * 그런 다음 필요한 곳에서 사용할 수 있습니다.
다음은 언어에 ISO-639-3 코드가 있고 ISO-639-2에서 언어 코드 “phi” 아래 또는 일부인 경우 phi 하위 태그가 사용됩니다. 이 하위 태그 코드는 집단 언어로 간주됩니다. 좋은 예는 다음과 같습니다.
lang="phi-krj"
lang="phi-mdh"
lang="phi-Tglg-mrw"
lang="phi-Tglg-tsg"
내가 사용한 형식이 language-extended_language-Script가 아니라 language-Script-variant라는 것을 눈치채셨을 것입니다. 내 추론은 간단합니다. phi 언어 코드는 실제로 언어가 아닙니다. 이 ISO 버전에서는 찾을 수 없는 다른 모든 필리핀 언어에 대해 ISO-639-2에서 “집합적인” 언어 항목이라고 합니다. 언어 표준. bik 언어 코드와 비교하면 ISO-639-2 및 ISO-639-3 모두에서 “매크로 언어"로 명확하게 표시되었습니다.
또한, 월드 와이드 웹 컨소시엄 또는 W3C에 따르면 매크로 언어의 방언은 즉시 작성되어야 합니다. 언어 하위 태그 뒤에. 즉, ISO-639-2 코드가 매크로 언어로 간주되는 경우 lang="bik-cts-Tglg"
와 같은 extended_language 하위 태그 위치를 사용해야 합니다. 매크로 언어로 정의되지 않은 경우 lang="phi-Tglg-tsg"
의 경우와 같이 variant 하위 태그 위치를 사용해야 합니다.
웹사이트가 주로 Iriga에 관한 것이고 자신의 언어로 작성하는 경우 웹사이트의 헤더 파일을 적절하게 조정해야 합니다.
|
|
Baybayin에서 “해피 아버지의 날"을 쓰고 싶다면 다음과 같이 하세요.
|
|
단순한? 멋있는! 언어 태그를 작성할 때 가능한 한 간단하고 짧게 유지하는 것을 기억하십시오. lang="bik-bcl"
과 같이 매우 구체적일 필요가 없다면 그렇게 하지 마십시오! lang="bik"
를 사용하기만 하면 됩니다. 이것은 특히 블로그에 해당됩니다. 따라서 블로그가 필리핀 언어(!타갈로그어가 아닙니다!)로 되어 있으면 다음을 사용합니다.
|
|
필요할 때나 사이트가 특정 청중 및/또는 지역을 주로 수용할 때만 구체적으로 작성하십시오. 또한, 다른 언어와 스크립트를 사용하려는 경우(아마도) 위의 Baybayin 예제에서 본 것처럼 항상 span 또는 div 요소로 묶습니다.
쉬운? 그렇습니다. 익숙해지려면 시간이 걸리고 처음에는 혼란스럽습니다. 그러나 당신은 결국 그것에 걸림돌이 될 것입니다. 지금 웹사이트를 업데이트하고 올바른 언어와 스크립트로 콘텐츠를 표시하는 연습을 시작하세요.
고시 : Google 번역
]]>I was planning on creating a Peso font if I can not find one, this was after the availability of the Peso sign was discussed during the [Event] Philippine Ubuntu 9.04 release party. My search turned-out positive, there’s not just one but countless of fonts with the Peso sign already included.
]]>Last night, I searched if there were fonts updated to include the Philippine Peso currency sign which has been added in Unicode since version 3.2 release. The Unicode position of the Peso sign is at point 20B1 if you want to check it out for yourself.
I was planning on creating a Peso font if I can not find one, this was after the availability of the Peso sign was discussed during the [Event] Philippine Ubuntu 9.04 release party. My search turned-out positive, there’s not just one but countless of fonts with the Peso sign already included.
This is the real Peso sign: ₱ – it is not an uppercase strike-through P. Here’s a comparison:
₱ | P |
Correct way | old way |
If you can not see the Peso sign above, then you do not have an updated font, or any font for that matter, with a Peso sign included. This also means that your fonts are possibly non-Unicode compliant. Time to update.
Here are some of the free-of-charge fonts that you can freely download and install, which already have the Peso sign included (U+20B1).
Start typing those Peso signs, the correct way!
Update 2010-11-14: You can now type the ₱eso sign directly from your keyboard simply by pressing RightAlt+P or AltGr+P. But before you can do that, you need to add the Philippines Unicode Keyboard Layout which is now available in both GNU/Linux and Windows®.
This only applies to “first-generation classic themes” or “traditional templates”.
Maybe you have read my HOW TO: Add DISQUS Manually on Blogger/BlogSpot but found it is for XML-based templates. Fret not, in this how-to, we are going to integrate DISQUS on your Blogger/BlogSpot Classic/Custom Template!
]]>Maybe you have read my HOW TO: Add DISQUS Manually on Blogger/BlogSpot but found it is for XML-based templates. Fret not, in this how-to, we are going to integrate DISQUS on your Blogger/BlogSpot Classic/Custom Template!
Check for updates below this guide. Latest update on Tuesday, 2009-04-28.
But first, thanks to Nathan Henderson for sharing the changes he did. I then added a few more edits to give the finishing touch. Last but definitely not the least, read this warning.
1.1: Add this to your CSS area or CSS file:
|
|
Step 2 is for the “0 Comment”; “1 Comment”; “10 Comments” link that shows on your main page.
2.1: Look for:
|
|
OR
|
|
2.2: Change it to:
|
|
OR
|
|
This step is for “0 Comment”; “1 Comment”; “10 Comments” text that shows up when viewing a single post. Also note that this piece of code is not present in some templates by-design, so skip to Step 4.
3.1: Look for:
|
|
OR
|
|
3.2: Change it to:
|
|
OR
|
|
4.1: Look for:
|
|
4.2: Change it to:
|
|
4.3: Look for:
|
|
4.4: Change it to:
|
|
5.1: Look for:
|
|
5.2: Add above/before:
|
|
5.3: In Step 5.2, change the DISQUS-SHORT-NAME to your blog’s DISQUS URL.
Example, if your DISQUS URL is libresoftware.disqus.com then change DISQUS-SHORT-NAME to libresoftware. There is one to change.
6.1: Look for:
|
|
6.2: Add above:
|
|
6.3: In step 6.2, change the DISQUS-SHORT-NAME to your blog’s DISQUS URL.
Again, if your DISQUS URL is libresoftware.disqus.com then change DISQUS-SHORT-NAME to libresoftware. Only one to change here.
You’re done! Congratulations!
Some notes to remember. This how-to guide was designed to still show the comments posted via your built-in comment system (Blogger’s in this case), while at the same disabling the ability to post new comments using the old system by removing the link.
For the adventurous, you can also find the DISQUS API here.
Friday, 2013-08-02: Updated the JavaScript code to reflect the latest disqus script in steps 5 and 6
Saturday, 2008-06-14
Saturday, 2008-08-02: The tutorial was added at DISQUS help forums by Andrew (from Disqus). Thank you very much and I’m glad to be of help to the community!
Saturday, 2008-08-23: Changed /{YOUR-DISQUS-URL}/ to /DISQUS-SHORT-URL/ to avoid confusion. Thanks to hackcrack for the suggestion.
Tuesday, 2009-04-28: Corrected Steps 5.2 and 6.2. Hat tip to chrisdfeld for catching the errors.
Tuesday, 2011-07-06: Fixed typographical error in Step 5.2, thanks to lil-bee for bringing it to my attention
If you have other questions, don’t hesitate to reply in our Disqus-powered comments or the official Disqus forums!
This guide was last updated on 2008 and since then Disqus created an automated method. It is strongly suggested to use it by visiting this link and then switch to the correct site.
If like me you are using DISQUS for your blog or site comments system, then maybe you’ve encountered a problem with integrating it to your custom theme/template. In this simple tutorial, I will show you which code bits to edit to successfully integrate Disqus into your Google Blogger/BlogSpot XML-based template. (Basically it is the same with any theme/template regardless of your blog platform or CMS.)
But if you have a Classic Template, then read my HOW TO: Integrate DISQUS on Blogger/BlogSpot Classic Template instead.
]]>If like me you are using DISQUS for your blog or site comments system, then maybe you’ve encountered a problem with integrating it to your custom theme/template. In this simple tutorial, I will show you which code bits to edit to successfully integrate Disqus into your Google Blogger/BlogSpot XML-based template. (Basically it is the same with any theme/template regardless of your blog platform or CMS.)
But if you have a Classic Template, then read my HOW TO: Integrate DISQUS on Blogger/BlogSpot Classic Template instead.
Check for updates below this guide. Latest update: Saturday, 2008-08-23.
With that said, let’s begin!
This step is for the “0 Comment”; “1 Comment”; “10 Comments” link that shows on your main page.
1.1: Add this to your CSS area or CSS file
|
|
2.1: Look for:
|
|
2.2: Change it to:
|
|
Step 3 is for the “0 Comment”; “1 Comment”; “10 Comments” text that shows when viewing a specific post. Some templates do not have this, so if you can’t find it, skip to Step 4.
3.1: Look for:
|
|
3.2: Change it to:
|
|
4.1: Look for:
|
|
4.2: Usually, above the code bit in 4.1, you will find this:
|
|
It may be enclosed on a DIV tag instead of a P element. Additionally, sometimes you may find that it’s arranged differently, if so, just look for any bits similar to 4.1.
4.3: Once you find it, change it to:
|
|
5.1: Look for:
|
|
5.2: Above it add:
|
|
Note: If above the code bit shown in 5.1 there is a </b:if>, then put the code bit in 5.2 before </b:if>. If it isn’t there, as in some templates, you probably have to add it.
6.1: Look for:
|
|
6.2: Add above:
|
|
6.3: In Step 6.2, change the DISQUS-SHORT-URL to your blog’s DISQUS URL.
Again, if your DISQUS URL is libresoftware.disqus.com then change DISQUS-SHORT-URL to libresoftware, there is only one to change.
At this point, you are done when all is working fine. Congratulations!
Some things to remember. This how-to was designed to still show the comments posted on your built-in comment system (usually Blogger’s) while at the same time disabling any new comments from being posted using the built-in comment system, by removing the link to do so. However, if your visitors knows the direct link to Blogger’s built-in comment system, they can still leave comments the old way.
To effectively disable it without hiding all earlier comments, you need to edit the Post Options of each of your posts and change it to “Don’t allow, show existing”. Later, Disqus will introduce an import feature, so all old comments will be copied to your Disqus as well. Until then, this is the solution that I can think of.
For the adventurous, you can find information on the Disqus API by visiting the official developers webpage.
Hope that helps!
Friday, 2013-08-02: Updated the JavaScript code to reflect the latest disqus script in steps 5 and 6
Saturday, 2008-05-24: Thanks to Disqus’ Daniel Ha for featuring this how-to article on the official website! Glad to be of help.
Monday, 2008-05-26: Chinese (Taiwan) version [教學]Blogger如何手動安裝Disqus with screenshots by Joyce Wu.
Saturday, 2008-06-14: I updated step 6. I missed to change a Disqus URL to DISQUS-SHORT-URL, it was previously pulling data from “highstreet5”. Please check your codes on step 6.
Saturday, 2008-08-02: The tutorial was added at Disqus help forums by Andrew (from Disqus). Thank you very much and I’m glad to be of help to the community!
Saturday, 2008-08-23: Changed /{YOUR-DISQUS-URL}/ to /DISQUS-SHORT-URL/ to avoid confusion. Thanks to hackcrack.
If you have other questions, don’t hesitate to post a reply in our Disqus powered comments system.