tmd83

What I don't understand (perhaps I haven't found the right docs to read) is how to safeguard the secret if a client machine of the secret is compromised. Say I have a web server that's connecting to the database and the database credential are stored in some separate value. If someone get's access to the web server machine can they not access the value from there?

One of my favourite kindle feature :) it fits in most of my back pockets. I like to read while on the road, when waiting etc and not having to carry it on my hand which is a hassle and not forgetting in random place is a big feature for me.

What are the top choices everyone would suggest in terms of Linux OS for reasonably upgraded packages, package availability in terms of dev/tech person and perhaps most importantly a sane and reasonably pain free upgrade path (no reinstall every year or something).

How does the Aktiia thing actually works?

How does one do something like this https://github.com/mame/quine-relay

Does anyone know the core concept?

Exactly and this being enabled by default seems specially more unusual. I can understand config being parseable even though log configurer directly pulling a remote config is a stretch specially by default. But I don't think it's unlikely that people would by default assume that their log message would be parsed that way and as someone said it even works if that's used as a user input using {} instead of +.

Does that mean it's only vulnerable if JMSAppender is used otherwise not? Which should at least be a rarer use case.

It's hard to name things. There's consumers whose data the system records, by resource I meant the data of the consumer (bulk of the system) and obviously users.

The users are authorized on consumer (a set of consumer + a set of roles or action they can do). We have been able to move the role aspect to app layer very cheaply. User A is doing X say running a report, we know role R is needed for it, we then ask the system run the report for the customers user A has access to it with index on consumer for all resources in system allowing fast query. But if your consumer list is too large the efficiency falls.

We can't make auto groups at system level because adding a group column in resource level and updating would be too expensive. There's no just large grouping. Some users say have access to consumer 1..100K where another has random 100K from 1..1M.

I have a similar use case but even worse. Rather than locations users are given access directly to the consumer/patient and the each resource is for some consumer x. So any access not just reporting we have to filter by a huge list of accessible consumers which sometimes can be as small as 50 but large as 100K+ which is massive challenge to scale.

We can obviously manage this still with careful optimization but I'm not sure if this is kind unlimitedly scalable say for 1M+ consumers. I wonder if this can only be handled by reframing business requirements (like location as you are using) or someone has better design/ideas.

And you probably don't even have to make it a whole lot of thicker or weightier to have a better heat dissipation at least these days. Just a little thicker which still keeps it very portable and probably increase grip in fact will get a lot more room for fan/airflow which probably don't increase weight to that degree.

Just beautiful and a quick scroll seems to suggest a fairly involved undertaking. Hoping to have fun reading it but for now just enjoyed the look of it,

I think having so many sides adds a lot of visual appeal.

Let's not forget that Oracle DB uses the system timezone as the datatype storage (not sure what other database do to be honest) so unless you were running your DB machine as UTC by default their timestamp storage would be ambiguous for DST shift and that's their default. Why wouldn't they store everything in UTC and use the system timezone for parse/formatting I have no clue.

What about resource usage? Are the tabs always loaded or just reference and loaded only when clicked?

Does anyone have recommendation on distributed tracing platform for Java (primarily spring). I'm confused as to what's a standard vs. tracing implementation vs. transport/exporter vs. storage/ui options are. Seems like there's lots of moving pieces to understand.

And it's advantage vs. disadvantage against a profile. Distributed tracing seems more powerful in the face of distributed application (microservice kind though not limited to it) as it can span hosts but limited in the sense that it only trace at coarse level web server > remote service > db kind of way but not providing a view of finer details in a single host (e.g. expensive method calls, computation or lock issues etc.) I wonder if that's a fair characterization or I'm completely off.

FYI your pricing has this 'HIPAA Complicance'.

It seems like a nice idea, the different consent/withdraw/forget workflow. But it seems the core idea is that all user PII is stored in a central table/tables and all other places uses reference. You can do this normally in a regular application, even the old version had only userId (a non PII info without the user table) and the PII was centralized. I think the biggest challenge is getting there where your PII is not spread all over the database and some denormalized PII for performance or whatever reason.

I guess the biggest advantage of this project is removing access to the PII by means of joins and such and automatically enforcing access to PII using a restricted API. I guess a premade API makes it much easier to ensure nobody ends up violating that access and integrate PII too closely with the application.

How to nicely represent all these in the database layer where most things end up living at the end of the day. I have't really found a good recommendation on that to be honest specially the whole LocalDate/Time thing. Anyone has recommendations/documents to help guide that?

I wonder what that means for regular log management use cases and that product.

Yes it was a fully working things before facebook. There has been a lot of improvement in both the core and cli. But the core innovations of zstd was well established before facebook. I was probably following his blogs (even though I wasn't a compression expert) for months before I saw the post about his joining facebook.

wow! Started a semi conductor company at 56. Talk about drive and energy.

I could never find any explanation why when root is exposed and infected you can't treat it with antibiotics and seal the cavity like normal and forced to have a root canal.

What's the sensor being used? Doesn't show any detail on the site. I assume it only tracks glucose and the rest are done at lab?

I guess that's the best option for compatibility. But it's not journaled and single fat, very prone to corruption right and fixing errors could take a while for lager disk like external hdd. There's not really any good option in terms of reliability and compatibility I guess.

I have had issues with ntfs getting corrupted and losing file both in mac and linux at times so there's that risk with implementation too.

I know why they do it. But the fact that a kind of mafia tactic is the best compromise is really sad.

Not an American. One thing I don't understand is how a non essential/time-critical bill like this is allowed to be put alongside critical funding related matter? For that matter how multiple completely independent laws are passed by a same vote?

How do you even reduce it without completely removing plastic from everyday use. Even a long term reusable thing will shade plastic from what it seems like. What happens with other materials that we use like metal, wood, glass, concrete do they shave off particles too or not?

I have had low bandwidth for most of my life and apple update has been a pain for the huge size of even point update. I actually haven't used offline download.

My biggest pain point was that the downloader portion of the updater is so low quality. It corrupts downloads or restarts with tiny network blips, can't resume most of the time and often much slower to download than available bandwidth (that might a bad routing issue on my country). Overall it's often a painful experience.

I'm not in US and even though I read about a lot on police brutality though I don't think all even most are evil. But the problem seems to be almost all police (and govt.) are systematically protecting the bad cop as well as the good cop.

Is this the current production version of the code or the MVP I wonder.

But looks like a simple, focused and very impressive execution born of his own pain points were.

But the memory usage isn't considering growth. If I grow by doubling the size (seems common) at n+1 element where n is the last allocation, one would allocate n2 + n (the original until the copy finishes) vs. n (pointer(s) + element size).

But yes the size advantage is very reduced for most use cases. What would you imagine the cases where LinkedList is still a valid data structure?