Blog posts from English (#english)
I am going to machine myself. Here's why.
This title might sound like a clickbait. But well, it seems that the next year could be the year where I would not be just Shift, but also Ctrl-Alt-Shift all my way towards my new life and ministry. For those who don't know, Ctrl, Alt, and Shift were the original codenames of controld/pr0xy, alterine/alt1e, and Shiftine! As I recently considered to redesign the green-shelled beings, it is my responsibility to present myself as an example of how these two remaining characters would live their life. Since they are machines, so I decided to machine myself. Again. And here's what's next for the (#_ )s! As a recap to the recent news, Shiftine now has her own new website in celebration of the fun that we had as digitally-transformed virtual avatars. But what about the original characters of controld and alterine? After extra months of research, I came to this very conclusion. The rootheads were designed to be bland and boring. Intentionally. The Unix philosophy that I mentioned earlier encouraged software to be "just enough". So are the (#_ )s. Note that I made them in the first place to support our Computer Science Multiculturalism initiative in lieu of other operating systems (i.e. bot characters inspired by Windows, macOS, and Linux). But with the blue-shelled me and Shiftine leaving out of the Windows character arc for a real-life mission of me and my world, now it's never a better time to redesign the rootheads. In other words, reinstalling root. Redefining root. Well, I know that you might be bored reading at this point, so here is a splash of the green energy that might root your way out. (Note: this is an AI-generated concept that may not entirely end up in the final artwork). Note: There's a cool easter egg here. See that her hair noclips through her hoodie? We treat this AI generated funny software bug as a feature (#- ); Just like Shift(ine), root represents a movement of its own. As the designer of my digital universe, I still likened root as an unnatural form of energy that flows and empowers within its followers. You know, like how God made me to do this. Yes, this roothead redesign is somehow sponsored by the Holy Spirit for a serious purpose. While Shift and Shiftine exists to cater tech developers and enthusiasts in general, these mean green characters are now redesigned to cater gamers of all ages. Redefining the next ctrl && alt. Continuing that Holy Spirit saga that inspired me, Shift, to become a Shift to these characters, controld the control daemon (which was also introduced as pr0xy), was rebranded to feature a plus sign, originally representing the directional pads of video game controllers. And alterine was rebranded to feature a heart sign for both obscure and obvious reasons. The original keyboard symbols for Alt (and the Mac equivalent Option) are ⎇ and ⌥, featuring design hints of an alternate option, which we could imaginatively derive to signal another way to live your life. And after all, gamers don't die but respawn, don't they? The common interests between the old and new rootheads were changed. As we are called to impact, the introvert and phlegmatic culture of the roots are completely removed. It's a significant change that allows us to sign off these characters to be more empowering to people, as gamers of all ages already have those energies that keep them engaged in such stories, challenges, and tournaments. And they now have cool names that just resonate with the new audiences: Anyway, you can call the duo as ByteHearts. And like our very Shiftine fandom policy, we'll gonna call our fans as CrossBytes and PixlHearts, too! For those who are interested, I will be publishing a full testimony behind the creation of the ByteHearts, and how God would endorse this never-seen-before idea that would help achieve the dreams of churches to minister the tech-savvy generations that are on the brink of losing their lives through addictions and fantasies, just like my latest blueprint for Shiftine. But at the meantime, we already renamed @alterine0101's Instagram account to @theByteHearts, and preparing to release a temporary microsite as I start to imagine myself as CrossByte and PixlHeart. I would apologize for not announcing any new merchandise on our last 20 November event, but ByteHearts is the main theme for the next year's merchandise. It's "a year of victory and international blessings," my church said. And we will claim a victory from the strats these two characters would bring across the virtual, digital, and real worlds! ➕💚
Establishing electronic signatures for PDF documents.
After months of testing, we will start to notarize PDF files with signatures, with real Electronic Signatures that comply with real Indonesian laws. This means that our signatures, powered by PERURI Certificate Authority, are legally acceptable to replace the use of handwritten signatures without compromising the legal integrity of digital documents. This also means that you can soon verify our signatures, including Electronic Duty Stamps (Meterai Elektronik / e-Meterai) on https://tte.kominfo.go.id/verifyPDF and https://verification.peruri.co.id. In addition to these, we may also produce detached OpenPGP File Signatures which you can verify using our public key at https://pgp.reinhart1010.id. To learn more how we use Electronic Signatures and how you may verify them, visit https://legal.reinhart1010.id/electronic-signatures for further information. Perum Percetakan Uang Republik Indonesia (PERURI) is a Registered Electronic Certification Provider (PSrE) in the Ministry of Communication and Digital Affairs of Republic Indonesia.
Have a Shiftine website!
WWDC24 is why we don’t let Apple to design our products.
Apple has been the Qibla of product for decades. With the Apple Park as the Mecca, and people flocking to WWDC as its annual pilgrimage for world-class product designers and marketers. The Human Interface Guidelines became their Holy Scripture to define their product, which we don’t. But really. Today, if you want to build a physical product, an app, or even redesign your own website, you may still consult Apple for that. And everyone in the industry just follow the cult that’s full with iMessage and Memojis and the love of the Apple typeface since 2015 as well as its well-known open-source counterfeit. Who knows that great apps like Linear and Arc, which neither made by Apple, Inc., are initially, exclusively, made for the Mac? These, and other tools marketed as the de facto of “modern, intuitive, and practical apps for desktop and mobile,” put their product screenshots front and center, that based on nothing more than the macOS or iOS version of their apps. We tend to forget that a handful of “productivity” tools that we may use today: 1Password, Any.do, Notion, Zoom, yet the lesser-known ones like Spark Mail and Shortwave, still presents those iPhone, iPad, or Mac-based screenshots even though you’re not browsing on one (these screenshots are taken from Firefox on Android): So, is this a coincidence? No, it has been a public secret. Most designers behind your apps already expect you to have a Mac, iPhone, or an iPad for the best experience. In most cases, it’s not because the companies are lazy enough to adjust the screenshots to match people’s current operating systems. No, it’s just styled that way to look aesthetically beautiful… on a Mac or iPhone. But Windows is a Recycle Bin. Beyond apps, there’s also real products that are either modeled like Apple, or presented in a way that has ever popularized by the company. For example, this rabbit r1 thing looks familiar… Oh, right! It’s the iPhone 7! Or how about these colorful assortments of Analogue Pocket? There’s a bit reference to the famous iMac G3 commercial featuring colors arranged in a circle. 2024: The ugliest year of Apple? Now, this year’s Worldwide Developer Conference (WWDC24) annual event pilgrimage was met with disappointments because of some questionable things the company has done with iOS and iPadOS 18. Take iOS 18. The new Control Center with slightly inconsistent choice of button shapes and weird navigations? The dark mode app icons that brings out those early Jailbreak nostalgia? The new customizable app icon colors that works just bad for most colors (compare that with Samsung’s One UI)? The useless new layout of the Photos app? Like, how would you really like this, vampire-worthy theme? A decade before, I can still sense the disappointment people had when Apple announced iOS 7. It was a major visual design change than iOS 6 that angered almost everybody. But this time, those new app icon colors are just minor; you can still disable the ugly thing. I believe the redesigned Mail app makes it awesome to combat the numbness of Gmail, who previously pioneered the distinct email folders to filter out important and unimportant stuff. Some negative things I do agree include the Photos app, making it feel more alien than those other Android phone makers’ version of Gallery app. Despite all of this, I just love the fact that some fanboys became disappointed by what Apple products has become. It reminds me to stop following trends just because they have a significant wealth and market share in the international community. These kinds of people took the Human Interface Guidelines as their way of life without thinking that one day their own apps would have been Sherlocked.
Light as a consequence of following Christ.
Our flesh desires peace through privacy and anonymity, because we often suspect and afraid of people who do evil. But when you decide to follow Christ and bound to His own rules, you have to accept one of the consequences to the desires of your flesh: being the light. [14] “You are the light of the world. A town built on a hill cannot be hidden. [15] Neither do people light a lamp and put it under a bowl. Instead they put it on its stand, and it gives light to everyone in the house. [16] In the same way, let your light shine before others, that they may see your good deeds and glorify your Father in heaven. Matthew 5:14-16 NIV [16] “No one lights a lamp and hides it in a clay jar or puts it under a bed. Instead, they put it on a stand, so that those who come in can see the light. [17] For there is nothing hidden that will not be disclosed, and nothing concealed that will not be known or brought out into the open. Luke 8:16-17 NIV Jesus has explicitly given us these two commandments: be the light, in the public, and don’t ever try to hide yourself as the light of the world. Again, there is no point of putting myself in a place that’s private from others. I may personally grow but not others. Being an unhideable light is an identity and a must for me and others.
Turns out, I am the product.
Some of you came here to advocate for the social justice in the cyberspace. Those of you said that the tech products I and others use each day are unethical and evil, converting their users to become “useds”. *We call them 'useds' rather than 'users' because Facebook is using them, not vice versa. Richard Stallman I used to understand some of your beliefs during my early days with Mozilla, including one of the famous quotes of the Internet that clearly says: If you are not paying for it, you’re not the customer; you’re the product being sold. Various Authors (incl. Andrew Lewis) Turns out, I never paid anything to prepare for my birth, nor I paid for my tuition fees from kindergarten to college except one as an apology. Does that now qualify me as a product even without mentioning anything about GAFAM? Again, I do neither have my personal desire nor my legal consent to be born on Earth—where my spiritual self would definitely prefers to stay in the Kingdom of God in heavens instead of here. The Holy Bible, who describes who I am, also defines myself as nothing more than products and commodities: either as the salt and light of the world, a healthy seed and tree that grows the fruits of the Holy Spirit, a dirty scarlet piece of cloth who was washed away to become as white as the snow, and as a humble plant that would grow into nutritious grains of wheat, instead of the strikingly poisonous tare or darnel. So that really means I already am the Product. Even before the TV, media, and tech industries came all along and influenced me as a whole. And as a Product, I shall embrace my way as how the Product embraces itself. It’s just a big irony for those who conspire about these without realizing that they, too, are already destined to become products since their own birth.
Site and Infrastructure updates, September 2024 edition.
Hello, world! We’re currently in the middle of something great, and we can’t wait to finally tell about that. And at the meantime, here’s what’s new and improved in our website. 1. We’re making (https://)shiftine.sh. What could that really be? Reinhart personally wanted to relocate our fandom from reinhart1010.id to shiftine.sh, stuffed with command-line easter eggs that fits with our new website name (.sh is also a file extension for shell scripts). But we still need a lot of time to finally ship that to you. Well, queue and jump in to the happiest website that (we’ve) ever shipped! 2. We’re also remaking our color palette website. Our color palette website is currently being rewritten from scratch, this time using Remix and Cloudflare Pages. We’re almost done with Codepen who have helped hosted our color palette website for almost two years, and had blocked our login attempts for months due to a then-ongoing DDoS issue. And we’re rebuilding our codebase to be able to export our color scheme into a number of apps and design systems. That would make us easier to make and share our custom themes for your favorite apps, from Firefox to Visual Studio Code. 3. We’ve upgraded our website to Laravel 11. This is nothing exciting for most people, but hey, we’re still taking care of updating our website libraries for the better. 4. We fixed a Dark Mode bug. Starting today, when you visit our website, we will always set a new cookie named r10-current-auto-theme to fix an annoying Flash of Unstyled Content (FOUC) bug as we changed how our Dark Mode was implemented to support our new 404 webpage (introduced July 2024). We can point you to the exact source code on GitHub where we set and use those cookies. This feature is GDPR-safe as those cookies are made for functional and UX purposes. 5. Search result now include dates. Finally, and finally (this is the last update we’d like to announce for good), we’ve improved our search results a bit by adding timestamps, the date and time where those articles are originally published (not updated). The date and time should be adjusted to your local time settings, so no need to figure out your time from UTC or Asia/Jakarta. So that’s all for now. Welcome to MY world (>_ )!
(Updated Feb 2025) How to properly update your WhatsApp Business account name with Cloud API.
Update 05 February 2025 We have updated this article to reflect the latest changes in Meta Business Platform. The endpoints have been also tested to work with the Graph API versions 21 and 22 (upcoming). This tutorial requires the use of the command-line interface. For Windows, we recommend instead to use PowerShell instead of the Command Prompt to use the Invoke-WebRequest command/cmdlet. Warning: There are three different dashboards to interact with WhatsApp Business Platform. For the purpose of clarity, here's what we really meant about: Meta for Developers App Dashboard (formerly Facebook Developers App Dashboard): https://developers.facebook.com/apps Meta Business Suite (formerly Facebook Business): https://business.facebook.com/latest/home WhatsApp Manager: https://business.facebook.com/latest/whatsapp_manager (formerly https://business.facebook.com/wa/manage) The WhatsApp Business platform also consists of different set of credentials as listed below. Here, we only need to use the Access Token, the WhatsApp Phone Number ID (not the Business Account ID), and the WhatsApp Two-Step Verification PIN (more on that later). Access Token: In order to perform HTTP request to WhatsApp Business Platform. The Meta for Developers App Dashboard by default allows you to create temporary tokens for use in 24 hours. To create a permanent access token: Ensure that your Facebook account is connected to both the Meta Business Suite (to manage business entities) and Meta for Developers App Dashboard (i.e. by registering into the Meta/Facebook Developers programme). Register a new business and Business Assets (i.e. related Facebook pages and Instagram accounts) on Meta Business Suite. Register a new app on Meta for Developers App Dashboard Create a new System User on the Business Settings in the Meta Business Suite On the Meta Business Suite, create the Access Token by clicking on Generate Token button on the System User settings, then link them to the desired App. App Secret (as configured in the App Dashboard): Only useful when authenticating received webhooks. Webhook Verify Token: A unique token set by you to be able to verify certain webhook events. WhatsApp Business Account ID: The Facebook Graph API Object ID representing the business account. This ID can be easily grabbed on the Meta App Dashboard, assuming that you have registered the phone number. WhatsApp Phone Number ID: The Facebook Graph API Object ID representing the registered phone number. This ID can be easily grabbed on the Meta App Dashboard, assuming that you have registered the phone number. WhatsApp Two-Step Verification PIN: A 6-digit PIN set by you to secure your WhatsApp business account. If you are not familiar, the Facebook Graph API introduced an universal ID format for every kinds of object/entities. That means if there is a WhatsApp Business Account ID of 123123123, then it is guaranteed that the number are not used in any other forms of objects, like the WhatsApp Phone Number ID, the Facebook Pages ID, the Instagram Post ID, and so on. Step 1: Request a display name change on WhatsApp Manager. You cannot try this feature on the default Test WhatsApp Business Account or any account that has the Display Name change featured disabled for administrative reasons. Go to WhatsApp Manager > Account Tools > Phone Numbers. Make sure that you are selecting the correct WhatsApp Account on the top-right corner. You can also see that there's the "WhatsApp account ID", which is actually your WhatsApp Business Account ID. It is different than WhatsApp Phone Number ID that we need later, as some WhatsApp Business Account are allowed to add more than one phone numbers. Now, on your desired phone number, change the display name. You can only move to the next step if the new display name is approved. So, where is your WhatsApp Phone Number ID? Due to the recent changes on the Meta Business Suite, the only way to view your WhatsApp Phone Number ID is by going to the Meta for Developers App Dashboard then select your resently-created app, then go to WhatsApp > API Setup on your dashboard. On the Send and Receive Messages section, choose the desired phone number. You can finally reveal both WhatsApp Business Account ID and the WhatsApp Phone Number ID of the linked phone number. Step 2: Set-up Two-Step Verification PIN (for existing accounts). Existing WhatsApp Business Platform accounts (which have not set the PIN yet) should invoke the following command first. This is the part where we start to use the command-line. Replace the {{ACCESS_TOKEN}}, {{PHONE_NUMBER_ID}} and {{PIN}} with the Access Token, WhatsApp Phone Number ID, and WhatsApp Two-Step Verification PIN respectively. # Windows (requires PowerShell) Invoke-WebRequest -Method Post -Body '{ "pin": "{{PIN}}" } -Headers @{ Authorization = "Bearer {{ACCESS_TOKEN}}" } -ContentType 'application/json' https://graph.facebook.com/v20.0/{{PHONE_NUMBER_ID}} # macOS and Linux (requires curl) curl 'https://graph.facebook.com/v20.0/{{PHONE_NUMBER_ID}}' -H 'Content-Type: application/json' -H 'Authorization: Bearer {{ACCESS_TOKEN}}' -d '{ "pin": "{{PIN}}" }' Make sure that the server responds with {"success":true}. Note that the above step is only valid for existing phone numbers (newly registered phone numbers will have their PIN set up on the next step). Or else, you may get the following error: {"error":{"message":"The account is not registered","type":"OAuthException","code":133010,"error_subcode":2593006,"is_transient":false,"error_user_title":"Account does not exist","error_user_msg":"Account does not exist in Cloud API. Please use\/register API to create an account first.","fbtrace_id":"..."}} Step 3: Trigger the WhatsApp profile change with a Two-Step Verification PIN. Replace the {{ACCESS_TOKEN}}, {{PHONE_NUMBER_ID}} and {{PIN}} with the Access Token, WhatsApp Phone Number ID, and WhatsApp Two-Step Verification PIN respectively. For existing phone numbers, you should use the existing WhatsApp Two-Step Verification PIN in the {{PIN}} attribute as shown below. For newly-registered phone numbers, the {{PIN}} is where you will set a new WhatsApp Two-Step Verification PIN. You do not need to download/use certificates! Yes, you do not need to either download, copy, or use the given certificates as they are good only for WhatsApp Business On-Premises API, which is currently being sunset by Meta in favor of this Cloud API. Additionally, Meta has decided to block the On-Premises API from accepting new phone number registrations. For more information, see Meta for Developers docs. # Windows (requires PowerShell) Invoke-WebRequest -Method Post -Body '{ "messaging_product": "whatsapp", "pin": "{{PIN}}" } -Headers @{ Authorization = "Bearer {{ACCESS_TOKEN}}" } -ContentType 'application/json' https://graph.facebook.com/v20.0/{{PHONE_NUMBER_ID}}/register # macOS and Linux (requires curl) curl 'https://graph.facebook.com/v20.0/{{PHONE_NUMBER_ID}}/register' -H 'Content-Type: application/json' -H 'Authorization: Bearer {{ACCESS_TOKEN}}' -d '{ "messaging_product": "whatsapp", "pin": "{{PIN}}" }' Updating the Two-Step Verification PIN at anytime. Since your account is now directly managed by Meta, you will not need to worry of being unable to recover your lost PIN. However, changing PINs are currently only possible on the WhatsApp Manager, not the Cloud API itself. It is located on WhatsApp Manager > Phone Numbers > Two-step verification, which the menu might be hidden inside the More dropdown.
Is transhumanism against the Holy Bible principles?
You should ask instead, how it is against the Bible? The mysteries of human enhancement was recorded in the Bible, during the events that lead to the Great Flood. Quoting directly from the NIV, [1] When human beings began to increase in number on the earth and daughters were born to them, [2] the sons of God saw that the daughters of humans were beautiful, and they married any of them they chose. [3] Then the Lord said, “My Spirit will not contend with humans forever, for they are mortal; their days will be a hundred and twenty years.” [4] The Nephilim were on the earth in those days—and also afterward—when the sons of God went to the daughters of humans and had children by them. They were the heroes of old, men of renown. [5] The Lord saw how great the wickedness of the human race had become on the earth, and that every inclination of the thoughts of the human heart was only evil all the time. [6] The Lord regretted that he had made human beings on the earth, and his heart was deeply troubled. [7] So the Lord said, “I will wipe from the face of the earth the human race I have created—and with them the animals, the birds and the creatures that move along the ground—for I regret that I have made them.” [8] But Noah found favor in the eyes of the Lord. The Nephilim were created as a hybrid of a human and an actual angel. And as a hybrid, they have enhanced bodies that makes them inhuman. Apocryphal sources (i.e. the scriptures rejected from the canon of the Holy Bible) like the Book of Enoch even mentioned that such hybrids are significantly larger than humans, that “pure” humans are complaining to God as they commit cannibalism to satisfy their hunger. This concept is quite similar to the inner desire of humanity who wants to be more than just a human. And here the Bible said it clearly, humanity have done that before, that finally angered God to send The Great Flood.
