drenvuk

they can't be argued with if they don't engage in civil discourse. the only option is to replace them with someone who will or remove their ability to affect the world in any meaningful way.

Why do some people seem to think that it will stay limited to that forever? It's not just you, it's multiple people in here who think that this is ok. They are our devices. They should not be running software that can get us arrested on our devices. It won't stop there. It never stops there when they can ask for more.

1. Their credentials provide some legitimacy to this endeavor.

2. They get to do some interesting work.

Those are the positives for them I see.

Rather than abstaining they work on it and lend their names. I don't know whether they support what Apple is doing with the protocol or if they just like figuring out the possibilities. I don't think either is good in this case because I don't like the very first application of this PSI System. Maybe I'm being short sighted and jumping to conclusions all at once. I still don't like it.

A drive for incrementing their number of citations wasn't what I was getting at.

Thank you for the purely informational post and I'm currently reading through the second just to understand this more thoroughly but I can say already screw the proofs. Apple needs to stay off my devices with their crime scanning bs. It doesn't matter if this whole scheme ensures that Apple cryptographically keeps their hands clean. The effect is the same. They're on my device looking for things that can send me to jail.

These brilliant academics just don't care so long as they can publish an interesting paper I guess. Whatever, still reading.

You've never considered that maybe growing up apart from the groupthink would be helpful to a child? Did you ever wonder why Jobs and all of the other tech ceos don't let their kids have these consumption devices? They're in charge of of this stuff yet they keep their progeny from utilizing it. But you actually want to give it to them as if there were nothing wrong with it because it's socially acceptable?

Your line of thinking is ridiculous but please continue.

Yes, yes, we all know. It's not like this is one of China's new policies. Tell me something new please.

I can see why hackernews was (is?) banned in china. You guys see nothing but negatives in any policy decision that comes out of there. Sure there are some power struggles, sure there's a powerful cadre of billionaires who own the politics of the country but aside from the pretty disgusting issues with the Uighurs I would consider china up there with Norway in terms of country development.

If you just contrast what Xi is orchestrating vs what's happening in the US with open eyes, you'd see that maintaining the status quo is impossible. We're too fat and complacent and there are too many leeches on government spending. This is the holy shit kind of article that made me realize we're going to lose our place on top. I don't even know how to help stop it.

if it's because of muscles, you should really be training your neck but adjusting your pillow to support your head works as well. it's a bit more finicky though. If it's flexibility you've gotta do more stretches just for your health.

Anyone complaining about the pain doesn't know how to work in bed. lie face down and prop your chest up with a pillow. you can work for hours that way. When that gets tiring, roll over, and brace yourself against the backboard or wall with the same pillow to support your lumbar. repeat for zero back stress computer programming.

Did you read the paper in its entirety? Honestly, did you?

It is filled with well researched arguments and quite a few facts that I found highly surprising. I say this as a guy who went from 270 lbs down to 180 then back to 240 then down to 200 and still struggling to stay put. The descriptions of leptin induced neuroses and people's varying mental states is highly accurate. The number of different cultures that don't have this obesity issue, my previous girlfriend who grew far fatter and taller than her peers after coincidently being fed antibiotics for a long term illness as a child.

For goodness sake, did you even get to the part about the Macaques and the standard bmi distribution growing just like humans are? This situation isn't normal and congrats on losing weight but you're one triumphant data point in a growing sea of obesity.

linkedin. if you ever hear "thought leader" in a sentence you should default to "virtue signaling gas bag", the majority of which congregate on LinkedIn, trying to attain a weird sort of guru status and build a following. Sometimes you get people with a good point a view, like this guy. Most times not.

If I'm wrong list some movies, please. I will watch them. I've seen enough foreign films to see many of the techniques used between films and between directors.

Maybe? I'm willing to bet that after 810+ movies he'll have seen all of the tropes and techniques trotted out by those outside of Hollywood. How many ways can you really tell a compelling story or possibly show an artistic experience?

They're sortable. I don't see what the issue is. Can you explain?

I don't care what the name of something is so long as it does what I want and has a form that I can understand and utilize.

This is wrong depending on the use case and where the user is and where the user might be going.

This is why dates are such an issue.

A timestamp is the number of seconds or milliseconds or units like 1624938650 seconds from epoch UTC. What I posted above are human parseable datetimes in ISO 8601. Each of them is a point in time that depending on the locale and tz fall on two separate dates but the most important aspect is that it doesn't matter whether I'm using them in my DB or on a user's machine in a different locale and tz. That's the point.

while developing my project I ignored what the officially named format was and simply checked what converted properly between three browsers.

Safari: "2021-06-28T22:59:18.366Z"

Chrome: "2021-06-28T23:01:09.131Z"

Firefox: "2021-06-28T23:00:14.385Z"

The three that I strive to support all utilize this format. YYYY-MM-DDTHH:mm:ss.sssZ. Looking on MDN this seems to call toISOString() which returns a simplified extended ISO format date.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Sure, my bad. You know what I mean though.

>Now it gets saved in a DB as 2021-06-27Z23:00:00

Why would you ever do this? Save it as a JSON date. coolDate.toJSON() would give a timezoned human parseable date. Just parse it back to the users locale with a built in Date constructor. You can do milliseconds UTC but someone like my younger stupid self would screw it up like most people.

There's enough other advice here that I just want to focus on one area on the safe assumption you're a straight male: Tinder is pretty toxic for men. Now that things are opening up you should get out and meet people in person. For romance sure, but friends or even acquaintances as well. Tunnel vision caused by desperation doesn't help either. Relax and branch out. Fail with people and try again with others. And again, Tinder is toxic for the majority of males, use it if you like, hell get good at it but understand that your match count and profile are not you and those chat based interactions are empty and fleeting.

And don't kill yourself. At 23 the world is your god damned oyster even if it doesn't look like it. Your back probably hasn't even gotten achey yet.

other enrolled devices. please check the provided links.

why build your own? just use element and matrix.

Can someone please tell me how important this topic based on the amount of news time and eyeballs it attracts relative to the number of people that it affects?

The numbers I can find for US citizens is: 0.6% or 1,988,696 out 331,449,281 of people total for the entirety of the US in 2021.

>https://en.wikipedia.org/wiki/LGBT_demographics_of_the_Unite...

In the UK where the featured article took place the latest poll I could find comes counts the number of people who selected "other" when choosing a sex at 0.4% or 224,632 people out of 64,596,800.

>https://practicalandrogyny.com/2014/12/16/how-many-people-in...

Personally I don't think this is very important compared to other topics. There are more blind people than trans people. There are more people with Alzheimer's than trans people. There are more people in the US who have lost a limb than trans people.

I don't mean to downplay what is happening because it is happening but do you not think the amount of outrage this topic generates surpasses the level of impact we can have assuming we fix it? It just feels like we're being distracted.

It's surprising how confident you are when you know so little. localStorage and indexedDB are very different in how they store data and read data, you also don't know the advantages both have over storing data on a server without using it as a full blown relational db.

The filesystem api would actually be a godsend regardless of whether if it would be limited to a single site owned directory or not. Right now we're limited to indexedDB, which is better than before where we only had localStorage, but persistence is a constant concern. I am always worried about whether the browser will just up and delete things. If they make everything be private and unsharable i.e. limited to a single domain, that includes no sharing between subdomains it would be perfectly viable.

The most important thing to note here is that we're looking to escape vendor control. A lot of people miss that. If browsers can get feature parity with apps that means no more app stores. no more app stores means more freedom of choice. Maybe that's not good for grandma but it's good for you and me.

There are a few decisions by chrome developers that I will never support, like a bunch of stuff in Manifest V3 but hopefully with other browser companies will provide a way around boneheaded, selfish corporate decisions while we reap the benefits of better integration with the operation system.

You're not the only one. Coroutines are complicated as hell and have too much boiler plate BUT once you handle it for a general enough case you get javascript-esque async await syntax which is very, very nice.

Take for instance, this code which relies on libuv for its event loop and co_await to retain its state during its execution: https://gist.github.com/Qix-/09532acd0f6c9a57c09bd9ce31b3023...

Lets say that you want to batch a bunch of database operations into one transaction. You could queue them up over the course of a few milliseconds, run the transaction, and then for each context that relied on different db operations simply return to each's previous point instead of having to call a handler. Granted, the handler is now inside of the `await_transform` needed to work with `co_await` but think of the possibilities. No weirdly separate callback function, no real need to make a class that encapsulates all of the operations for let's say a user's post request, and to top it all off, you can do this on a single thread. It's a tool for cleaner code but I'll be damned if it is really easy to understand.

It's just so much stupid boiler plate and a strange way of putting it together.

I'm of two minds with regards to this: This is cool but unless you have no authentication, data to fetch remotely or on disk this is really just telling you what the ceiling is for everything you could possibly run.

As for this article, there are so many knobs that you tweaked to get this to run faster it's incredibly informative. Thank you for sharing.

it will settle. Just keep trying, we'll get back together.