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

QRcodes are unrestricted in size. it's just a quetion of resolution and redundancy...


same with gps - the user should deside how to open direction / location links.


I wonder where they host

>>> Bandwidth Restricted

The page you have tried to access is not available because the owner of the file you are trying to access has exceeded our short term bandwidth limits. Please try again shortly. Details:

451 Actioning this file would cause "jbkempf.com//blog/2024/ffmpeg-7.1.0/" to exceed the per-day file actions limit of 160000 actions, try again later >>>


FastMail :)


huh good to know! I've been switching things over to Fastmail but haven't tried their web hosting yet. Perhaps it's not a great choice...


The hn high of death.


nitter was awesome but since x, i just ignore the twitter void ... https://nitter.cz/


As that site states, public Nitter instances are no longer viable.


i tried LineageOS, shortly after i also wanted to try e/os (..because of my proprietary banking app...) and was amazed how easy the e/os flashing+setup was. Also with e/os you have way more control over features like e.g GPS where you can not only enable/disable GPS but you can also provide fake GPS data for apps which force you to turn it on.


that explains why there is no buidtool.


Well of course, there can still be bugs in the code even if 200 is returned.

I always implement a /~/healthcheck route which will return the exit code of each check, but also encodes it in the HTTP STATUS. if any error is detected the status will be 500 if any warning is detected it will be 200+<numberOfWarnings> of course checks still need to be written, e.g. a code needs to verify that it can connect to ssh and is greeded with the correct login msg.

still there could be problems for outcomming connections.


but now you have 2 up paths. and migrations are critical, i would avoid it where possible!


so the main Problemes are the users which provide wrong or loose identification.

why should google care? mybe go after the company who sold them a phone/PC? or after there Parents who got them born in the first place..


> why should google care?

Well, if "we" want to prevent a scenario where Alice provides wrong/loose identification to Bob and Bob accepts it, there is only really two realistic ways to do so: force Alice to not do this, or force Bob to check (maybe with "our" aid). Or do you propose having Victor who would regularly come by Bob and check all of the new identifications provided from the all of Alices in the meantime?


I think yellowsir actually has a point, and I'm the one they responded to. For search I think Google should care, as their users will eventually leave if they can't find reliable information. YouTube on the other hand... I don't see any business reason for them to care about content quality or authenticity - they make money from every video people watch.

To my first point, I don't know how any Google competitor is going to provide more reliable information until the root problem of authenticating sources is solved. So maybe there is really no reason for them to care after all.


and who will maintain it?


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

Search: