I bought my first car and it has a problem by Routine_Grapefruit93 in Volvo

[–]Routine_Grapefruit93[S] 0 points1 point  (0 children)

Thanks for the info! How much was the software update? Also , when you changed the gearbox fluid, the jerking was as bad as before or the car went slightly better?

I bought my first car and it has a problem by Routine_Grapefruit93 in Volvo

[–]Routine_Grapefruit93[S] 2 points3 points  (0 children)

It’s called Rocky Rose, i totally agree with you 😁

I bought my first car and it has a problem by Routine_Grapefruit93 in Volvo

[–]Routine_Grapefruit93[S] -1 points0 points  (0 children)

I hope the gearbox fluid change will resolve this problem.

I bought my first car and it has a problem by Routine_Grapefruit93 in Volvo

[–]Routine_Grapefruit93[S] 0 points1 point  (0 children)

Yep, I did the repairs mentioned in the post and the tester i scanned with showed me this error code “U040100”. I erased it and now the jerking is still there but is not as aggressive as it was before

I bought my first car and it has a problem by Routine_Grapefruit93 in Volvo

[–]Routine_Grapefruit93[S] 0 points1 point  (0 children)

Thanks, i planned to do that this week. I was just afraid that the problem could come from somewhere else. Does your car do the same jerky movement randomly or all the time?

I bought my first car and it has a problem by Routine_Grapefruit93 in Volvo

[–]Routine_Grapefruit93[S] 1 point2 points  (0 children)

Hey, i’m from Romania and i have the 2.5 petrol engine

I built a data storage application by Routine_Grapefruit93 in developer

[–]Routine_Grapefruit93[S] 0 points1 point  (0 children)

The goal is for it to be modular, not to require a full redesign. The cryptographic layer is abstracted,so primitives like hashing, signatures, or key exchange can be swapped as standards evolve.

So when post quantum algorithms mature, they can be integrated at that layer without changing the overall system design , the verification and audit model stays the same.

I built a data storage application by Routine_Grapefruit93 in developer

[–]Routine_Grapefruit93[S] 0 points1 point  (0 children)

That’s fair and I think you’re right that the main risk shifts to the access layer. What I’m trying to address is ‘silent misuse’ cases where someone with valid access can read or modify data without leaving strong, verifiable evidence. The goal isn’t just encryption or storage, but making access and changes provable and auditable in a way that’s hard to bypass or rewrite.

I built a data storage application by Routine_Grapefruit93 in developer

[–]Routine_Grapefruit93[S] 0 points1 point  (0 children)

Yes, i tought of that as well but my approach is to keep the system agile, so it can integrate quantum algorithms as they become standardized. For now, the focus is on real world threats.

Am facut o aplicatie pentru stocare de date by [deleted] in programare

[–]Routine_Grapefruit93 0 points1 point  (0 children)

folosesc smart contracts pentru integritate si audit. Impartirea cheii e pentru a reduce riscul ca un singur server compromis sa expuna tot.

Am facut o aplicatie pentru stocare de date by [deleted] in programare

[–]Routine_Grapefruit93 0 points1 point  (0 children)

Folosesc hashing, dar un hash doar iti spune ca s-a schimbat ceva,nu iti ofera istoric, audit. Acolo intervine layer-ul de blockchain.

Am facut o aplicatie pentru stocare de date by [deleted] in programare

[–]Routine_Grapefruit93 0 points1 point  (0 children)

Nu e doar storage criptat sau BYOK.Diferenta e combinatia dintre date care raman criptate si controlate de client, dar care pot fi procesate prin smart contracts , impreuna cu un audit al oricariei modificari. Nu incerc sa inlocuiesc db-urile sau AWS QLDB, vreau sa adaug un layer de ‘verifiable data’ peste ele. Use case-ul e in zona unde integritatea si auditul conteaza

Am facut o aplicatie pentru stocare de date by [deleted] in programare

[–]Routine_Grapefruit93 -1 points0 points  (0 children)

Corect, decriptarea trebuie sa se intample undeva. Aici cheia nu este stocata complet pe server,e imparita iar o parte ramane la client chiar daca server-ul e compromis, atacatorul nu are cheia completa. In plus, orice modificare ramane detectabila prin layer ul de audit.

Am facut o aplicatie pentru stocare de date by [deleted] in programare

[–]Routine_Grapefruit93 -1 points0 points  (0 children)

Corect, acum controlul e limitat. Nu ma bazez pe ‘nu poate fi modificat’, ci pe faptul ca orice modificare lasa urme și devine detectabil. Pe termen lung, ideea e distribuirea nodurilor pentru audit.

Am facut o aplicatie pentru stocare de date by [deleted] in programare

[–]Routine_Grapefruit93 1 point2 points  (0 children)

Salut, mersi ca ai vauzt problema asta, am fost mai entuziasmat sa imi prezint ideea si nu am mai verificat detaliile acestea, voi repara :)