2,058 karma · joined December 29, 2010
To benchmark this virtual_vec fairly against std::vector, you would need to call std::vector::reserve() with the intended number of items you intend to store in the vector before you start calling std::vector::push_back() in a tight loop.
[0] https://www.cplusplus.com/reference/vector/vector/reserve/
Lack of proper capitalization.
[0] https://en.wikipedia.org/wiki/Guillain-Barr%C3%A9_syndrome
[0] https://en.wikipedia.org/wiki/Guillain-Barr%C3%A9_syndrome
The economics I'm thinking of are along the lines of cryptocurrency energy usage per participant, vs image scanning energy per caught perpetrator. The number of caught perpetrators via this method over time will approach zero, but we'll keep using energy to enforce it forever.
All this does is remove technology from the problem of child abuse, it doesn't stop child abuse.
People like to complain about the energy wasted mining cryptocurrencies - I wonder how this works out in terms of energy waste? How many people will be caught and arrested by this? Hundreds or thousands? Does it make economic sense for the rest of us to pay an electric tax in the name of scanning other people's phones for this? Can we claim it as a deductible against other taxes?
In light of that, I then imagine that other providers are already storing photos and data unencrypted and did not object to adding scanning on the server side, and also did not share anything about the scanning with the public.
When we started down the path toward Salesforce-ification, it involved lots of bulleted feature lists. Maybe 1-2 wireframes. Then this was handed to contractors who implemented it exactly as written without an eye towards usability. Simple things like saving a ticket with some fields blank or unknown we’re not supported and made the entire ticketing process miserable.
I eventually stepped in as the voice of the “customer”, customer in this case being fellow engineers and support staff. I eventually left the company before the final implementation, but even by then no one prioritized usability and design.
Anyway, I agree with your general sentiment, and it tickles my mind. Thank you!
Spam is an interesting problem. Assuming one self-hosts and makes their email address publicly available, then one can get a metric for how much spam is flying around. Eventually one will try to stop spam from coming to their inbox, and on doing so one might build a mental model for how the big mail providers combat spam and realize why one's emails are not being delivered. Then one might realize that one is sending mail that one would not willingly receive! And then take action to resolve.
In general though, there is some base effort to establish trust, and as long as you don't ruin it by sending spam, then you shouldn't end up on a blacklist. If you find that your IP was on a blacklist before it became yours, then work with the people that are blacklisting - but at that point it does become a bit of a job. I actually ran into an issue in my professional life where an AWS WAF rule started alerting on one of our own servers hosted in AWS because someone had previously used the IP for malware C&C.
Anyway - I will think on this and see if I can write something up. It's a good idea. My main concern is that there is a gap between the way I did things (sysadmin style) and the "new" way of doing things (containerized).
Picking up litter in a park isn’t a steady job, but it’s something they can do because they’re already there, and paying them to do it seems better than handouts of equivalent value. It’s a win-win in terms of value exchange, and it doesn’t push the recipient into the mental role of panhandler or beggar or unworthy-person. They did something, they got something for it.
When I've thought through this, some of the scenarios and questions that come up are interesting and I'm not sure how things would play out. Would homeless people litter more, in order to be paid more? Would everyday people litter more because they know the homeless will get paid to pick it up? Is there any net gain for society? Would I be exposed to liability if I were the one paying these people? Should the public be the one paying?
In a way, this thought pattern is akin to finding a way to gig-economize homeless people. idk. Just things on my mind, about my community that I would like to improve.
I also heavily limited the types of things Facebook will send push notifications for. It used to be that if I got a notification, it was because one of my friends actually interacted with me in some way. Now I get a bunch of junk notifications that I feel are designed to pull me into the app and not really inform me of anything, to get me back to scrolling a feed. Like I’ll get a notification that someone I don’t know made a post in a group I’ve been in for years without ever getting a similar notification in the previous years. So I basically turned off everything that doesn't involve my actual friends doing something relevant to me.
I would look into if there is some similar audio based course in your native language that targets English.
My experience learning Spanish and French in classroom settings was that once most people see a word written, they fall back into a way of pronunciation that leans toward their native language and causes an accent. Audio only courses can help break that pattern.
The Pimsleur method should also help your use of “a” and “the” feel more natural which is going to help with your rhythm when speaking. Even as a native speaker, if I drop “a” and “the” I’m going to sound strange.
What I would like to get across is that self hosting is not impossible or unacceptably unreliable. If Google and Microsoft have policies that make it difficult to send messages to gmail or hotmail users, that isn’t a reason in and of itself that we should not self host. It’s a reason that we should work with Google/Microsoft to have better policies - but accepting things as they are and writing off self hosting as impossible is eventually accepting control of email by a limited handful of corporations, which I don’t think is a good thing.
I think maybe once in the last 3 years I ended up in someone’s spam box, total. In fact I just sent to a new gmail address and to a university I have never contacted before this week and both were delivered without issue.
Setting up DKIM/SPF/etc isn’t that hard and it’s fairly easy to verify with existing tools FYI.
Location (as well as date, time, light, air pressure...) is certainly a factor that should be used when classifying something though.
I think the problem is probably related to data collection / data integrity. At least in my case, I'm using an iPhone that has variously placed microphones and speakers. It isn't clear to me how to hold the tool to collect the sound. If it gets wet or grungy, it's not something that is user-serviceable. I don't have an easy way to tell if it even needs to be serviced. If you're relying on the microphone that follows you literally everywhere to remain clean & untarnished - maybe that's the problem?
My phone rides in my pocket, it picks up dust, it gets moist, it gets dropped, etc. Perhaps I'm projecting. Maybe your phone is untarnished and is working fine? Do you have data to back up the 100% fail rate across Europe and North America? It seems you might be projecting as well?
People see things like this and think, "Troll", hence the flagging. I did not flag or downvote in this case, as I came across it hours after it already occurred.
Not a direct reply, but Starlink will also enable some interesting scenarios around open internet access in places where it doesn't exist today - like the Middle East during the Arab Spring, or in China, or in North Korea.
I'm also the guy that found low hanging fruit in a huge codebase to replace things like frequent linear array lookups with hash table lookups for 10x+ speed improvements in the build process. This is IMO precisely the type of capability that "Oh, that's O(n^2), surely we can do better. Is there any way to do this in O(1)?" is designed to tease out in the interview process. I did it! In a build process effecting 1000+ engineers, used to build for millions of shipped units! But talking about this in an interview makes eyes gloss over as we prepare to move on to sort algorithm trivia, how would I design search, or doubly linked list implementations.
It's also my understanding that it's kosher for gentiles to perform actions outside of the constraints of the rules of Judaism, like turning on/off fans on behalf of those respecting the rules of the sabbath.
Another great aspect of the QR code driven menus is that after my meal or drink arrives I still have the menu readily available, so I can check what is in the dish or drink that's in front of me. It's great for foodie restaurants that give lots of description in the menu - before, when the meal came out I would sometimes find myself wondering what that odd shaped component was on my plate, but with a first class phone accessible menu I can get back to the description of what I ordered and figure out what's on my plate, or figure out what might be making my drink taste like bitter orange.
I didn't notice how much I liked these things until I recently traveled to Santa Fe, where every place was still using printed menus. One drink menu for a table of five? Let's all pass it around and tell the server to come back in a few minutes after we've had a chance to look one by one. Server took all of the menus after ordering, then comes around after the meal inquiring if we want dessert? I don't know what's on the menu, but I'm not interested in waiting for the server to come back with the menu. I ordered posole as a side, but forgot what the description was? I guess I'll google it...