Once some users have extra power to push content to the front-page, it will be abused. There will be attempts to gain that privilege in order to monetize, profit from or abuse it in some other way.
The only option along this path would probably be to keep the list of such users very tightly controlled and each vouched for individually.
---
Another approach might be to ask random users (above certain karma threshold) rank new submissions. Once in a while stick a showhn post into their front page with up and down arrows, and mark it as a community service. Given HN volume it should be easy to get an average opinion in a matter of minutes.
I was hoping to see one of his posts here. If he's going to post under an alt, he should advertise it so that I can know which posts I should be taking extra ironically.
Worse than that, lets remember that WG14 rejected Dennis Ritchie proposal for fat pointers, and the C authors decided it was more fun to keep their own way with other programming languages than try to improve C from WG14.
I think we are talking past each other. I was saying that passing an array with a size to a function was standardized 27 years ago, asking if that isn't long enough. Sure, some may don't like how it was standardized, but it is possible.
Beside the sibling comment about this specific proposal, I also think that fat pointers don't belong in the C standard. There is nothing in the C standard that says that pointers on the abstract C machine don't come with the allocated size, in fact the behaviour is described as if they do. Pointers are essentially scoped by allocation. All that is missing is code for that in a C implementation, the language allows that just fine.
I read through the RFC and I think it's fair it was rejected, because this was ultimately a half-measure, with severe usability restrictions.
Fat pointers are clearly a way to deal with arrays (and also get "slices" and non-zero terminated strings for free!), but it's just not possible to retrofit them into the language without breaking existing code.
You can conceal that open port with some form of port knocking. Though this does reinforce your "easy" point.
Also, if it's an UDP port, then using a protocol that expects first client packet to be pre-authenticated and not emitting any response otherwise gets you pretty damn close to having this port closed.
I looked into it but it seems that port knocking and Single Packet AuthZ literally open the firewall and expose the port when used.
Meaning it is great to reveal the SSH port when needed, do your business quickly and close it back when you are done. But my guess is those overlay networks need to port available all the time, so...
I witnessed something recently that points unambiguously at Whatsapp chats being not private.
Not two months ago I sent a single photo to a friend of some random MacGyver kitchen contraption I made. Never described it, just a photo with the lol. He replied lol. He never reshared nor discussed it with anyone else. We never spoke about this before or after. Two days later he starts seeing ads on Facebook for a proper version of the same. There's virtually no other explanation except for Meta vacuuming and analyzing the photo. None.
Machines are really good at putting two and two together and humans are generally not. Are both of you completely sure that you didn't google anything related to the image before or after?
While Meta doesn't have access to the contents, they do know who you're texting and when.
I don't think the claim was that the commercial device never existed but that it was too obscure for the friend to randomly independently get targeted ads about it..
But I don't think WhatsApp takes many steps to protect media and in many cases the user really wants to backup media or share in other apps, etc, over security for media.
Once some users have extra power to push content to the front-page, it will be abused. There will be attempts to gain that privilege in order to monetize, profit from or abuse it in some other way.
The only option along this path would probably be to keep the list of such users very tightly controlled and each vouched for individually.
Another approach might be to ask random users (above certain karma threshold) rank new submissions. Once in a while stick a showhn post into their front page with up and down arrows, and mark it as a community service. Given HN volume it should be easy to get an average opinion in a matter of minutes.reply