▲ 92 r/Habits

What are some habits that genuinely improved your life?

I’ve been thinking lately about building better habits and becoming more disciplined, but I’m curious about what actually works for other people rather than just following the usual advice you see everywhere.

What are some habits you personally started doing that made a noticeable difference in your life? It could be something related to productivity, studying, health, fitness, sleep, money, social life, or even something really simple.

I’m especially interested in habits that you’ve been able to stick with for a long time and that genuinely made you feel better or improved your life in some way.

Also, are there any habits you started that you thought would help but ended up being a waste of time?

I’d love to hear what has actually worked for you and what you would recommend to someone trying to build a better daily routine.

reddit.com
u/Only-Dependent7024 — 3 days ago

Would you be fine with being made into an AI partner/companion?

I keep seeing more creators get turned into AI companions, where a platform licenses your likeness and personality and people pay to chat and not just chat) with the AI version of you. OhChat is signing new creators in every week, I saw someone called Kai Luessenhop signed this week and he's not even that big of a creator so it shouldn't be that hard to get signed, and now I can't stop thinking about whether I'd do it with my own brand or not.

The chatting and sexting is the part of this job that burns me out fastest, and an AI version handling that around the clock while I sleep sounds more available AND cheaper than hiring an agent to talk to people (or up to 3 if you want yourself to be available 24h/day), Id also retain parts of the earnings just for having myself be the baseline inspo of the AI character. It will potentially scale in a way I never can on my own.

But there are real downsides to it too, I know people can and do take things really far with the AI stuff. ANd I know it's things you'd never know about + that isn't really you, so it shouldn't matter, and yet it still feels a bit strange to picture (especially if there are audio/image features they can use and generate). There's also the control side, since once your likeness is a model out in the world, I'm not sure how much say you keep over what it says or does with your face on it.

reddit.com
u/Only-Dependent7024 — 11 days ago

Most popular 5 EU enterprise password managers for 2026, pros and cons of each (no particular order)

I went down a rabbit hole trying to find a password manager for my team that keeps data in European hands, and "European" turns out to be a slippery word. So I got specific about where each company is incorporated and where your data physically sits. These aren't ranked, just the five worth knowing, laid out the same way so you can compare like for like.

Psono (Germany)

Pros: German company, open source, self-hostable, so everything can stay on your own infrastructure inside the EU. Solid role-based access and audit logging on the enterprise tier. The clearest EU-incorporation story on this list, too.

Cons: setting it up is a pain,and it's not just me this is a common complaint I saw on review platforms too. The interface feels dated next to the consumer options especially the mobile app. Enterprise features need you to get the paid edition, so the free version won't cover AD sync and audit logs alone. Smaller company, thinner ecosystem.

Recent controversy: none on record, no breach or incident.

Proton Pass (Switzerland)

Pros: built by the Proton Mail team, open source, end-to-end encrypted, a useful free tier, built-in email aliases. Swiss privacy law is strict, often tougher than GDPR.

Cons: autofill is inconsistent, it misses a real share of login forms and is worse on mobile, which is the most common gripe from people who moved over (from Bitwarden especially). Support is thin on personal plans, no live chat, just a contact form with no ticket status. And Switzerland is not in the EU, so if you need strict EU jurisdiction for procurement or residency, Swiss hosting may not qualify.

Recent controversy: no product breach. Proton's CEO Andy Yen sparked political controversy in January 2025 by praising a Trump administration appointee, leading to user debate over the company's stated political neutrality. (context)

Bitwarden (US)

Pros: the open-source default, for good reason at that. Excellent free tier, cheapest paid plans, self-hostable, strong SSO and SCIM, and it documents EEA (Frankfurt) storage so vault data can stay in Europe. Mature and heavily audited.

Cons: the company is US-incorporated, so even with Frankfurt hosting the vendor sits under US law and CLOUD Act reach, which is what some people here are trying to avoid. Hosting location doesn't change corporate jurisdiction, and self-hosting is real operational work nohow, not an afterthought or "just one more thing".

Recent controversy: in April 2026 a malicious version of the Bitwarden CLI was published to npm and was live for about 90 minutes, stealing cloud and CI credentials from build pipelines. End-user vaults were not affected, and it was a compromised third-party build action rather than a flaw in Bitwarden's own code, but worth knowing if you wire the CLI into CI/CD. (context)

Passwork (Spain)

Pros: Spanish company, does both self-hosted and EU-hosted cloud in German data centres. On-prem zero-knowledge architecture, LDAP/AD sync, per-user audit logs, ISO 27001, a 2025 HackerOne pentest. Strong enterprise fit on features and EU hosting.

Cons: no native desktop app, browser extension and mobile only. The code is also not open-source, though they say on their website that they are willing to provide it upon customer request.

Recent controversy: in July 2026 a five-outlet investigation (OCCRP, Le Monde, and others) reported Passwork originated in Russia in 2014 and shares a codebase with the Russian sister product, which ends August 30th 2026 alongside model updates too (so exactly 4 weeks from today) and after that, to each their code/updates/etc. Passwork, however, says the Spanish company is independent, shares no data with the Russian side, and that its on-prem zero-knowledge design means even the vendor can't reach your vault. My take: the on-prem zero-knowledge setup is a real mitigation if you self-host and review the code, but if your bar is no Russian origin at all, then you make the call. Read both sides before deciding. (investigation/Passwork's response)

NordPass (Lithuania)

Pros: parent company Nord Security is headquartered in Lithuania, so the parent sits inside the EU. Polished, beginner-friendly apps, modern XChaCha20 encryption, easy to use for non-technical teams.

Cons: closed source, so you can't independently audit the code the way you can with the open options. Audits are announced but only summaries get published, not full reports, which is weaker transparency. It doesn't let you pin a vault region, so verify current data-processing locations if residency is the point.

Recent controversy: NordPass itself has never been breached. The wider Nord group had a NordVPN server breach disclosed in 2019 (unrelated to NordPass, an expired key on a rented server) that still comes up around their disclosure habits. (context)

So which password manager should your enterprise/company use?

→ For strict EU incorporation plus open source, Psono.
→ For polish and Swiss-grade privacy where non-EU jurisdiction is fine, Proton Pass.
→ For the mature open-source default where a US parent is tolerable, Bitwarden.
→ For a password manager made for businesses and with businesses in mind, Passwork (it still carries the unresolved Russian question, so it needs the most diligence).
→ For an EU parent with easy rollout, NordPass.

And good luck!

u/Only-Dependent7024 — 16 days ago

Handling access provision and onboarding/offboarding for a call center for 40%+ employee turnover has become most of what I do every day

Im venting I have nothing to ask nor add here, Im merely venting.

Call center IT work is a nightmare. Someone starts today while another's gone tomorrow, and both are mine across every system they touch. A new agent needs the dialer, the CRM, the ticketing system, the knowledge base, the workforce tool, and a stack of shared logins before they can take a single call. Miss one and they sit there paid and idle while their trainer waits on me. Then a week later three of them quit and I'm doing the whole thing in reverse. Across the time they're here, THEY ALL KEEP MAKING SIMILAR MISTAKES and paging me for questions I've answered a billion times before.

The offboarding is almost the same, had it not been for Passwork's automated API letting me instantly rotate the exposed shared keys and my heavily abused PowerShell scripts handling Azure AD, I would've probably went insane (which Im not far from nohow). I also have to remove company emails, revoke building badge access, reclaim the hardware for the ones that did remote, pull them from the workforce management and scheduling system, etc. Every. Single. Person.

The churn never stops. Atp my job is basically reduced to letting people in and out of a building all day long. Some days the whole job is just that, which is...humbling to say the least

reddit.com
u/Only-Dependent7024 — 20 days ago

What a shame : aadit recharge telephonique aal D17 , 5DT ooreddo w ma woslouch

Although i got the sms indicating the transfer but nothing added in balance. Where does this issue originating from D17 wle ooredoo.

Who should i call if there is customer service handle these situations. Any advice is appreciated

reddit.com
u/Only-Dependent7024 — 1 month ago
▲ 37 r/devops

Our CI/CD secrets are scattered across GitHub, Jenkins, .env files (and a few more). How can I get to runtime injection (relatively) peacefully?

We spent the last year shipping as fast as we could and the bill came due on secrets management. Right now they're everywhere: hardcoded in a few GitHub repos, sitting in .env files, baked into Jenkins credentials, and on at least three devs' laptops that I know of. It works until it doesn't, and I'd rather fix it before it becomes an incident instead of after.

The goal is runtime injection so nothing sensitive lives in the repo or the CI config at all, but I don't have six months to stand up a whole platform. I'm trying to find the pragmatic middle path between "keep living like this" and "boil the ocean".

A few things I'm weighing: IT already runs Passwork for human credentials and it has an API and CLI, so one option is just consolidating machine secrets there too rather than introducing yet another system. The other direction is a dedicated secrets store built for the pipeline. Underneath all of this is the identity question of do I go OIDC federation so the runner authenticates without a long-lived token, or accept a bootstrap secret somewhere and just minimize the blast radius?

reddit.com
u/Only-Dependent7024 — 1 month ago

Welche Tools skalieren eigentlich noch gut für 'n wachsendes Startup? Unser aktuelles Setup bricht grad voll zusammen.

Wir sind in 'nem guten Jahr von 8 auf 42 Leute gewachsen, wir machen SaaS und anderen Tech-Kram, und die Nachfrage steigt einfach schneller als ich hinterherkommen kann. Einstellen ist natürlich das Erste was man tun muss und ich bin da eh schon dran, aber was mich eiskalt erwischt ist wie viel von unserem internen Setup klammheimlich den Geist aufgibt je mehr wir wachsen. Sachen die bei 10 Leuten noch völlig okay waren werden bei 42 zu 'nem echten Krampf.

Einiges von dem was bei uns grad schon bricht:

-Shared Drives: Ordnerberechtigungen die geklappt haben als noch jeder jeden kannte fangen an zu viel zu teilen oder blockieren Leute. Wir integrieren grad schon Google Workspace aber ich würde mcih über Feedback zu seinem Skalierungspotenzial freuen

-Onboarding: jeder Neuzugang muss Konten manuell in voll vielen Apps einrichten, ich dachte da an Rippling für.

-Tool-Wildwuchs und überlappende Abos: jedes Team sucht sich seine eigene App aus, von denen sich voll viele überschneiden und keine redet mit der anderen. Würd Zapier helfen das einzudämmen?

-Passwort-Manager: im Moment liegen unsere Passwörter in Google Docs (so ein Doc pro Abteilung) und werden manchmal über Slack verschickt (ich weiß, ich weiß). Es fühlt sich weder sicher noch audit-freundlich an also dachte ich drüber nach Passwork dafür zu integrieren.

Wir sind fast 50 Leute was der Punkt ist wo Audits wje NIS2 reinkicken also versuch ich echttt das ASAP dichtzumachen. Will mal sehen was ihr so nutzt und was eure Reviews/Meinungen zu alelm sind was ich geschrieben hab, danke.

reddit.com
u/Only-Dependent7024 — 1 month ago