Hacker News new | past | comments | ask | show | jobs | submit | osipovas's comments login

Looks like they're doing some sort of geo-filtering. I wasn't able to sign up from Canada.


Same. I rarely give out my email address for a waitlist, but the "Prefer More" screenshot showing that you can influence the rank of individual sites is a feature I've wanted in search for ages. There are so many sites I'd like to delete from the internet when I search with Google / Bing.


Same here in Europe. That's probably a good thing for them as it looks very US focused for now (as many products are), so providing a lesser service to users outside their currently active markets prevents bad user experience & bad reviews. I won't hold my breath waiting for it to hit Scandinavia.


In the examples they provide at the bottom of the article - my instant reaction is - these tunnels can replace ngrok tunnels.


Yeah according to our logs, our messages started failing to send at Feb 26 13:01:24 UTC.


Can confirm that's about right.

One thing that I find interesting about that, is that's -just- after the TCPA window opens in the EST time zone. The other reason that raises my brow is this status update...

> Twilio services are now operating normally, however processing of Programmable Messaging queues was delayed during the incident.

Emphasis mine.


If you're in the USA - Snug Safety is a great option for seniors living alone who are not ready or don't want a Life Alert necklace.

Website: https://snugsafe.com

Snug is available for Android (Google Play) and iOS (iPhone only).

Disclaimer: I currently work on Snug Safety. Please send any questions to support@snugsafety.com and we'll definitely be able to answer them.


What does it say about Alphabet that I expected to see a: We're closing down Project Jacquard. After clicking the link...


This will be frustrating when Google decides (as they always do) to stop supporting the older hardware. I use the Home Edition for my parent's computer. The update process is virtually seamless for my parents and it just works.

What to do when they end support...


ChromeOS has been going through a big process to divorce the browser updates from the operating system updates, so that they can continue to deliver updates to the browser itself even after older hardware stops being supported.

as it is, you can keep using the old hardware after support ends, you'll just have an outdated browser and linux kernel. In the future, that problem should be reduced to just having an outdated kernel.


Is there a similar project that releases current Android distros for post-end-of-support android phones?


If I were splitting hairs about it I wouldn't personally call the bulk of them "distros," if only because the overall Android ecosystem is that much more homogeneous compared to one like GNU. The extent to which features or visual tweaks are added will vary, but your underlying system will generally be the same regardless of whether you're running LineageOS, Paranoid Android, Carbon or most others. (Some exceptions include Bliss, which maintains a desktop-focused x86 build; /e/, which is specifically built around MicroG; and GrapheneOS, a hardened build specifically for Pixels.)

With that said though -- yes, if you're into modding or general preservation there are a variety of community spins of Android, and potentially even a small scattering of other Linux-based systems depending on your device.

Now that Android requires the use of a GSI -- or generic system image -- in testing, device compatibility is also significantly better than it used to be. That said, you're still limited to those that support bootloader unlocking. (Notably, while they don't implement this internationally, if you're US-based Samsung is out.) Additionally, GSIs will still have edge cases around drivers (since they don't have to actually work on production devices), Google apps generally have to be loaded separately, and even then the act of opening your bootloader to begin with trips SafetyNet -- which breaks everything from banking apps (for the sensitive-data protections this was originally intended to cover) to Netflix (for DRM) to various games (for anti-cheat) to... Snapchat for some reason?

Where this starts to really get exciting is that, over the next year or two, that requirement for generic image compatibility will be extending to the kernel, on devices that are actually shipping to users. Treble's launch triggered a sort of second wave within the custom ROM scene, as it meant they no longer strictly needed to be ported to devices on an individual basis -- a limitation which up until now has still existed for the kernel.

Some particularly interesting details around this are that a custom kernel is required to run Halium (a GNU compatibility layer for Android devices that allows images like Ubuntu Touch to be loaded as GSIs), and that Android 11 can actually boot on a minimally-patched mainline assuming that all necessary drivers exist.


Why did they call them Plex? Come on Google! Plex is already a trademark.


Can we get a 2019 in the title?


A service I run on Digital Ocean was affected by this early this morning. Looks like it was mitigated by DO - so I'm very grateful for that. Although, the service I run is time sensitive so failures like this are pretty unfortunate for me. Where would I get started with building in redundancy against these sort of outages?


As an Albertan living in Edmonton and as per the feasibility study mentioned in the article, I don't think this is happening. That said, if by some miracle it does happen, that would be awesome!


Also Albertan. Maybe it's unrealistic but I agree it would be pretty awesome to see in my lifetime. Would also be cool to see Alberta get on the map for something other than oil.


Yet another Albertan. I would expect the AB government to not directly fund something like this. P3? Privately owned and operated?

Still unlikely.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: