I’m using Mullvad, too. I can almost never get a response from Imgur unless I hop exit nodes a bunch.
🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆.
𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍
I’m using Mullvad, too. I can almost never get a response from Imgur unless I hop exit nodes a bunch.
I really wish Imgur didn’t block VPNs 🙁
I’m sure it’s lovely - congratulations!
Seconded. OP, if you can write Markdown, Hugo will turn it into a website.
The best of times, architecturally.
After I responded, I did some more reading. It looks like Cyperus rotundus is the way to go. It’s quite similar, though: waxing, threading, or tweezing, apply the oil thoroughly, and then daily until the next wax; repeat a couple of times, and Bob’s your Uncle. Same efficacy, except Alexandrite lasers work only on dark follicles, whereas Cyperus works on all follicles.
How bad was it? Really? I’ve no experience, here. I’ve pulled plenty of individual hairs out with tweezers from various places; some made my eyes water. Is it much worse? If I were going to use an Epilady, I’d douse the area with numbing cream and go at it. It can’t be worse than waxing or tweezing, can it?
Am a guy, so my experience in this specific scenario is limited.
If Epilady is not acceptable, even with serious numbing, then I’d try the Cyperus Rotundus. The NIH report looked promising.
Go ahead… you can whisper it to me
Is she sure she wants to shave? There are those rolling tweezing things which I’ve never used and sound like mild torture, but pulling the hairs out by the roots usually leaves things bare for longer, and there’s no risk of getting cuts; plus, with such pliable skin in that area, it’s probably less challenging to shave.
Or, maybe an electric razor? There are also hair removal creams especially made for sensitive areas, and things like Cyperus Routundus and Oleum Cyperus oils. The linked NIH study says Cyperus Rotundus is as effective as Alexandrite laser.
I’d try a lot of things before I took a razor to my bits.
Who do I write?
Opening an office is a completely different thing; there is an enormous difference between offshore contractors and offshore employees. That much, I’ll agree with.
In the US, though, it’s usually cost-driven. When offshore mandates come down, it’s always in terms of getting more people for less cost. However, in most cases, you don’t get more quality code faster by throwing more people at it. It’s very much a case of “9 women making a baby in one month.” Rarely are software problems solved with larger teams; usually, a single, highly skilled programmer will do more for a software project than 5 junior developers.
Not an projects are the same. Sometimes what you do need is a bunch of people. But it’s by far more the exception than the rule, and yet Management (especially in companies where software isn’t the core competency) almost always assumes the opposite.
If you performed a survey in the US, I would bet good money that in the majority of cases the decision to offshore was not made by line managers, but by someone higher in the chain who did not have a software engineering degree.
Thing is, outsourcing never stopped. It’s still going strong, sending jobs to whichever country is cheapest.
India is losing out to Indonesia, to Mexico, and to S American countries.
It’s a really stupid drive to the bottom, and you always get what you pay for. Want a good development team in Bengaluru? It might be cheaper than in the US, but not that much cheaper. Want good developers in Mexico? You can get them, but they’re not the cheapest. And when a company outsources like this, they’ve already admitted they’re willing to sacrifice quality for cost savings, and you - as a manager - won’t be getting those good, more expensive developers. You’ll be getting whoever is cheapest.
It is among the most stupid business practices I’ve had to fight with in my long career, and one of the things I hate the most.
Developers are not cogs. You can’t swap them out like such, and any executive who thinks you can is a fool and an incompetent idiot.
And 123’s a nice, round number
That’s comforting!
The metal flashing could just be standard, but people do add that to prevent damage to the door. The dripping down the door looks like it may have been cribbing, so they may have added the bars to limit damage to the wood.
I think Android updates intentionally made the Pixel C slower. It was a noticeable process, up to the point they stopped supporting it. I’d downgrade to an earlier version, but there’s such poor support in Lineage, I’m barely able to run the version that’s on there now.
Such a shame, because it’s still an amazingly beautiful device.
I’m 100% with you. I want a Light Phone with a changeable battery and the ability to run 4 non-standard phone apps that I need to have mobile: OSMAnd, Home Assistant, Gadget Bridge, and Jami. Assuming it has a phone, calculator, calendar, notes, and address book - the bare-bones phone functions - everything else I use on my phone is literally something I can do probably more easily on my laptop, and is nothing I need to be able to do while out and about. If it did that, I would probably never upgrade; my upgrade cycle is on the order of every 4 years or so as is, but if you took off all of the other crap, I’d use my phone less and upgrade less often.
The main issue with phones like the Light Phone is that there are those apps that need to be mobile, and they often aren’t available there.
ntfy is in the app store, so you don’t have you side load it. I don’t know how many iOS apps use ntfy, but many Android OSS apps will ask you over which notification system you want to work.
I was just clarifying that this isn’t one of the XKCD proliferation cases. Apple and Google’s push notifications are proprietary and give them full access to your notifications. Unified Push is the OSS alternative, and this KDE enhancement doesn’t createa another one: it uses the defacto standard OSS push notification specification.
The fact that ntfy is in the Apple app store makes me suspect there must be some number of iOS apps that can be configured to use Unified Push.
since all apps are designed to run well on budget phones from 5 years ago, there’s no reason to upgrade.
5 years, maybe, but any more is stretching it. And not getting system upgrades anymore is problematic. Unless you own a particular model of phone, de-Googled Android can be hard to come by.
For example, I have a 7-year old Pixel C. By the time Google stopped using system updates for it, I wasn’t wanting them as every release made the device slower and more unstable. After some effort, I was finally able to install a version of Lineage, which itself has problems including no updates in years. There’s a lot of software that is incompatible with my device, both from Aurora and FDroid.
Android isn’t Linux; Google doesn’t care about maintaining backward compatability on old devices, much less performance, and there’s no army of engineers making sure it is because there’s a served running in walled-up closet no one can find.
Google deprecates features and ABIs in Android, apps update and suddenly aren’t backwards compatible.
5 years, maybe. The entire industry is addicted to users upgrading their phones, and everyone gets a piece of that pie. There’s no actors, except perhaps app developers, who have any interest in keeping old phones running. Telecoms upgrade their wireless network - the internet connection in my 8 y/o car, and half its navigation features, died the day AT&T decided to stop supporting 3G; Phone makers make no money if you don’t buy new phones; and maintaining backwards compatibility costs Google money which they’d rather siphon off to shareholders.
Good thing women have a higher tolerance for pain. Or so I’ve heard.
I don’t know. Women put up with a lot of painful stuff; threading doesn’t look like any fun, either. I guess it just depends on the individual.
For those not willing to do that, the Cyperus Rotundus oil looks encouraging.