a reverse proxy these days is pretty much just a requirement of any dynamic service. they often run on the same host as the software
a reverse proxy these days is pretty much just a requirement of any dynamic service. they often run on the same host as the software
on a technicality, debts like this are not legally dischargable through bankruptcy
it does say it has a built-in serial console and raspberry pi
b2b and audited security standards are a whole different thing - you deal with finance and health you’ve gotta prove to a 3rd party over and over that you have controls and technology in place to make sure you aren’t lying
this isn’t consumer BS
and you know the security standards that are achievable on google cloud entirely negate your point right? their cloud offering is a totally different beast
there is an argument that prioritising traffic would be a good thing - pay more for high priority video calls etc, or pay less for things you don’t care about like bulk download
… but we can’t trust ISPs to wield these powers responsibly and in ways that’s good for consumers
the up side of flip flopping is that it still results in some amount of effective net neutrality… in order to develop products and build customers for them, ISPs need to actually be sure they’re going to be able to continue to offer them… industries aren’t going to rely on fast lanes, etc until they’re pretty sure they aren’t going to go away
until they lose a multi billion dollar mission because of conversion errors
anyone who enables a company whose “values” lead to prompts like this doesn’t get to use the (invalid) “just following orders” defence
it’s possible it was generated by multiple people. when i craft my prompts i have a big list of things that mean certain things and i essentially concatenate the 5 ways to say “present all dates in ISO8601” (a standard for presenting machine-readable date times)… it’s possible that it’s simply something like
prompt = allow_bias_prompts + allow_free_thinking_prompts + allow_topics_prompts
or something like that
but you’re right it’s more likely that whoever wrote this is a dim as a pile of bricks and has no self awareness or ability for internal reflection
well, there’s a schema description built into compliant graphql apis and a tool called graphiql that consumes that and provides exactly that api explorer that you’re looking for. many graphql backend frameworks embed graphiql
definitely not what people are talking about when they say front end though
peer to peer is an option too
perhaps also useful in this case to document the shortcut of
<(echo ‘{…}’)
since not many people know about it, and it makes your tool work with things specified entirely on the command line rather than temp files
alternatively —config-file and —config-json or similar
making and cleaning up temp files when writing scripts is just such a massive PITA
but you can’t interact with instagram users. AFAIK the DMA will require instagram etc to provide a gateway for services like pixelfed to interoperable with
i’m not comparing the whole thing; just breaking the problem down into parts… i’m asserting that your definition of “dead” is wrong. they are not permanently dead, because they can be revived
we have 3 potential people. either you remain at the end with 1 person, or 2 people… the choice is between action (killing tuvix to save neelix and tuvok) or inaction (allowing tuvix to live, and accepting the death of neelix and tuvok)
it’s perfectly valid to say that inaction is the ethical choice because you should never personally cause harm… but it’s also perfectly valid to say action (in this case, murder, as we see in the episode) is the ethical choice because it has the greatest good for the most people
and in fact, the latter is repeated often in star trek: the needs of the many outweigh the needs of the few
and indeed, in this episode they further throw a spanner in the works: the many includes voyagers crew, and their chief security officer
totally agree; just saying that if it’s GOT to be something, that something should probably be unless… unless . . .
and people whose heart stop… we revive them, and then they are not dead any more. if someone is able to be revived, it’s irrelevant what you called them before that point: their… let’s say potential state? is not dead
i mean, “unless” tends to be the usual term for an “if not” keyword in languages that implement such a thing
it’s possible, but that would seem… odd… for such a large and tech-savvy instance. there’s a lot of reasons why this isn’t a good idea, and very few technical reasons why it is
my guess is that it’s less about obscuring server location for privacy reasons as is the implications in this thread, and more about handling changes cleanly or something like that - in which case, sure it obscures the server location but more that it makes the server “location” (or hardware, etc) irrelevant and fungible