I meant that if someone made multiple replies within some time threshold, similar to how 'this post has been edited' works, the board could automatically join them into one post, maybe with a little indication that it's concatenated. You could even make it config option for users.
We embedded third party auditors in that crypto exchange so I'm curious exactly how inscrutable tiktok really are.
I mean the accusations are that they're too beyond oversight and we can't confidently audit the data, so giving us a button to stop them when we can't see what they're doing would be a joke. But I'm skeptical that it's as difficult to lock down their data as we make it seem.
That's what I said. Free licenses are for free software, while copyleft is for "free software." Copyleft is because corporations like Xerox will act in bad faith, etc. Free licenses are for free software. Copyleft is for Free Software, The Movement. People aren't cucks for not deigning to make every piece of code they write part of some statement.
Permissive licenses are truer to the spirit of free software but copyleft, while kind of a copout, seems more pragmatic due to corporations. I wouldn't avoid copyleft licensing on principle or anything but it feels incongruous to want to make something freely available to all but then nitpick over how they use it.
I wonder if influencers are real. People will make decisions and then gravitate towards something, and others will end up thinking that that something is the cause. But I've never seen evidence that an influencer with 1 million followers is anything other than a mustering ground for people already wanting to act out. I guess "influencer" is just shorthand for "we don't actually know what's influencing all these people, but we know where they've assembled!"
It's very weird to want strong benefits from your employer and not simply as a separate thing. Maybe that's not what he meant but the way it's listed is vague.
The Shinzo Abe situations are always weird to me. One or more people decided to do this, in the sense that the buck stops somewhere.
It's easy to find addresses, workplaces, family members, an itinerary.
It's like in order to make it to these positions you need to have a defective brain that allows you to hurt lots of other people while ignoring how easy it is for one of them to reach out and touch you. I'd need constant anxiety meds.
There are tracing programs that let you see when a program makes system calls to read and write files, control hardware, etc. It might be easiest to run it and see what it does in a VM sandbox. Process Monitor looks like a strace equivalent on windows.
It's new to me, I think it's saying that your system is built up by you declaring what you want in a file, a single source that everything comes from.
It's atomic because each action the system takes is carefully completed rather than bailing out and requiring you to fix something.
It's immutable meaning you declare how you want things to be set up and then critical changes stem from those declarations and nothing else. You would obviously generate preferences, save data, etc. but the files that make the system / packages work are carefully locked.
It's like the concept of flatpaks + structured system defining + modern common sense OS operations?
If this is local (it's a Montreal site so probably) and we're working with -4 UTC then quali is at 1700 on the 8th, right by a peak, and then the race is at 1500, near another peak.
I wish I remembered/knew how much rain fell at other races -- hopefully they get to drive.
And because corporations aren't people, here's the CEOs that ran things during 2014:
Hans Vestberg (b 1965) Verizon
Randall Lynn Stephenson (b 1960) AT&T
Glen F Post (b 1952) CenturyLink
We let these people act with impunity in our society but it doesn't need to be this way. Look at how Elon, who thrives on attention, flips out over being tracked and heckled. They stole hundreds of billions from us but we don't even act like it.
No problem. I'm no guru and I'm currently on Zig but I think learning some Rust is a really fast way to hone skills that are implied by other languages.
You could have support for this thing in the board's software, but I don't think it's common. So normally, where a post will have at least a header, sometimes also a footer, multiple posts means duplicated data on screen. Pretty minor though.
I think it fragments the workflow a bit because normally you can just quote a block and easily interject your replies + add more quote syntax. If it were multiple posts you'd need to repeat certain steps each time. Personally I want to minimize switches between keyboard and mouse. On mobile it's more even.
I see both styles here and there. It might be too much if multiple posts were the norm but when it's occasional it really doesn't matter to me. I'd rather you do what feels natural.
S. Korean government is the woman before ~20 seconds, N. Korean government is the woman after that point, and I guess regular citizens are like the people in the diner.
You use lifetimes to annotate parameters and return values in order to tell the compiler about how long things must last for your function to be valid. You can link a specific input with the output, or explicitly separate them. If you don't give lifetimes the language uses some basic rules to do it for you. If it can't, eg it's ambiguous, then it's a compile error and you need to do it manually.
It's one of the harder concepts of rust to explain succinctly. But imagine you had a function that took strA and strB, used strB to find a subsection of strA, and then return a slice of strA. That slice is tied to strA. You would use 'a annotation for strA and the return value, and 'b for strB.
Rust compiler will detect the lifetime being shorter than expected.
Also, ownership semantics. Think c++ move semantics. Only one person is left with a good value, the previous owners just have garbage data they can't use anymore. If you created a thing on the heap and then gave it away, you wouldn't have it anymore to free at the end. If you want to have "multiple owners" then you need ref counting and such, which also stops this problem of premature freeing.
Edit: one more thing: reference rules. You can have many read-only references to a thing, or one mutable reference. Unless you're doing crazy things, the compiler simply won't let you have references to a thing, and then via one of those references free that thing, thereby invalidating the other references.
I'm currently watching the Trump presser the day after, and he's straight up violating his gag order, spending awhile talking about Cohen, basically saying "I can't talk about him, but his name rhymes with Mohen, they call him a fixer, and ..."
The whole thing is nuts but just thought that was a bit special.
Memes According to Garp