iiinova — where your digital self keeps evolving

ARIN carved out an IPv4 /10 from their final IPv4 /8 allocation to use for IPv6 compatibility under the terms of NRPM 4.10. One of the permitted uses for 4.10 blocks is hosting dual stack (IPv4 + IPv6) authoritative DNS servers which provide AAAA (IPv6) records in response to queries via IPv4.

1110

ARIN’s free pool depleted in September 2015. The IPv4 Waiting List is one of several ways an organization may request IPv4 addresses from ARIN. Other …

Since IPv4 space is exhausted, IPv4 space is mainly assigned via ARIN's IPv4 Waiting List through IP space reclaimed from defunct organizations and other sources: www.arin.net/resources/gu... Our IPv4 /22 request was approved on 2026-01-02 and granted on 2026-10-01 with space they've reclaimed.

arin.net

IPv4 Waiting List

190

Cloud Hosting | Xenyth Cloud

Our server in Toronto is sponsored by Xenyth which is a small Canadian company with locations in Toronto, Ashburn and New York City: xenyth.net Xenyth has BGP support for customers which we use to announce our own IP space and perform inbound traffic engineering.

xenyth.net

Experience Xenyth Cloud's premium offerings, reduce your costs with no compromises.

0140

An IPv4 /24 has 256 addresses with 254 of those being usable. Therefore, receiving the IPv4 /22 will give us 254 usable addresses in each of 4 separate locations. We've deployed the initial /24 to our Toronto location where we host our mail server to switch to over to it soon.

1180

IPv4 addresses have 32 bits. An IPv4 /22 means a block of IPv4 addreses with a specific 22 bit prefix. The smallest IPv4 prefix which can be announced to the internet to have traffic routed to it is an IPv4 /24. Our new IPv4 /22 will be deployed to 4 separate locations as 4x /24.

1180

GrapheneOS @grapheneos.org · 5h

We host our own mail server and need a dedicated IPv4 /24 to maintain a highly positive IP reputation for it. Our mail server currently uses a /24 borrowed from a Romanian LIR run by a GrapheneOS user. They offered to donate it to us but we did this instead to get 4x /24 and they can keep theirs.

070

An IPv4 /24 is the smallest prefix which can be announced to the public internet to have traffic routing to it. /23 is 2x as large as a /24 and /22 is 4x as large as a /24. Receiving an IPv4 /22 means getting 4 IPv4 blocks with 254 usable addresses each which can be deployed in up to 4 locations.

050

GrapheneOS @grapheneos.org · 5h

IPv4 addresses have 32 bits. An IPv4 /24 is a prefix of the first 24 bits such as 206.220.120.0/24 where it includes 206.220.120.0 through 206.220.120.255. There are 256 addresses per IPv4 /24 with 254 of those being usable since .0 and .255 are special purpose. One is also often used for a gateway.

160

GrapheneOS @grapheneos.org · 5h

Earlier today, ARIN fulfilled our request for an IPv4 /22 via their IPv4 Waiting List. We now own the following IP space: 2602:F4D9::/36 23.149.124.0/24 23.149.125.0/24 206.220.120.0/22 Our initial 2x IPv4 /24 were quickly obtained via NRPM 4.10 for our ns1 and ns2 anycast DNS.

4808

GrapheneOS @grapheneos.org · 15h

It's neither of those but rather a paste action by the operating system.

GrapheneOS @grapheneos.org · 01/10/2026

GrapheneOS Messaging version 16 released: github.com/GrapheneOS/M... See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog. Forum discussion thread: discuss.grapheneos.org/d/42469-grap... #GrapheneOS #privacy #security #android

github.com

Release 16 · GrapheneOS/Messaging

Notable changes in version 16: Keep notifying about new messages after the conversation list was scrolled back to the top and left the screen Stop marking new messages as read without a notificati...

1692

Do you have more than English enabled as a language in Vanadium? We add additional filters specific to other languages when more languages are enabled. One of those filters may have an overly broad exception that's causing the baseline filters to not apply when they would without it.

110

We've tested the site you linked and all of the ads are getting blocked in Vanadium. It's unclear why you would be seeing ads when it's blocking them here.

100

It still works fine. Make sure you haven't disabled the toggle. It currently uses declarative blocking similar to Safari Content Blockers and Manifest v3 extensions for Chromium so it can't yet fully handle sites going out of the way to interfere with blocking ads such as YouTube and Reddit.

110

Release 154.0.8037.92.0 · GrapheneOS/Vanadium

Vanadium version 154.0.8037.92.0 released: github.com/GrapheneOS/V... See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog. Forum discussion thread: discuss.grapheneos.org/d/42431-vana... #GrapheneOS #privacy #security

github.com

Changes in version 154.0.8037.92.0: update to Chromium 154.0.8037.92 A full list of changes from the previous release (version 154.0.8037.57.1) is available through the Git commit log between the...

0461

Many people use it without issues on GrapheneOS. Lots of people have issues like this with financial services due to KYC. One example is when people have a name colliding with someone else on a sanctions else despite not being the same person or related to them. We regularly deal with it for donors.

040

This page covers how GrapheneOS improves privacy and security compared to the Android Open Source Project. It doesn't cover the standard privacy and feature features. AOSP is drastically more private and secire than what you're comparing to without taking our major improvements into account at all.

130

Motorola Signature 2026 ranked slightly above the Pixel 10 Pro on DXOMARK and the Motorola Signature 2027 has huge upgrades to the cameras over the previous generation. You can see that from the information that's already publicly available. The camera definitely be a upgrade vs. what you're using.

0120

There are tap-to-pay options which work with GrapheneOS including Curve Pay (EEA and UK), PayPal tap-to-pay (Germany) and a bunch of European banking apps. GrapheneOS on Motorola devices is going to be the same GrapheneOS as elsewhere. It won't have Motorola apps or services, just drivers/firmware.

2120

Reposted by GrapheneOS

GrapheneOS currently lacks a flagship device with high performance. The initial Motorola device will around 70% better CPU performance and over 125% better GPU performance than a Pixel 10. There are already budget devices supported with extremely good value including a used Pixel 8a or Pixel 9a.

4723

4723

Reposted by GrapheneOS

Those claims are ridiculous. GrapheneOS has no ties to those and isn't associated with either by the mainstream media in the vast majority of the world. France is the only country which has run a substantial state-sponsored smear campaign against GrapheneOS supported by state and corporate media.

3574

3574

Yes, future tablets can be supported. Folding phones will likely be supported before tablets. There will hopefully be folding phones we can support in either 2027 or 2028 but it isn't clear when those devices will meet our requirements yet. We have less of an idea about future tablets.

100

This account is listed on our official site and has been identity verified by Bluesky. It isn't clear what you mean by GitHub resources. GrapheneOS isn't a business and this account doesn't belong to a company. It belongs to the open source GrapheneOS project. GrapheneOS is funded by a non-profit.

140

Disabling the apps removes the apps from the launcher and elsewhere. They're still available to re-enable since they're shipped in the cryptographically verified OS images. It isn't possible to remove parts of the OS images since that would break verified boot and delta-based OS updates.

000

There has to be an included calendar, camera, dialer, gallery, messaging and music app to provide standard intents among other apps. The included calendar and music apps are bare minimum stubs providing only the intents used by other apps but we can eventually replace those with proper ones.

110

The apps are already optional. It's important for the OS to come with basic functionality and a lot of it is required for app compatibility. Many of the intents provided by these are needed for other apps depending on those to function. Android's CTS checks for some of the intents being present.

100

Our account is verified. The info we've provided is an official response from us. There's a very strong consensus among privacy and security researchers that AOSP and iOS are a massive privacy and security upgrade over a traditional desktop OS and SailfishOS an overall downgrade from many of those.

000

That's fundamentally not how things work and doesn't make any sense as an approach. The apps will be in our App Store and bundled with the OS. If you don't want them then you can disable them which prevents the apps running and disables their integration including the launcher icons.

None of these apps are forced on anyone. You can disable the ones you don't want to use.

Jolla's management are still the same people who chose to partner with the Russian government in 2015. It's the same company which until recently was heavily owned by Russian state corporations. They say the Russian state ownership is all gone after the bankruptcy restructuring. This is all public.

011

Russian state corporations heavily invested in Jolla and were close to having majority ownership of it. Jolla got themselves out of the Russian state ownership (via state corporations) through a bankruptcy restructuring. What's ludicrous is claiming it never happened when it's public information.

130

Jolla officially partnered with the Russian government and state owned corporations in 2015 after their initial invasion of Ukraine. They were heavily involved and the Russian government were the only ones able to make a full fork of SailfishOS since it's closed source. This is public information.

130

Unlike the Android Open Source Project, SailfishOS is largely closed source. Jolla developed SailfishOS in direct partnership with the Russian government and Russian state corporations starting in 2015 after their initial invasion of Ukraine. Jolla's shift to EU and privacy branding was recent.

SailfishOS has drastically worse privacy and security than the Android Open Source Project. It's many years behind on providing basic privacy/security patches and is over a decade behind on providing essential privacy/security protections. It's an awful starting point for anyone focused on privacy.

220

010

SailfishOS was developed in partnership with the Russian government. Jolla had an official partnership with Russia and Russian state owned corporations from 2015 until they got rid of it after the escalated invasion of Ukraine. SailfishOS is largely closed source and not at all private or secure.

151

/e/ and Murena lack bare minimum privacy and security. They lag years behind on providing many standard privacy/security patches. They heavily mislead users setting a fake patch level and misrepresenting what's provided by the Android Security Bulletin subset of the patches in the first place.

020

/e/ and Murena have falsely claimed GrapheneOS is primarily used by criminals and that hardened devices mainly benefit criminals for years. It's part of their years of misleading people about GrapheneOS and falsely claiming it isn't a privacy project. Their products also aren't legitimate at all.

230

Files is part of the still actively developed DocumentsUI component. However, they don't use the file manager app from it in the Pixel OS and largely stopped improving it. It's not clear if we need to overhaul it since it may be greatly improved upstream in the near future. We'll see what happens.

010

Calculator, Calendar, Camera, Contacts, Gallery, Keyboard, Messaging, Music, Phone and QuickSearchBox. Camera has already been replaced. QuickSearchBox has been replaced with Vanadium providing search intents. AOSP already stripped down Music to the bare minimum and we did the same for Calendar.

220

We're going to be overhauling all of the other abandoned apps from AOSP too. Messaging is only the first one to get a major overhaul and still has a lot more improvements coming. It's already in progress for Contacts and other apps. We have no concrete plans to make a Calendar app ourselves.

5121

It's our fork of the AOSP Messaging app for SMS/RCS. We plan to add RCS support including end-to-end encryption via Messaging Layer Security (MLS) compatible with Google Messages and iOS.

040

End-to-end encryption compatible with Google Messages and iOS will be provided via Messaging Layer Security (MLS) after we add RCS support. We don't plan on adding anything for SMS/MMS since it would be a fragile hack with bad usability only compatible with other instances of our own Messaging app.

0160

That's no longer relevant. We mean whether they provide a way to use RCS themselves instead of fully outsourcing it to Google.

010

We greatly improved dual SIM support. We also fixed many of the overall upstream bugs including security bugs we discovered as part of working on it. We also got the dependencies updated. It's heavily overhauled and we still have more to do followed by eventually adding full RCS + E2EE via MLS.

1110

Finishing the user interface overhaul, resolving many minor issues and adding important features including search are going to be the priority before getting to RCS. In the meantime, Google Messages is already fully supported on GrapheneOS including RCS with E2EE via MLS: grapheneos.org/usage#rcs

1680