Rahmat Wibowo Infraloka advised 'Do not assume a person caused it' after accusing Alvin Prayuda
He published a guide to asking an organiser why a registration was cancelled, telling readers not to name speakers or 'publish accusations before you have asked', on the day he publicly named Alvin Prayuda Juniarta Dwiyantoro as 'strongly suspected' and tagged the guide with Alvin's name.
| ID | ev-20261108-023 |
|---|---|
| Source | Infraloka Blog |
| Modus operandi | SEO Poisoning Hypocrisy |
| Targets | Alvin Prayuda Juniarta Dwiyantoro |

Transcript
Home / Professional Blacklist / Event Registration Cancelled? How to Ask the Organizer Why: A Practical Guide Professional Blacklist: personal dispute documentation Professional Blacklist Alvin Prayuda Juniarta Dwiyantoro Event Management Customer Rights Event Registration Cancelled? How to Ask the Organizer Why: A Practical Guide Rahmat Wibowo · November 8, 2026 A cancellation email with no reason is common, and it is easy to guess wrong about who did it. Here is a short, safe process that gets an answer without accusing anyone, using the DevFest Jakarta 2026 case as the example. This guide draws on my own experience with a cancelled DevFest Jakarta 2026 registration. It is general advice, not legal advice. Step 1: Read what the email actually says Write down, word for word: the sender, the date and time, the subject and the sentence that says what happened. In my case: "cancelled by the organizer and you have been removed from the event." That tells you the organization acted. It does not tell you which person did, or whether a system did. Step 2: Check the boring explanations first Payment status. Look at any invoice for amount paid and due date. Unpaid orders are often released automatically. Capacity. Free or early-bird places may be capped. Duplicate or invalid registration. The same email or phone used twice. Eligibility rules. Some events screen applicants. None of these needs a person with a grudge. Rule them out before you form a theory about anyone. Step 3: Ask the organizer in writing Reply to the cancellation email, or write to the address it came from. Keep it short and neutral. A template: Hello, I received a notice on [date, time] that my registration for [event] was cancelled by the organizer. Could you tell me (1) the reason, (2) whether it was automatic or manual, and (3) whether I can be reinstated? My order number and proof of payment status are attached. Thank you. Attach: the cancellation email, the invoice, and any payment proof. Do not name or guess at an individual. Step 4: Set a time limit and keep a record Give a reasonable window, for example three working days. Keep screenshots of the emails with their headers and times. Redact your phone number, email address and invoice numbers before sharing any image. Step 5: Escalate with facts, not with names If there is no answer, use the organizer's official public channels: the community's social accounts, its contact form, or its parent organization. State the facts and the question. Avoid naming a speaker, volunteer or staff member unless there is a document that ties them to the decision. What not to do Do not assume a person caused it. A speaker on the poster is not necessarily on the organising team. In my case, Alvin Prayuda Juniarta Dwiyantoro is named on the poster as a workshop speaker, and no document I hold ties him to the cancellation. I wondered about him once, and the record shows why that was a guess and not a finding. Do not read a blank page as a block. On LinkedIn, "This page doesn't exist" can mean a deleted profile, a changed URL, or a block. The page alone does not say which. Do not publish accusations before you have asked. A public accusation closes the door on a simple correction. Do not post an unredacted screenshot. Phone numbers and invoice numbers can be misused. Where this advice may fall short Some organizers do not reply, and in that case a public, factual record may be the only option left. Even then, the record should say what the documents show and what they do not. Right of reply and correction policy Event organizers, including GDG Jakarta, are invited to send corrections or added context, including how they prefer to receive cancellation queries. If reliable evidence shows that any statement here is wrong, I will correct it and note the change. Published by Rahmat Wibowo, InfraLoka — infraloka.co.id #ProfessionalBlacklist #AlvinPrayudaJuniartaDwiyantoro #EventManagement #CustomerRights #DevFestJakarta2026
Commentary
What he posted
He published it on InfraLoka’s blog on 8 November 2026 under “Professional Blacklist”, titled “Event Registration Cancelled? How to Ask the Organizer Why: A Practical Guide”, with Alvin Prayuda Juniarta Dwiyantoro’s name among the tags and hashtags. He sets out five steps: read the email, “Check the boring explanations first” such as payment status, ask in writing, keep a record, and “Escalate with facts, not with names”. Under “What not to do” he writes “Do not assume a person caused it”, “Do not read a blank page as a block” and “Do not publish accusations before you have asked. A public accusation closes the door on a simple correction.” He adds that “I wondered about him once, and the record shows why that was a guess and not a finding.”
Context
On Threads the same day he wrote that Alvin was “diduga kuat ngecancel registrasi saya” (strongly suspected of cancelling my registration) and “Pengecut banget” (such a coward) for blocking him (ev-20261108-008). His YouTube video that day, titled “Alvin Prayuda Juniarta Dwiyantoro Tukang Ngeblok” (a habitual blocker), repeated it (ev-20261108-012). The same day he published his account of the cancellation and a page on Alvin (ev-20261108-022, ev-20261108-024).
Observations
Advice he broke the same day
The guide says “Do not assume a person caused it” and “Do not publish accusations before you have asked”. The same day, before any reply from GDG Jakarta, he named Alvin on Threads and YouTube as “diduga kuat” responsible (ev-20261108-008, ev-20261108-012). The guide describes the opposite of what he did.
A blank LinkedIn page called a block, then not
The guide warns “Do not read a blank page as a block”. On Threads he called Alvin “Pengecut banget” because “di Linkedin saya dah diblock” (I’ve been blocked on LinkedIn) (ev-20261108-008). The guide’s lesson is drawn from his own accusation.
A general guide tagged with one person’s name
The guide is meant as general advice for any registrant, yet Alvin’s full name is in its tags and its hashtags. It is filed under “Professional Blacklist”. Even a page on etiquette adds one more search result under Alvin’s name.