Hacker Newsnew | past | comments | ask | show | jobs | submit | stwrzn's commentslogin

I very much hope that the backend uses one of the bluesky jetstream endpoints. When you only subscribe to new posts, it provides a stream of around 20mbit/s last time I checked, while the firehose was ~200mbit/s.


yes it does!


What happens if I don't have any active social media? Also, most people could not even produce such a list, even if they wanted to.

Would that be a permanent ban from entering the US?


Youtube doesn't even want me to watch videos anymore!

Every video is just this now:

  Sign in to confirm you’re not a bot
  This helps protect our community. Learn more


This seems to be ip-address-based. Change your ip if feasible, possibly using a vpn, and you can likely bypass that.

Or you could just do the healthy thing and walk away from YouTube. Plenty of better things to do with one’s time!


It is IP based, and my whole range is banned. I welcome it though, as you said it stops the Youtube time-wasting.


They probably meant "whois privacy"[1] (without the space). Whois is basically a way to get information about a domain name (and many other stuff). Whois privacy just ensures that your address, name and other stuff is not public.

[1]https://en.wikipedia.org/wiki/Domain_privacy


They were probably joking when they asked that question.

Your reply doesn't seem sarcastic, so I take it you genuinely r/whoosh'ed (that's a reference to a subreddit about situations where someone is acting clueless).


Realistically, I don't think HN is the place for those kinds of jokes, which are best kept for reddit/twitter.


Yeah I'm increasingly seeing these reddit-style low effort jokes on here, hopefully it's transient as folks acclimatize to the culture and customs here.


I know ;) Some people still value an explanation though.


What happens if the sender's Google account ceases to exist for whatever reason? What if Google ceases to exist?

I know that there are a lot of HIPAA "secure email" solutions that also do this, but I don't want this to become more common practice then it already is...


IMO those are different use cases. If that sender or Google itself were to disappear, hopefully the messages would just disappear too. It's better that they become inaccessible rather than public.

Long term archival is a different use case altogether, especially of encrypted materials. It's questionable whether any provider or medium can survive over the long term, so it's better to use an encryption system where you hold the keys and the encrypted data can be migrated to any sort of storage or provider over the years.


Keep HARs from the browser if you need your own record of the messages. Next step would be to determine how to extract the messages from a history of HARs and inject into your own mailbox or other storage system for archiving and search. Perhaps a browser extension to automate this automated logging of message retrieval.


Coming to Google's Blog in 2028:

Focusing on the Future of Secure Communication

[...] Starting next week, E2E emails on Gmail will no longer function, and all your E2E messages on Gmail will be deleted on February 1 2029.


I just keep all my Gmail synced into local Thunderbird via IMAP.


Doesn’t matter. If using this and I send you an email, and my account disappears, you can no longer read the email you received because it’s merely a link to read something from my account on Google.


Downloading is a "grey-zone", but no one that I know of got in trouble for that. Uploading is not allowed, and the little seeding done while downloading a torrent is still illegal. Although getting in trouble is rare because ISPs are not allowed to give out user data to random companies.


The Internet Archive uses torrents for the files uploaded to their platform.

Is that an issue that the Electronic Frontier Foundation would need to be involved in?


The Internet Archive provides direct downloads for the content they host, so the fact that they also offer torrents doesn't really change the legal situation.


Not their legal situation, but it turns a downloader into a distributor who may not be aware of the potential legal consequences.


Nice tool, however if I am correct you are calling the Google generative language API directly, your API key is exposed to the client (the browser).

If you have no spending limits, this is a very (very very very) bad idea.


damn, I can't stress this enough. You publish a key be prepared for millions on dollars of issues.


Yes, exactly. Google seems to be calm in this regard luckily as far as i know though.

OP please revoke the key ASAP


Done. Thanks both of you for pointing out my obvious mistake


Thanks a lot man. I totally missed it lol. Just fixed it.


That's concerning. I thought everyone knows that zone transfers should be generally disallowed, especially when coming from random hosts.


They were not shut down.

Confirm yourself using:

  dig +tcp @$(dig +short ns.nih.gov @a.ns.gov) www.nih.gov


Yes. As noted elsewhere in this thread, they still respond to TCP requests. I did not know this at the time of writing.


This is for sure a firewall misconfiguration. If there would be malicious intent, the bad actor would for sure not just close UDP.


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

Search: