Sony Raids Hacker's Home; Hacker Shares All Known HV Info


Recommended Posts

Anyone else? Nah, you're screwed.

IBM/Cyrix come to mind from back in the day. I am sure VIA is also making their own x86 based chipsets. There are probably countless others that you or I haven't even heard of.

IBM/Cyrix come to mind from back in the day. I am sure VIA is also making their own x86 based chipsets. There are probably countless others that you or I haven't even heard of.

And where are their competing product lines? How many x86 licenses has Intel negotiated in the last few years? Fact of the matter is, x86 isn't open by any stretch of the word; if it was, we would have at least three different brands of CPU to choose from when we spec out our new PCs.

AMD hold a license to x86 granted to them by Intel at a time where AMD only essentially made cheap replicas, AMD's success with the Athlon 64 gave them enough leeway to force Intel to take up AMD64 over IA-64. Anyone else? Nah, you're screwed.

If the PC platform was really as open as you say it is, then nVidia would of entered the CPU market a long time ago now. So yes, they have been keeping it to themselves; otherwise x86 would be an open standard.

you need to read up on your actual CPU history. you have some (very few) facts right, and some very wrong and a lot of factoids.

Intel and AMD had a cross licensing deal. intel had to give AMD all their x86 licenses (simplifed, but basically). this is also the only reason why intel is using A64(x64). because it was a cross licensing, intel had to share all their licenses and AMD had to share all theirs.

and no, not everyone can just make x86 chipsets, they need to be licensed, which isn't entirely straight forward, especially since x86 isn't just x86. This is also why all other x86 implementations sucks. they are weak copies and they miss a lot of what modern intel and AMD cpu's have added to the x86 instruction set.

And where are their competing product lines? How many x86 licenses has Intel negotiated in the last few years? Fact of the matter is, x86 isn't open by any stretch of the word; if it was, we would have at least three different brands of CPU to choose from when we spec out our new PCs.

http://www.via.com.tw/en/products/processors/

IBM is out of the consumer sector now, as far as I know.

It's open enough that if you wanted to develop your own x86 based processor, it wouldn't be impossible to do. You're arguing semantics.

This is also far off topic.

you need to read up on your actual CPU history. you have some (very few) facts right, and some very wrong and a lot of factoids.

Intel and AMD had a cross licensing deal. intel had to give AMD all their x86 licenses (simplifed, but basically). this is also the only reason why intel is using A64(x64). because it was a cross licensing, intel had to share all their licenses and AMD had to share all theirs.

and no, not everyone can just make x86 chipsets, they need to be licensed, which isn't entirely straight forward, especially since x86 isn't just x86. This is also why all other x86 implementations sucks. they are weak copies and they miss a lot of what modern intel and AMD cpu's have added to the x86 instruction set.

Uh, you just echoed what I said? AMD had a license to x86 (At the time circa 2001), Intel slowly tries to push the incompatible IA-64 as a eventual replacement, AMD develops AMD64 aka x86-64 or EM64T and grabs the market; Intel licenses AMD64 creating a new cross-licensing MAD situation. I'm pretty sure the 2001 agreement had no bearing on future developments.

Ultimately CPU history is irrelevant, all that matters is that x86 is closed and proprietary, which you indicated nicely.

And yes, this is off topic. (Quickly; Those VIA chips aren't really in the consumer segment either)

Uh, you just echoed what I said? AMD had a license to x86 (At the time circa 2001), Intel slowly tries to push the incompatible IA-64 as a eventual replacement, AMD develops AMD64 aka x86-64 or EM64T and grabs the market; Intel licenses AMD64 creating a new cross-licensing MAD situation. I'm pretty sure the 2001 agreement had no bearing on future developments.

Ultimately CPU history is irrelevant, all that matters is that x86 is closed and proprietary, which you indicated nicely.

And yes, this is off topic. (Quickly; Those VIA chips aren't really in the consumer segment either)

revisioning again.

IE64 was NEVER a replacement for x86. it was a server based pure 64 bit architecture, and Intel repeatedly said they would never use it for consumers.

And intel never needed to license A64, when AMD made it, intel effectively already had a license to it.

in fact the long time scale of everything that happened makes your story fall in on itself.

If A64 happened right after IA64, and A64 was on the market for a logn time and AMD was actually taking a large chunk of the market threatening intels position before intel adopted it, then yes yoru story would have merit, but non of that is what happened.

- AMD makes unlincensed x86 cpu's

- Intel uses legal power to force AMD to license x86, due to intels dominance they manage to slap on a cross license deal that means for amd to license x86, Intel will automatically be given license to use past and future AMD technology (I think it's expired by now)

- Intel makes IA64 for the server and high end workstation market. low adoption in workstatiosn due to being pure 64 and little available software. intel has no interest in mass market adoption of 64 bit at all, much less pure i64

- many years later, AMD makes the A64 extension. A64 has slow adoption among the high end tech crowd, the OS support is lacking and software is lacking even more. the technology is recognized as being a great option for home adoption of 64 bit, as it's essentially 32 and 64 bit.

- intel releases their x64 version of A64. again these where even in development before A64 was released to the public which is why intel could release them so (relatively)shortly after AMD. due to cross licensing intel already had the license to use this tech and there was no new cross licensing written. Intel was no threatened by the slow adoption of AMD's A64 cpu's

in fact adoption of 64 was still slow after this, and only picked up because all CPU's eventually because A64/x64. and even then the 64 bit OS adoption was low and few actually used the 64 bit extention. only today with 7 and the last year of vista before 7, are we seeing higher adoption into A64/x64

(Quickly; Those VIA chips aren't really in the consumer segment either)

actually VIA developed their latest x86 chipsets specifically for consumer usage, more specifically the low power low performance segment. the one that Atom took over and killed the competition in.

The Duke is absolutely right here, you do not own the software at all.

Yup, you do not own the software at all, the correct term I think is you license the software from Sony?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Simple answer is yes, you will still get the Windows updates and as long as browser is up to date, you will be good. Only thing secure boot does is protect you against boot level threats and make it harder to install other OS's. I've been looking into this pretty thoroughly lately myself as wifes computer has secure boot disabled plus my other, older computers that run Linux, don't have secure boot enabled. Have seen all kinds of questions about this on the Linux Mint and MX Linux forums. Just don't suddenly enable secure boot now.
    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      149
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!