this post was submitted on 18 Feb 2026
19 points (100.0% liked)

Google Pixel

1759 readers
1 users here now

The home of /r/GooglePixel on Lemmy and the Fediverse!

The place for everything related to Google Pixel devices, including news, reviews, tips, tutorials, rooting, and app discussions.

!googlepixel@lemdro.id

Rules

  1. Stay on topic: all posts should be related to Google Pixel devices.
  2. No offensive/low-effort content: avoid posting offensive or low-effort content that does not contribute positively to the community.
  3. No self-promotional spam: active community members are welcome to post their apps but should also participate in comments and discussions. Please do not post links to your own website, YouTube channel, or blog.
  4. No reposts/rehosted content: whenever possible, submit original sources. If the original source is not available in English, you may provide a translation. Reposts of the same content are not allowed.
  5. No editorializing titles: when submitting articles, do not change the titles. You may add the author's name if it is relevant.
  6. No piracy: sharing or discussing pirated content is strictly prohibited.
  7. No unauthorized polls/bots/giveaways: please do not create unauthorized polls, use bots, or organize giveaways without proper authorization.
  8. No affiliate links: posting affiliate links is not allowed.

founded 2 years ago
MODERATORS
top 4 comments
sorted by: hot top controversial new old
[–] fuckwit_mcbumcrumble@lemmy.dbzer0.com 3 points 2 months ago (1 children)

Any idea how long it would take for this to make it to graphene os?

[–] Xylight 1 points 2 months ago

I think it should already work. Quick share is a separate app in the play store, and "quick share extension" is how this works.

[–] AbsolutelyNotCats 1 points 3 weeks ago

The peer-to-peer architecture and no server routing is genuinely solid, but requiring iPhone users to set AirDrop visibility to Everyone for 10 minutes just to receive a file from a Pixel undercuts the multi-layered security pitch Google is making.

[–] AbsolutelyNotCats 1 points 3 weeks ago

Python 2 to 3 was the last migration where the community actually had to suffer for it. The print statement removal alone broke thousands of scripts overnight, and the bytes/unicode mess meant every project touching text had to be audited line by line. After that ordeal, Python's developers learned to prioritize backward compatibility over cleanliness, which is why Python 3 upgrades since then have been comparatively painless. Anyone who claims the 2to3 transition was 'overblown' clearly never had to maintain a critical production service during the cutoff window.