kenniskrag

the person is usually accused and maybe not guilty. Normaly you let them finish the exam and start the legal stuff afterwards (proof, counter arguments etc.)

Nexus Mutual InsurAce is a small insurance, which isn't backed by a bigger insurance. Traditional insurances can cross protect the risks e.g. fire & water, europe & asia or sell some risks to a reinsurance company. Maybe there is no regulation on how much reserves in fiat they have to keep. So no not the same protection.

> everytime the host of the current/next blob o' data goes offline, you need to waste time finding a replacement

Ther is an algorithm in place where the rarest is downloaded. Also a priority list of older peers is implemented. Some protocol also request the chunk from muliple peers (kademlia).

They can. If it is strong enough you can feel dizzy if you move the head.

Heat and nerve stimulation is also possible according to https://en.m.wikipedia.org/wiki/Safety_of_magnetic_resonance...

Isn't that solved with c++ modules [1]?

[1] https://en.cppreference.com/w/cpp/language/modules

> are often drafted by newspapers in advance

I also saw that with sports topics.

can I do that with non existing domains or mal. login attemps in a nginx config? That would maybe slow down the attackers a little :)

if you want to test these settings I can recommend `sudo systemd-run -p "DynamicUser=yes" -p "ProtectSystem=yes" -p "ProtectHome=yes" --shell` but be in a readable directory like /tmp or you receive an error.

maybe use something like goatcounter or selfhost the analytics.

To 3:

You can encode html in feeds. You just have to mark them as cdata.

If you know sqlite there is also a json extension for filtering. Here a link to the example section: https://www.sqlite.org/json1.html#examples_using_json_each_a...

They start 12 containers and recommend 2 core cpu with 4GB RAM. At least 2 GB RAM. [1]

[1] https://bitwarden.com/help/article/install-on-premise-linux/

Put the zip file to your static site, mirror to bitbucket, mirror to sourcehut. I have more doubts, that you don't find the code. Maybe a link inside the CVE would be good.

There are only native packages + 1 external packages suah.dev/protect.

There is row level security. But that usually means many db users or sometimes usergroups are supported.

https://www.postgresql.org/docs/current/ddl-rowsecurity.html

The cron should run always.

They have a rate limit for the amount of renewed certs. This doesn't apply if you don't reach their servers or don't get a cert.

But if you have a problem with a CA just switch to another which supports your bot (e.g. acme compliant CAs).

That's why we renew our certs more than one day in advance.

Keepass2Android also supports webdav, http, ftp, sftp and nextcloud directly

in the the man page they say only legacy

> The /dev/random device is a legacy interface which dates back to a time where the cryptographic primitives used in the implementation of /dev/urandom were not widely trusted. It will return random bytes only within the estimated number of bits of fresh noise in the entropy pool, blocking if necessary. /dev/random is suitable for applications that need high quality randomness, and can afford indeterminate delays.

and recommend:

> Linux 3.17 and later provides the simpler and safer getrandom(2) interface which requires no special files; see the getrandom(2) manual page for details.

Are you always connected? If not how do you receive the answer?

In my university we can take photos after a topic was explained. The prof told us, that he wants us to understand the topic and ask questions while he was explaining.

if the user agent is linux, they provide the isos. Otherwise they want you to use their creation tool.

On "cloud" servers I usually do a snapshot before the upgrade. That way I can revert to it in a few minutes.

I have to push the hashes (DS records of the ksk) to the parent zone (tld). I think that only can do my domain registrar.

I like hetzner but they do not support dnssec yet.

https://docs.hetzner.com/dns-console/dns/general/dnssec/

> In my book

Which book?

I see know that one can think of the domain model as most changed layer and if there is a bigger change it is because the domain model changes (e.g. business requirements). So a dependency from the domain model to other parts below are mostly fine.

So you create a class in the Domain which is responsible to save the domain object? And inside of this class you map the domain object to the persistency model? Is that not a forbidden by the layer principle because now the domain model layer has a dependency to the persistency layer.

I usually create "Service" classes in the domain layer, which use Repositories. These repositories are a wrapper for the DbContext to allow unit testing. Where do you put your domain logic? Do you have a domain model or is your persistence model your domain model?

> I am tempted to merge it with the HTTP model as well, add JSON tags to it.

If you add a property which shouldn't be public you have to separate them. For example in the domain model you have a user with email but do not want to expose the email.

Second argument: I usually create a simple struct for each method. For example I do not want, that they provide the id for post requests. I want to send the id on get requests so that they can send an update request with the id. I prefer only "non-null" arguments and as a bonus you get a clean (auto-generated) api documentation.

What I nerver understood:

* How to disconnect the domain model from persistence.

Some solutions add the OR Annotations to the domain model. Some other map the domain model to persistence with a Mapper-layer.

But all of them have some constraints. For e.g. on a web api I receive a dto, map it to a domain model, map it to a persistence model and vice versa. Not much gained imho. In this example I would add the OR-annotations to the domain model and configure many-to-many by "text" so that they are not contained in the domain model.

What are your thoughts?