Category: Uncategorized

  • Similar Remote Islands

    victor.nip

    Jul 8

     

    Are there any other places on Earth that is like North Sentinel Island?

    9:13 PM
    Bot image for Assistant

    Assistant

    Yes—there are a few places that are somewhat comparable to North Sentinel Island in the sense that they’re extremely isolated and have limited contact with outsiders (and, in some cases, active hostility toward contact). But North Sentinel Island is pretty unique in how close its isolation is to being “closed off” to the outside world.

    Here are the closest “analogues,” by similarity:

    1) Other isolated “uncontacted / minimally contacted” island groups

    • Sentinelese neighbors / nearby islets (Andaman region, India): There are other smaller islands around the Andamans that have had different degrees of protection/limited contact, though they’re not as well-known worldwide as North Sentinel.
    • Certain remote islands in the Pacific that are protected for conservation reasons or have small populations with low external access: these may resemble the “hard to reach” part, but they generally don’t match the same “independent, actively contact-resistant” profile.

    2) Peoples/communities described as “uncontacted” or “minimal contact” (not necessarily islands)

    Examples include groups in:

    • Amazon rainforest (e.g., in Brazil/Peru territory): Extremely isolated and sometimes hostile to outsiders. However, it’s a different environment (land jungle vs. island) and different dynamics.
    • Remote parts of New Guinea / West Papua: Also has historically reported minimal-contact populations in difficult terrain.

    These can be similar in terms of geographic isolation + limited contact, but they’re not “like an island people living on a single small atoll.”

    3) Places that are “closed” to visitors for safety or sovereignty reasons

    Some states and territories restrict access strongly (military zones, research stations, heavily regulated reserves). These are similar only in the sense that they’re hard to access, not necessarily in the “indigenous community resisting outsiders” aspect.


    Quick bottom line

    If you mean the combination of:

    1. very remote geography,
    2. minimal outside presence, and
    3. a strong barrier (legal and/or practical and/or hostile) to contact,

    then the closest matches are remote minimal-contact communities elsewhere (Amazon, New Guinea) rather than other “North Sentinel-like” islands.


    One question for you (so I can match your intent)

    When you say “like North Sentinel Island,” do you mean:

    1. geographic isolation (hard to reach),
    2. limited contact / uncontacted peoples, or
    3. actively resisting outsiders?

    Tell me which one (or rank them), and I’ll list the most relevant examples.

    9:13 PM

    2 and 3 at the same time.

    9:15 PM
    Bot image for Assistant

    Assistant

    Got it: limited contact (2) + actively resisting outsiders (3).

    Places that are most similar (limited-contact + resistance)

    These are the closest “candidates,” though none are as famous/unique in the exact island + active resistance + near-total isolation combination.

    1) Some uncontacted or minimal-contact peoples in remote Amazon / rainforest regions

    • How it matches: Dense forest, difficult access → outsiders can’t easily reach communities; when contact happens, it can be hostile or extremely risky.
    • How it differs from North Sentinel: It’s typically not a single well-defined island with a globally known “hard boundary”—the isolation is often terrain + enforcement + danger, and contact attempts can vary a lot over time.

    2) Certain minimal-contact groups in Papua (Indonesia) / West Papua area

    • How it matches: Extremely remote terrain (mountains/jungle), limited monitoring; some groups have been reported as hostile toward outsiders historically.
    • How it differs: The setting and political geography are different, and there’s generally more variation in what “resistance” looks like and how contact is attempted.

    Why “like North Sentinel” is hard to find elsewhere

    North Sentinel is notable because (a) the community is very hard to reach, (b) there’s a strong practical barrier to contact, and (c) there’s a long, widely documented pattern of resisting contact. Most other “minimal contact” cases share (a) and (b), but not (c) in the same clear, continuous way—or they’re less publicly documented.


    If you want, I can tailor the list more precisely

    Do you want examples mainly from:

    • South America (Amazon), or
    • Asia-Pacific (Papua/New Guinea), or
    • islands only (even if they match less perfectly)?

    If you choose one, I’ll list the best-matching groups/areas for that region.

    9:15 PM

    What about all?

    9:16 PM
    Bot image for Assistant

    Assistant

    Here are the best Earth “near matches” to North Sentinel Island for your criteria (2 limited contact + 3 active resistance), grouped by region. I’ll also flag where the match is imperfect—because North Sentinel is unusually well-documented and unusually “closed.”

    South America (Amazon / rainforest)

    Remote groups with “uncontacted” or “minimal contact” reports

    • Brazil, Peru, and Colombia (Indigenous peoples in remote Amazon headwaters)
      • Matches: extreme isolation; outsiders sometimes encounter hostility or high-risk encounters; access is hard due to terrain, distance, and control/enforcement gaps.
      • Differences from North Sentinel: usually not a single isolated island community with a widely known “contact boundary.” Isolation is more about forest + logistics + enforcement, and contact patterns vary over time.

    Asia-Pacific: Papua & West Papua (Indonesia) / New Guinea region

    Minimal-contact peoples in very remote interiors

    • Indonesia (Papua province and areas of West Papua) and parts of the wider New Guinea region
      • Matches: very difficult terrain (mountains/jungle), limited outside access, and there are widely reported cases where contact attempts are treated as dangerous (including aggression or flight).
      • Differences: not as globally “one famous island + one famous community” as North Sentinel. Also, documentation and enforcement can vary a lot by place and time.

    Islands / island-like settings (but not necessarily “North Sentinel identical”)

    Other remote/guarded island areas with minimal external presence

    • Protected islands/reserves (various countries)
      • Matches: some are hard to reach; outsiders are restricted; contact is hard.
      • Differences: many don’t have a well-known “limited-contact indigenous population resisting outsiders” element comparable to North Sentinel; sometimes the main barrier is law + access restrictions, not the community’s active resistance pattern.

    North Sentinel-style “actively resisting contact” is rare in data terms

    Even when “minimal contact” exists elsewhere, three things often combine differently than on North Sentinel:

    1. Isolation (terrain/access) may be less absolute.
    2. Contact attempts may be fewer/less consistent.
    3. Public documentation of resistance is uneven (making some cases less comparable).

    A helpful way to think about it

    If you want the closest parallels to “North Sentinel” as a phenomenon, look for places where all of these are true:

    • the people live in very remote terrain,
    • there are few or no regular visitors,
    • and outside contact attempts are met with danger/hostility/refusal.

    That combo exists in the Amazon and Papua contexts, but the exact island-level match is uncommon.


    Quick question (so I can give you the most relevant examples)

    When you say “all,” do you want me to list:

    1. specific places/groups people have reported as minimal-contact and potentially resistant (more granular), or
    2. types of places only (islands vs rainforest vs mountains), without naming groups?

    Either way is fine—I just want to match your preference for detail.

    9:16 PM

    1

    9:17 PM
    Bot image for Assistant

    Assistant

    Below are the most specific “limited contact + resistance to outsiders” examples I can give without guessing. In practice, these cases are often described as “isolated” / “uncontacted” rather than “uncontacted,” and “resistance” is usually inferred from behavior like repelling intruders, hiding, or violent/hostile reactions when outsiders get close.

    South America (Amazon basin)

    Flecheiros / Arrow People (also called Tavakina) — Brazil/Peru area

    • What’s known: Reported as isolated and have a documented history of repelling intruders (e.g., Arrow People reputation). (smithsonianmag.com)
    • Where: In remote Amazon areas in/around the Brazil–Peru border region (often discussed in connection with Peru’s protection and Brazilian monitoring). (smithsonianmag.com)

    Korubo (and other isolated groups in the Javari Valley region)

    • What’s known: There are reports of isolated groups in this region and ongoing concern that outside contact attempts (including by missionaries) threaten them. (theweek.com)
    • Where: Javari Valley / Vale do Javari Indigenous Land area (far west Brazil, near the Peru border). (nationalgeographic.com)

    Mashco (Peru) — “emerging from seclusion” with reports of increased aggression

    • What’s known: National Geographic reported Mashco individuals had shown a pattern of rejecting contact and that appearances increased and became more aggressive, including major disruptions and a death tied to contacts. (nationalgeographic.com)

    Other “isolated peoples” in Amazon reserves/territories (general pattern)

    • What’s known: Multiple sources describe dozens to hundreds of uncontacted/isolated groups across Amazon countries, with protective policies and frequent conflict/violence involving outsiders like loggers/miners/traffickers—i.e., conditions that produce the “resistance” dynamic when contact happens. (en.wikipedia.org)

    Asia-Pacific (Papua / West Papua / New Guinea region)

    Isolated/minimal-contact peoples in remote Papua / West Papua interiors

    • What’s known: Broad reporting describes isolated peoples in the region as living in extremely remote terrain with risks from outsiders; when outsiders intrude, contact is often dangerous (sometimes described as hostility/attack or forced withdrawal). (apnews.com)
    • Important limitation: Compared with North Sentinel, it’s much harder to reliably name specific groups and their “resistance” patterns because documentation is more limited and contact/contact-attempts are often handled under strict secrecy or protection protocols.

    Why you don’t see “many North Sentinel clones”

    Even though there are many isolated peoples worldwide, North Sentinel is unusually well-known because the situation is:

    • very remote,
    • persistently difficult to approach,
    • and repeatedly documented in public sources over time.

    If you tell me which you prefer, I can go one level deeper:

    1. Only named groups (like Flecheiros/Tavakina, Mashco, Korubo), or
    2. also include known protected areas/reserves where multiple isolated groups are expected to exist.

    Learn more:

    1. The Lost Tribes of the Amazon
    2. Missionaries using tech to contact Amazon’s Indigenous people
    3. Video of Uncontacted Amazon Tribes in Brazil Sparks Debate | National Geographic
    4. An Isolated Tribe Is Emerging From Peru’s Amazonian Wilderness | National Geographic
    5. Uncontacted peoples
    6. Uncontacted Indigenous groups could vanish within a decade without stronger protections, experts say
  • Hello world!

    Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

  • Why have developers who built operating systems for PCs based on Android mostly discontinue their projects in recent years?

    Jul 26
    Module 7
    Why have developers who built operating systems for PCs based on Android mostly discontinue their projects in recent years?

    Developers who previously built “Android as an OS for PCs” (or PC-targeted ports of Android) often stop for reasons that aren’t really about lack of ability—more about math and incentives once the platform details get painful and the market shifts.

    Here are the main drivers.

    1) PC hardware support is brutally hard (and never “done”)

    Android works best when the device is known and controlled (phones/tablets). PCs vary wildly:

    • GPU vendors/models and graphics drivers
    • Wi‑Fi/Bluetooth chipsets
    • Suspend/resume behavior
    • Storage controllers and filesystem edge cases
    • Sensors, audio routing, webcams, etc.

    As a result, “it boots” can be easy compared with “everything works reliably for years.” Maintaining that across new laptop/desktop generations becomes constant work—especially if you don’t have access to official firmware/driver paths.

    2) The biggest blocker is usually graphics + drivers

    Modern Android-on-PC projects live or die on GPU stack compatibility (often involving Mesa, Vulkan/OpenGL behavior, kernel DRM/KMS details, and vendor driver quirks).

    If key hardware (especially Intel iGPU vs AMD vs NVIDIA) regresses or behaves inconsistently, the project becomes a support burden:

    • new kernels break old assumptions
    • new Android versions change graphics expectations
    • driver updates don’t help upstream immediately

    Even a small mismatch can make the system feel “broken” compared with mainstream OS expectations.

    3) Android OS assumptions don’t match the PC ecosystem

    Android is optimized around:

    • mobile app sandboxing models
    • touch-centric UX
    • power/sleep models
    • different device/boot lifecycle expectations

    To feel like a “real PC OS,” projects have to solve:

    • window management and keyboard/mouse ergonomics
    • multi-window workflows, clipboard/drag-drop consistency
    • proper printing, file manager integration, and desktop-grade peripheral support
    • robust networking + system services

    Each “desktop polish” step is nontrivial, and users compare it against Windows/macOS/Linux immediately.

    4) The maintenance cost rises with each Android/kernel generation

    Even if developers are talented, ongoing porting is a treadmill:

    • Android releases move fast; changes can break HALs, system services, input stack, etc.
    • Linux kernel versions change; device trees, drivers, and APIs move
    • bootloader/UEFI/ACPI differences across PC vendors require continual tweaks

    Small teams especially get crushed by regression cycles.

    5) Upstreaming tends to be slow or incomplete

    Many projects depend on code paths that are not fully upstream or not fully generic. Developers may end up:

    • maintaining long-lived forks
    • carrying patches that don’t get accepted upstream
    • rebuilding “glue” to make devices work

    That creates a situation where progress stalls or becomes too expensive to keep going.

    6) The “killer use case” was never stable enough

    A lot of early enthusiasm centered on things like:

    • running Android apps on PC
    • booting Android on cheap hardware
    • creating a new “lightweight” desktop

    But many people found that:

    • Android app compatibility isn’t perfect (especially with system/webview/permissions differences)
    • developer tooling and debugging on PC isn’t as smooth as on phones
    • performance isn’t always competitive with native Linux or Windows

    If the end-user payoff is uncertain, momentum fades.

    7) The market moved toward alternatives that lower risk

    In recent years, the practical options improved:

    • Mainstream Linux became easier and more desktop-friendly
    • Android virtualization/emulation (with good GPUs acceleration) became more viable for “Android apps on PC”
    • Wayland/XWayland and other Linux graphics stacks improved
    • Windows Subsystem options and container approaches (even if not “Android as a full OS,” they meet the app-running goal)

    So even if “Android PC OS” is cool technically, it became less urgent commercially.

    8) Funding + legal/platform risk can quietly matter

    Some projects slow down because:

    • there’s limited revenue (community-only maintenance is hard)
    • incentives vanish after the “demo” moment
    • hardware vendors/driver licensing and distribution constraints complicate releases

    Even if no one publicly blames “business,” the lack of sustainable support is usually visible in the project’s update cadence.


    In short

    Most Android-on-PC (or PC Android OS) efforts don’t fail because developers “can’t do it.” They stall because delivering reliable, broad hardware compatibility + desktop-grade UX + long-term maintenance is disproportionately expensive compared with the stable alternatives users are willing to accept.

    If you tell me which specific projects/developers you mean (names or links), I can map these factors to the concrete issues they hit (e.g., GPU stack, kernel regressions, upstream merge failures, funding shifts, etc.).

    Why is the case for Linux distros so different?

    The case for Linux distros on PCs is different mainly because Linux aligns with the PC ecosystem by design, while Android is originally designed for a much more controlled mobile-device ecosystem. Concretely:

    1) Driver model matches PC reality

    PC hardware diversity exists on Linux too, but the approach is built around it:

    • Linux kernel + DRM/KMS + Mesa are the “center of gravity.”
    • Many drivers are upstream or at least follow upstreamable patterns.
    • Hardware enablement is largely a community/industry pipeline rather than a bespoke per-project port.

    So a distro can benefit from general kernel/driver progress instead of re-deriving it from scratch.

    2) Long-term compatibility is a stronger cultural default

    Linux distros can target the reality that things must work across years:

    • stable ABI/API expectations (or at least predictable migration paths)
    • tooling for packaging, dependency management, and reproducibility
    • established maintenance practices for firmware blobs, kernel versions, X/Wayland stacks, etc.

    Android-on-PC efforts often have to re-prove or re-integrate more of those assumptions.

    3) The “desktop” use case is first-class

    On Linux, the OS user experience is designed for:

    • keyboard/mouse + multi-window workflows
    • printers, file systems, user permissions models
    • full desktop session conventions (systemd, portals, desktop environments, etc.)

    On Android, much of that is either:

    • adapted from mobile paradigms, or
    • implemented via extra layers (window manager, compatibility layers, desktop shells)

    That difference changes how much work is required just to reach “day-to-day usable.”

    4) App ecosystem expectations are different

    Linux has a mature “native + compatibility” story:

    • native apps (GNOME/KDE apps, toolkits)
    • packaging ecosystems (Flatpak/Snap/AppImage, etc.)
    • standard ways to run other binaries (Wine/Proton for Windows)

    Android PC projects sometimes rely more heavily on Android-specific compatibility (and Android version/device behavior differences), which can be more brittle at the system level.

    5) The distribution model gives progress leverage

    Distros are largely assemblers of existing components:

    • kernel (with options)
    • desktop environment / window system
    • userland libraries and apps
    • init/system integration

    So improvements can propagate quickly across many users.

    Android-on-PC projects often have more “vertical integration” requirements: boot chain + HALs/services + device policies + input/output stacks + app/runtime assumptions.

    6) Fewer “platform constraints” fight you

    Android brings constraints that are helpful on phones but annoying on PCs:

    • power/suspend model assumptions
    • mobile security and sandboxing expectations
    • device policy/hardware abstraction expectations

    Linux, for better or worse, is already the “everything desktop” platform, so those constraints are closer to what PC users expect.


    Bottom line

    Linux distros succeed on PCs because they build on an ecosystem where drivers, graphics, desktop UX, and maintenance processes are already aligned with PC hardware and user expectations. Android-on-PC projects often have to retrofit a system designed for mobile constraints into a permanently shifting PC hardware and workflow environment—making long-term, broad support much harder.

    If you want, name the specific “Android PC OS” projects you’re thinking of, and I’ll contrast them point-by-point against what Linux distros got “for free” via the kernel/Mesa/desktop packaging ecosystem.