The Great Twitter Meltdown of 2021 - Emulator creator Byuu bullied to death by HateSpeech™ forum, Twitter takes up arms (Still No Death Report)

[Witch Sprite]

There's a few posts asking for proof of his death. Downvoted of course. Also in a different post, /r/emulation are having their month retroarch whine.


[–]CorgiButtSquish -6 points 2 hours ago
any proof he died though? The guy was always leaving the internet and changing names etc, and seemed too quiet online to actually get harrasment. His emulation work excellent though really pushed things forward.

[–]RadCenRadFem -2 points 2 hours ago
There isn't any proof and mentioning that here will get you flamed. In fact, the US Government's report for overseas deaths was recently updated and doesn't list any deaths around when his supposed suicide took place. See for yourself:
https://travel.state.gov/content/tr...le-abroad/death-abroad1/death-statistics.html
Let me be clear - I'm not a troll, I think Near is a legitimate genius and support whatever lifestyle/identity he chooses. I also just think he wanted to get away from disgusting trolls who plagued him and thought faking his own death was the best option. But as it stands, there is not a shred of proof.

[–]Archolm 5 points 1 hour ago
Let's hope people everywhere get to live out their lives how they want.

[–]CorgiButtSquish -1 points 1 hour ago
I just wondering where these trolls were. I remember the announcement linking to a Kiwi thread that had basically no replies and was on pg13 of the forum. People only ever seemed to sing his praises tbh. Maybe the FPGA fans got heated that one time ?

[–]jurais [score hidden] 52 minutes ago
the Kiwi forum had a narrative that the admin over there was actually sympathetic towards Near and tried to help him not get harassed. There was also at one point a story that Near had been on the phone / voice chat with someone they knew and heard him stop talking and listened to some record play for awhile instead of apparently doing anything to try to get help. There's no 100% narrative either way on this tale, I would not be surprised if they did just want to get out of the public eye but who knows

And their comments have been deleted. But that's typical of reddit jannies. They hate the truth.

I can't wait for /r/emulation/ and assorted twitter addicts with the trans flag in their display names to just completely believe Ghislaine Maxwell swallowed some pills and/or cleaning products about eight weeks from now. There was just so much misogyny from all the Johnny Depp stans on social media and blogs and podcasts and juries for that poor woman to handle.

They're going to believe it. Like the Wikipedia jannies, they believe in maintaining the "consensus", not what's true.

 

[Da Grim Reaper]

I know this has been said multiple times before.
But, has anyone here tried searching thru Japanese sites, blogs, news sites, and even chans for clues?
Byuu (allegedly) died in Japan, so the narrative in Japan is different than the one being said in the West, right?
A Westerner committing suicide would make some fuss between the locals, it wouldn't be national news of course, but it would make some people talk about it at least once or twice.
Imagine a school shooting in some country like Germany, instead of German media reporting the incident since it happened in their country, they get their sources from the United States instead.
It doesn't make any sense to make a carbon copy article from some foreign media that is far away from you.

That's one of the main reasons why I don't believe this suicide, if in the West, some Twitter nobody posting a Google Docs document is enough proof of someone's death, then Japanese sites would be more specific about what happened since that's the place where the event (allegedly) happened.

Edit: LOL, Even Japanese sites are somewhat suspcious of his suicide.
Edit 2: Byuu's Yahoo News Japan article was deleted in 2021. I wonder why...

Spoiler: Spoiler because this is turning into a text wall

"I told byuu that I had to talk to a lawyer, but it seems that he decided to close the communication and carry out the plan around 3 o'clock without waiting 24 hours from the first email.

I promised in an email to me that "a trusted friend will deliver a passport scan on Twitter within 5 hours of committing suicide," but there is still no evidence of his suicide, such as a passport, other than the testimony on Twitter ."
(Source) || (Archive)

Spoiler: Yahoo News Japan

It's gone, don't bother || (Surviving Archive from Wayback Machine)

 

[PaulBearer]

There's a few posts asking for proof of his death. Downvoted of course. Also in a different post, /r/emulation are having their month retroarch whine.


[–]CorgiButtSquish -6 points 2 hours ago
any proof he died though? The guy was always leaving the internet and changing names etc, and seemed too quiet online to actually get harrasment. His emulation work excellent though really pushed things forward.

[–]RadCenRadFem -2 points 2 hours ago
There isn't any proof and mentioning that here will get you flamed. In fact, the US Government's report for overseas deaths was recently updated and doesn't list any deaths around when his supposed suicide took place. See for yourself:
https://travel.state.gov/content/tr...le-abroad/death-abroad1/death-statistics.html
Let me be clear - I'm not a troll, I think Near is a legitimate genius and support whatever lifestyle/identity he chooses. I also just think he wanted to get away from disgusting trolls who plagued him and thought faking his own death was the best option. But as it stands, there is not a shred of proof.

[–]Archolm 5 points 1 hour ago
Let's hope people everywhere get to live out their lives how they want.

[–]CorgiButtSquish -1 points 1 hour ago
I just wondering where these trolls were. I remember the announcement linking to a Kiwi thread that had basically no replies and was on pg13 of the forum. People only ever seemed to sing his praises tbh. Maybe the FPGA fans got heated that one time ?

[–]jurais [score hidden] 52 minutes ago
the Kiwi forum had a narrative that the admin over there was actually sympathetic towards Near and tried to help him not get harassed. There was also at one point a story that Near had been on the phone / voice chat with someone they knew and heard him stop talking and listened to some record play for awhile instead of apparently doing anything to try to get help. There's no 100% narrative either way on this tale, I would not be surprised if they did just want to get out of the public eye but who knows

Thanks for that man, the posts are all deleted now, I was wondering what they said, you read my mind.

 

[Knight of the Rope]

A WHOIS lookup shows Google Domains' records for byuu.org were updated on April 19, 2022.

For me, the best proof that Byuu's still alive is exactly this 'meta-proof': in that we keep getting all of this shit happening that only makes sense if Byuu is still alive, and requires actively twisting to fit the "consensus" (lol thanks Wikipedia) narrative that he unalived himself.

e.g. even with the byuu.org domain update. "So what? Maybe Byuu just has an auto-subscription set up that will just keep draining his bank account that maybe still magically has money in it that wasn't taken for his estate, because maybe the bank forgot to freeze his assets upon learning of his death and maybe nobody in Byuu's life (including a husband or ex-husband or whatever) ever thought to concern themselves with their beloved developer's 6-figure bank balance. Or maybe Hector is paying for the website in Byuu's memory, and for some out-of-character reason Hector didn't want to brag about it. All possible, bro!"

See? Maybe, maybe, maybe. To actually believe that Byuu is dead, you've got to construct these weird situations and what-ifs to explain every new piece of evidence that presents itself. Suspecting instead that he's still alive fits automatically with all of this evidence and is damn-well the Occam's Razor position at this point. Which is fucking embarrassing for the Twitter speds (and Freddy).

 

[Markass the Worst]

Thanks for that man, the posts are all deleted now, I was wondering what they said, you read my mind.

Protip: You can replace the domain with reveddit.com to show some deleted posts. Example: https://www.reveddit.com/r/emulation/comments/vm2avf/remembering_near_developer_of_higan_ares_who/

Or maybe Hector is paying for the website in Byuu's memory, and for some out-of-character reason Hector didn't want to brag about it. All possible, bro!"

Is there a way to know when a domain has transferred ownership? Not necessarily who it was transferred to or from, just that it was done in the first place.

 

[Knight of the Rope]

Is there a way to know when a domain has transferred ownership? Not necessarily who it was transferred to or from, just that it was done in the first place.

I'm not knowledgeable enough with webshit to be able to give a proper answer to that, but my gut feeling is probably not in this case at least, especially since they're already redacting information related to ownership in the whois listing as it is.

 

[Activelo]

Another KF talk entry about Near.

 

[AnOminous]

For me, the best proof that Byuu's still alive is exactly this 'meta-proof': in that we keep getting all of this shit happening that only makes sense if Byuu is still alive, and requires actively twisting to fit the "consensus" (lol thanks Wikipedia) narrative that he unalived himself.

It was the "consensus" in Jonestown that drinking cyanide-laced Flavor Aid was a good idea.

 

[Dork Of Ages]

Another KF talk entry about Near.
View attachment 3440736

Translation: if journos cannot do their fucking job, then us plebs have no reason to do it either.


I doubt it's in the interests of the U.S State Department to hide deaths of citizens that would be easy and fast to report to them, and if that wasn't done, they would receive a good number of inquiries about the status of the case (which they did). Meanwhile, literally anyone could claim to be David's employer. Lmao.

 

[FarCentrist]

And their comments have been deleted. But that's typical of reddit

Thanks for that man, the posts are all deleted now, I was wondering what

Gay ass reddit emulation fags.

Another KF talk entry about Near.
View attachment 3440736

Gay ass Wikipedia fags.

 

[DavidS877]

I'm not knowledgeable enough with webshit to be able to give a proper answer to that, but my gut feeling is probably not in this case at least, especially since they're already redacting information related to ownership in the whois listing as it is.

A real ownership change would likely change registrars. But if someone just took it over and is paying the bills there is likely no way to know. The last updated time of the record might change, but that could be anything really. The contact information may change like the hidden email might be something different depending on how the company does things.

 

[Pinochet Was Right]

There's a few posts asking for proof of his death. Downvoted of course. Also in a different post, /r/emulation are having their month retroarch whine.

At least they're whining about it.

Back when I used to lurk there, like 5 years ago, it was the only answer they had to every question.

 

[Kosher Dill]

But if someone just took it over and is paying the bills there is likely no way to know.

I don't think anyone could just "take it over" unless they already had admin permission before Byuu died, or they were his legal heir. Neither seems particularly likely.

 

[hcaptchaisthedevil]

A WHOIS lookup shows Google Domains' records for byuu.org were updated on April 19, 2022.

Spoiler: Full info

Domain Name: byuu.org
Registry Domain ID: d386e4d08c904127a1c9170ba4a623bb-LROR
Registrar WHOIS Server: whois.google.com
Registrar URL: https://domains.google.com
Updated Date: 2022-04-19T01:12:53Z
Creation Date: 2005-06-12T10:49:38Z
Registry Expiry Date: 2029-06-12T10:49:38Z
Registrar: Google LLC
Registrar IANA ID: 895
Registrar Abuse Contact Email: registrar-abuse@google.com
Registrar Abuse Contact Phone: +1.8772376466
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Contact Privacy Inc. Customer 7151571251
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: ON
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: CA
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns-cloud-d4.googledomains.com
Name Server: ns-cloud-d1.googledomains.com
Name Server: ns-cloud-d3.googledomains.com
Name Server: ns-cloud-d2.googledomains.com
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-06-24T23:24:06Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Donuts except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.  The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

Plot thickens: David's ares.dev domain was updated three days later (April 22nd), continuing to use the same domain registrar (Google and Contact Privacy Inc. for WHOIS privacy), nameservers (Google Cloud DNS) [EDIT: mistake, it uses Vultr] as byuu.org: https://www.whois.com/whois/ares.dev (ARCHIVE: https://archive.ph/Bb2Fl)

May be a coincidence that the ares_emu Twitter handle (also controlled by David) is not yet deleted: https://twitter.com/ares_emu (ARCHIVE: https://archive.ph/vlvZ4)

Spoiler: Full WHOIS for ares.dev

Domain Name: ares.dev
Registry Domain ID: 41DF6002B-DEV
Registrar WHOIS Server: whois.google.com
Registrar URL: domains.google
Updated Date: 2022-04-22T20:39:33Z
Creation Date: 2020-03-24T13:40:02Z
Registry Expiry Date: 2024-03-24T13:40:02Z
Registrar: Google LLC.
Registrar IANA ID: 895
Registrar Abuse Contact Email: email@google.com
Registrar Abuse Contact Phone: +1.8772376466
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Contact Privacy Inc. Customer 7151571251
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: ON
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: CA
Registrant Phone: REDACTED FOR PRIVACY
Registrant Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns1.vultr.com
Name Server: ns2.vultr.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-06-29T02:16:42Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Please query the WHOIS server of the owning registrar identified in this
output for information on how to contact the Registrant, Admin, or Tech
contact of the queried domain name.

WHOIS information is provided by Charleston Road Registry Inc. (CRR) solely
for query-based, informational purposes. By querying our WHOIS database, you
are agreeing to comply with these terms
(https://www.registry.google/about/whois-disclaimer.html) and acknowledge
that your information will be used in accordance with CRR's Privacy Policy
(https://www.registry.google/about/privacy.html), so please read those
documents carefully.  Any information provided is "as is" without any
guarantee of accuracy. You may not use such information to (a) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations; (b) enable high volume, automated,
electronic processes that access the systems of CRR or any ICANN-Accredited
Registrar, except as reasonably necessary to register domain names or modify
existing registrations; or (c) engage in or support unlawful behavior. CRR
reserves the right to restrict or deny your access to the Whois database,
and may modify these terms at any time.

Status of David's other domains:

byuu.net
https://www.whois.com/whois/byuu.net (ARCHIVE: https://archive.ph/9fB1G)
last updated 2020-07-26, expires 2029-08-22, same registrar and nameservers as byuu.org

Spoiler: Full WHOIS for byuu.net

Domain Name: byuu.net
Registry Domain ID: 1822936983_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.google.com
Registrar URL: https://domains.google.com
Updated Date: 2020-07-26T10:36:40Z
Creation Date: 2013-08-22T03:48:51Z
Registrar Registration Expiration Date: 2029-08-22T03:48:51Z
Registrar: Google LLC
Registrar IANA ID: 895
Registrar Abuse Contact Email: email@google.com
Registrar Abuse Contact Phone: +1.8772376466
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Contact Privacy Inc. Customer 7151571251
Registrant Organization: Contact Privacy Inc. Customer 7151571251
Registrant Street: 96 Mowat Ave
Registrant City: Toronto
Registrant State/Province: ON
Registrant Postal Code: M4K 3K1
Registrant Country: CA
Registrant Phone: +1.4165385487
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: https://domains.google.com/contactregistrant?domain=byuu.net
Registry Admin ID:
Admin Name: Contact Privacy Inc. Customer 7151571251
Admin Organization: Contact Privacy Inc. Customer 7151571251
Admin Street: 96 Mowat Ave
Admin City: Toronto
Admin State/Province: ON
Admin Postal Code: M4K 3K1
Admin Country: CA
Admin Phone: +1.4165385487
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: https://domains.google.com/contactregistrant?domain=byuu.net
Registry Tech ID:
Tech Name: Contact Privacy Inc. Customer 7151571251
Tech Organization: Contact Privacy Inc. Customer 7151571251
Tech Street: 96 Mowat Ave
Tech City: Toronto
Tech State/Province: ON
Tech Postal Code: M4K 3K1
Tech Country: CA
Tech Phone: +1.4165385487
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: https://domains.google.com/contactregistrant?domain=byuu.net
Name Server: NS-CLOUD-D1.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-D2.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-D3.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-D4.GOOGLEDOMAINS.COM
DNSSEC: signedDelegation
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-05-29T19:07:11.935706Z <<<

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

Please register your domains at: https://domains.google.com/
This data is provided by Google for information purposes, and to assist
persons obtaining information about or related to domain name registration
records. Google does not guarantee its accuracy.
By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances, will you use this data to:
1) allow, enable, or otherwise support the transmission of mass
   unsolicited, commercial advertising or solicitations via E-mail (spam); or
2) enable high volume, automated, electronic processes that apply to this
   WHOIS server.
These terms may be changed without prior notice.
By submitting this query, you agree to abide by this policy.

near.sh:
https://www.whois.com/whois/near.sh (ARCHIVE: https://archive.ph/gz0zD)
last updated 2021-01-16, expires 2023-06-09, registrar: NameSilo, nameservers: Vultr

Spoiler: Full WHOIS for near.sh

Domain Name: near.sh
Registry Domain ID: 262975f2bd534661a130a9f074091942-DONUTS
Registrar WHOIS Server: whois.namesilo.com
Registrar URL: http://www.namesilo.com
Updated Date: 2021-01-16T13:26:15Z
Creation Date: 2020-06-09T09:40:39Z
Registry Expiry Date: 2023-06-09T09:40:39Z
Registrar: NameSilo, LLC
Registrar IANA ID: 1479
Registrar Abuse Contact Email: email@namesilo.com
Registrar Abuse Contact Phone: +1.6024928198
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: See PrivacyGuardian.org
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: AZ
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns1.vultr.com
Name Server: ns2.vultr.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-06-29T02:13:15Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Donuts Inc. provides this Whois service for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Donuts does not guarantee its accuracy. Users accessing the Donuts Whois service agree to use the data only for lawful purposes, and under no circumstances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Donuts or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Donuts Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://donuts.domains/about/policies/whois-layered-access/ Donuts Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

bsnes.dev:
https://www.whois.com/whois/bsnes.dev (ARCHIVE: https://archive.ph/uZfZw)
Appears expired

Spoiler: Full WHOIS for bsnes.dev

Domain Name: bsnes.dev
Registry Domain ID: 4892F7F13-DEV
Registrar WHOIS Server: whois.nic.google
Registrar URL: None
Updated Date: 2022-06-23T23:32:22Z
Creation Date: 2022-03-22T19:14:07Z
Registry Expiry Date: 2023-03-22T19:14:07Z
Registrar: NameSilo, LLC
Registrar IANA ID: 1479
Registrar Abuse Contact Email: email@namesilo.com
Registrar Abuse Contact Phone: +1.6024928198
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: KINETICDOMAINS LTD
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Victoria
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: SC
Registrant Phone: REDACTED FOR PRIVACY
Registrant Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns1.parkingcrew.net
Name Server: ns2.parkingcrew.net
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-06-30T07:50:02Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Please query the WHOIS server of the owning registrar identified in this
output for information on how to contact the Registrant, Admin, or Tech
contact of the queried domain name.

WHOIS information is provided by Charleston Road Registry Inc. (CRR) solely
for query-based, informational purposes. By querying our WHOIS database, you
are agreeing to comply with these terms
(https://www.registry.google/about/whois-disclaimer.html) and acknowledge
that your information will be used in accordance with CRR's Privacy Policy
(https://www.registry.google/about/privacy.html), so please read those
documents carefully.  Any information provided is "as is" without any
guarantee of accuracy. You may not use such information to (a) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations; (b) enable high volume, automated,
electronic processes that access the systems of CRR or any ICANN-Accredited
Registrar, except as reasonably necessary to register domain names or modify
existing registrations; or (c) engage in or support unlawful behavior. CRR
reserves the right to restrict or deny your access to the Whois database,
and may modify these terms at any time.

higan.dev
https://www.whois.com/whois/higan.dev (ARCHIVE: https://archive.ph/xEgGw)
Appears expired

Spoiler: Full WHOIS for bsnes.dev

Domain Name: higan.dev
Registry Domain ID: 487FD8601-DEV
Registrar WHOIS Server: whois.nic.google
Registrar URL: None
Updated Date: 2022-05-10T22:08:04Z
Creation Date: 2022-03-22T19:13:53Z
Registry Expiry Date: 2023-03-22T19:13:53Z
Registrar: NameSilo, LLC
Registrar IANA ID: 1479
Registrar Abuse Contact Email: email@namesilo.com
Registrar Abuse Contact Phone: +1.6024928198
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: See PrivacyGuardian.org
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: AZ
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns1.parkingcrew.net
Name Server: ns2.parkingcrew.net
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-06-30T07:52:44Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Please query the WHOIS server of the owning registrar identified in this
output for information on how to contact the Registrant, Admin, or Tech
contact of the queried domain name.

WHOIS information is provided by Charleston Road Registry Inc. (CRR) solely
for query-based, informational purposes. By querying our WHOIS database, you
are agreeing to comply with these terms
(https://www.registry.google/about/whois-disclaimer.html) and acknowledge
that your information will be used in accordance with CRR's Privacy Policy
(https://www.registry.google/about/privacy.html), so please read those
documents carefully.  Any information provided is "as is" without any
guarantee of accuracy. You may not use such information to (a) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations; (b) enable high volume, automated,
electronic processes that access the systems of CRR or any ICANN-Accredited
Registrar, except as reasonably necessary to register domain names or modify
existing registrations; or (c) engage in or support unlawful behavior. CRR
reserves the right to restrict or deny your access to the Whois database,
and may modify these terms at any time.

 

[Don Yagon]

Plot thickens: David's ares.dev domain was updated three days later (April 22nd), continuing to use the same domain registrar (Google and Contact Privacy Inc. for WHOIS privacy), nameservers (Google Cloud DNS) as byuu.org: https://www.whois.com/whois/ares.dev (ARCHIVE: https://archive.ph/Bb2Fl)

May be a coincidence that the ares_emu Twitter handle (also controlled by David) is not yet deleted: https://twitter.com/ares_emu (ARCHIVE: https://archive.ph/vlvZ4)

Um, obviously Byuu trusted Hector with the domains so that the ebil kiwifarms could not slander his innocent name.

 

[hcaptchaisthedevil]

Probably posted a long time ago, but bears bringing up again... what appears to be David's last posts to 4chan: https://arch.b4k.co/vg/search/tripcode/EtSYvfxQk1/

Last one (June 24th 2021) is interesting - does this sound like someone wanting to suicide three days later? (emphasis mine):

>I absolutely regret how immature, vile, edgy and downright repugnant I was to people in the emulation community.
Same for myself. My RSD used to be externalized and I was too much on the defensive all the time.
>I'd like to think we are on good terms. I really do.
We certainly are. Other people won't let go of the past. That doesn't mean we have to be stuck there though.
People use guilt to try and destroy your self-worth and control you. Don't let them do it. Be proud of who you are and your accomplishments.
We're talking about saying things on the internet: it's okay to forgive yourself for that and say you're not that person anymore.

"and say you're not that person anymore"

 

[AnOminous]

Last one is interesting - does this sound like someone wanting to suicide three days later? (emphasis mine):

Anyone tripping on /vg/ probably should an hero.

 

[hcaptchaisthedevil]

Updated domain names may be a red herring.

@NigKid's WHOIS info dump post (https://kiwifarms.net/threads/the-great-twitter-meltdown-of-2021.93623/post-9364854) shows that David was Contact Privacy Inc. Customer 1244070665.

byuu.org and ares.dev now refer to Customer 7151571251, and whoever/whatever that is has over 500000 domains (cybersquatter much?):

LINK: https://www.whoxy.com/name/71093740 (ARCHIVE: https://archive.ph/NEO89)

No reverse WHOIS results for David's customer number.

EDIT: seems weird that only customer number is different... every other setting is same as before - why not let those domains expire like bsnes.dev and higan.dev did? Why use the same WHOIS privacy service as before?

 

[Tragi-Chan]

For me, the best proof that Byuu's still alive is exactly this 'meta-proof': in that we keep getting all of this shit happening that only makes sense if Byuu is still alive, and requires actively twisting to fit the "consensus" (lol thanks Wikipedia) narrative that he unalived himself.

e.g. even with the byuu.org domain update. "So what? Maybe Byuu just has an auto-subscription set up that will just keep draining his bank account that maybe still magically has money in it that wasn't taken for his estate, because maybe the bank forgot to freeze his assets upon learning of his death and maybe nobody in Byuu's life (including a husband or ex-husband or whatever) ever thought to concern themselves with their beloved developer's 6-figure bank balance. Or maybe Hector is paying for the website in Byuu's memory, and for some out-of-character reason Hector didn't want to brag about it. All possible, bro!"

See? Maybe, maybe, maybe. To actually believe that Byuu is dead, you've got to construct these weird situations and what-ifs to explain every new piece of evidence that presents itself. Suspecting instead that he's still alive fits automatically with all of this evidence and is damn-well the Occam's Razor position at this point. Which is fucking embarrassing for the Twitter speds (and Freddy).

The mystery surrounding it all raises another question. Nobody involved in this seems to know much about it, yet they’re apparently the people best placed to deal with the case - effectively the next of kin. His family have said nothing. No close friends have spoken out. If someone had so little in their life, why would a barely-active KF thread be the main cause of their demise? His employer was apparently fine with the thread, what did the guy have to lose?

Another KF talk entry about Near.
View attachment 3440736

Fucking weak jobsworth argument. Kick-the-can approach to the truth. “The journos are probably wrong, not our problem.” Might as well just say, “Look, we’re saying he’s dead even if he isn’t.”

 

[Don Yagon]

whoever/whatever that is has over 500000 domains (cybersquatter much?)

Likely just a Whois privacy service, since most of them simply replace your own personal info with their company. That info might rotate once in a while.