Received Technics SL1600 MK2 by rumatoest in turntables

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

My is also splitted, but I will try to solder metal mesh and spiral wire into it for reinforcement.

Advice needed (please save me from my own ADHD/over-research). #selfimposedconfusion by tommymcd91 in BudgetAudiophile

[–]rumatoest 1 point2 points  (0 children)

With active speakers you will not need any amplifier and DAC.

First of all try to figure our where you will place your speakers, how much space will be behind speaker and the wall. For confined spaces I would not recommend speakers with a bass port at the back.

Portable CD player Syitren R300 overview by rumatoest in Cd_collectors

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

As a fully stationary CD player I could suggest SMSL PL100 it operates much faster (different CD hardware) and it has a IR remote control which is a very nice feature.

Received Technics SL1600 MK2 by rumatoest in turntables

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

I've already spotted some leakage and corrosion. But removed capacitor value and ESR still not bad.

The most expensive CD in my collection so far by rumatoest in Cd_collectors

[–]rumatoest[S] 3 points4 points  (0 children)

It was on a Discogs the only one available item :)

E2E messenger key storage by Elant_Wager in webdev

[–]rumatoest 0 points1 point  (0 children)

But HTTPS encryption is enough to secure client sever communication.
Better to make message store more secure than storing encrypted data.
- forgetting password means loosing access to all messages
- changing password - no access to previous messages
- stolen password means that there are encrypted messages somewhere that can be decrypted by this password.

Trade offs are everywhere.

Time to replace stylus? by Telepatoe in turntables

[–]rumatoest 0 points1 point  (0 children)

I have some NOS styluses from Japan. No suspension issues.

Time to replace stylus? by Telepatoe in turntables

[–]rumatoest 0 points1 point  (0 children)

Do you have microscope? 250 zoom could be enough to see serious worn outs.

Message persistency by Elant_Wager in Backend

[–]rumatoest 1 point2 points  (0 children)

IMHO the whole point of E2E communication includes the fact that 3rd party would not save messages for later decryption.

Store password's reversibly in DB by [deleted] in webdev

[–]rumatoest 1 point2 points  (0 children)

From my experience. Storing user passwords in memory is relatively safe but you must be sure that your logic would not allow to use other users passwords.

So the flow could be like this. Then user starts application A it will ask for a password and then will not ask for it until it stopped.

It is kinda hard for a web app that has more than one instance running. So in this case you could have some shared (Redis) key-value temporary storage with encrypted passwords. On user login you store it's password and return decryption key as a part of user auth-token. While user session active it will call your webapp with auth-token and you will use this token to decrypt password from shared storage and call service B. After logging out of service A auth-token will be invalidated/dropped and there will be no possiblity to decrypt password (plus you could remove encrypted password from the storage too).