If you`re struggling to get jeans to a particular fit, you can get them custom made to your required measurements at https://www.makeyourownjeans.com/. They’ve got a good selection of fabrics, and I can recommend getting a gusset put in to significantly extend the life of the jeans.
I’m a satisfied customer but have no other affiliation with them.
A suitably large catapult would deliver the necessary delta-v, not release pollutants into the atmosphere, and would make a satisfying ‘sproing thump’ noise in doing so.
Yes, I think the chicken would need to be rotating, you should use both hands to spread the warmed area, and be prepared to administer more slaps than were calculated.
You could say you just go round and round hunting for it, but no matter how hard you try you just can’t corner it.
Well, you could.
One must also consider the thermal conduction of the chicken. Slapping it, either once or multiple times, on a single area will impart energy to that area, raising the temperature there, but it will take time for that to disperse throughout the fowl. Thus will inevitably lead to the slapped area/areas being overcooked and the rest being dangerously undercooked. Losses to the environment must additionally be taken into account unless sufficient insulation is employed to mitigate this.
Bend them the other way. Start with all fingers open for zero, and curl them as needed. You only need to move them a bit, so even twenty (thumb and ring finger back, the others curled) isn’t too hard.
I agree that them having users’ phone numbers isn’t ideal. There are other identifiers they could use that would work just as well. However, both the client and server are open source, so you can build, at least the client, yourself. If you can content yourself that it does not leak your ID when sending messages, then you don’t need to trust the server as it does not have the information to build a graph of your contacts. Sealed sender seems to have been announced in 2018, so it’s had time to be tested.
Don’t get me wrong, the fact they require a phone number at all is a huge concern, and the reason I don’t really use it much, but the concern you initially stated was addressed years ago and you can build the client yourself to validate that.
You’re correct that if you use the system the way it used to work they can trivially build that connection, but (and I know this is a big assumption) if it does now work the way they say it does, they do not have the information to do that any more as the client doesn’t actually authenticate to the server to send a message. Yes, with some network tracing they could probably still work out that you’re the same client that did login to read messages, and that’s a certainly a concern. I would prefer to see a messaging app that uses cryptographic keys as the only identifiers, and uses different keys for different contact pairs, but given their general architecture it seems they’ve tried to deal with the issue.
Assuming that you want to use a publicly accessible messaging app, do you have any ideas about how it should be architected? The biggest issue I see is that the client runs on your phone, and unless you’ve compiled it yourself, you can’t know what it’s actually doing.
Strictly you’re having to trust the build of the client rather than the people running the server. If the client doesn’t send/leak the information to the server, the people running the server can’t do anything with it. It’s definitely still a concern, and, if I’m going to use a hosted messaging app, I’d much rather see the client built and published by a different group, and ideally compile it myself. Apart from that I’m not sure there’s any way to satisfy your concerns without building and running the server and client yourself.
‘Sealed sender’ seems to avoid this by not actually requiring the client to authenticate to the server at all, and relying on the recipient to validate that it’s signed by the sender they expect from the encrypted data in the envelope. As I mentioned in another reply, I’m just going on what they’ve published on the system, so either I could be completely wrong, or they could be being misleading, but it does look like they’ve tried to address this issue.
Whilst I absolutely agree it’s correct to be skeptical about it, the ‘sealed sender’ process means they don’t actually know which account sent the message, just which account it should be delivered to. Your client doesn’t even authenticate to send the message.
Now, I’m just going on what they’ve published on the system, so either I could be completely wrong, or they could be being misleading, but it does look like they’ve tried to address the very issue you’ve been pointing out. Obviously it’d be better if they didn’t have your phone number at all, but this does seem to decouple it in a way that means they can’t build a connection graph.
With ‘sealed sender’ your phone number, or any other identifying information, is not included in the metadata on the envelope, only the recipient’s id is visible, and it’s up to the recipient’s client to validate the sender information that is inside the encrypted envelope. It looks like a step in the right direction, though I don’t use signal enough to have looked into auditing it myself.
I know it’s trite to say “calm down Satan”, but, calm down Satan. You’ve captured the spirit of a Fae deal really well.
It’s a non-starter for me because I sync my notes, and sometimes a subset of my notes, to multiple devices and multiple programs. For instance, I might use Obsidian, Vim and tasks.md to access the same repository, with all the documents synced between my desktop and server, and a subset synced to my phone. I also have various scripts to capture data from other sources and write it out as markdown files. Trying to sync all of this to a database that is then further synced around seems overly complicated to say the least, and would basically just be using Trillium as a file store, which I’ve already got.
I’ve also be burnt by various export/import systems either losing information or storing it in a incompatible way.
From the article it’s in the form of hydrated salts, so it’s not drinkable as it stands, but I expect it could be extracted and purified to be so.
I think that the point is it’s entirely pointless building something like this into the email system. It should be a separate system that you can choose to use if you want it. Building it in just opens questions about exactly what they’re doing with your data, despite their assurances.
‘This post is a palaeontological disaster’ is a marvelous turn of phrase, and I intend to steal it for use at the first opportunity.
Well yes, humpback whales reach sexual maturity by around 10 years of age (some much before then it seems). A marine biologist is still practically in it’s larval form at that point.
(Yes, yes, I know that wasn’t what you meant, but I couldn’t help myself)
Crabadile - the ultimate lifeform.
Isn’t one of the main issues with carbon-monoxide that hemoglobin preferentially binds with it over oxygen, and so it doesn’t get expelled from your bloodstream via your lungs? You can tolerate quite large doses with little more than a headache, so I doubt you could overdose from internally generated amounts, but a large enough dose dangerously reduces your blood’s oxygen carrying capacity.