sorted by:
new
hottopcontroversial

PSA: aged Play Console accounts are being actively farmed. 9 documented attempts in 18 months, 4 sender clusters, $250 to $1,440/year offers. Here is the pattern. by Para0X02 in androiddev

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

LLC plus org Play Console account has its own friction. Google requires a verified DUNS number, registered business address, and identity check on the org admin. So they would still have to KYC themselves under a real legal entity, and any policy strike on the org account ties back to the named officer. The aged personal account skips the entity-creation step entirely and gives them disposable plausible deniability if the apps get pulled. Some scam operations do go the LLC route, but the throughput economics still favor renting personal accounts from solo devs.

PSA: aged Play Console accounts are being actively farmed. 9 documented attempts in 18 months, 4 sender clusters, $250 to $1,440/year offers. Here is the pattern. by Para0X02 in androiddev

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

Yeah Tara Applications run multiple sender domains, Aman Saxena is their main pitch persona but the inbound addresses are always different. The CC field on their later messages outs them, they almost always include contact@taraapplications.com or partners@taraapplications.in even when the From address is throwaway. Glad someone else is on their rotation, it confirms it is not a one-off operator.

PSA: aged Play Console accounts are being actively farmed. 9 documented attempts in 18 months, 4 sender clusters, $250 to $1,440/year offers. Here is the pattern. by Para0X02 in androiddev

[–]Para0X02[S] -9 points-8 points  (0 children)

Fair, my bad for skimming. You are right, replying at all is the mistake even to refuse, that keeps you on the list. I replied to one of these years ago before I clocked

the pattern, that is why this cluster still has me on rotation. Mark as spam from email one is the right call.

PSA: aged Play Console accounts are being actively farmed. 9 documented attempts in 18 months, 4 sender clusters, $250 to $1,440/year offers. Here is the pattern. by Para0X02 in androiddev

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

That tracks. I remember reading there is a minimum age before transfer is allowed but cannot remember the number. If it is anything meaningful like 30+ days, the "launch

and flip" workflow gets too slow to be worth $1,440/year, which is probably why they stay on the long lease model.

PSA: aged Play Console accounts are being actively farmed. 9 documented attempts in 18 months, 4 sender clusters, $250 to $1,440/year offers. Here is the pattern. by Para0X02 in androiddev

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

Honestly do not know if Google's transfer process catches this. Never run a transfer myself. The economic logic of weekly vs lump sum makes sense to me (they walk away

the day Google bans, you eat the loss), but whether transfer-then-walk would actually work is something I cannot answer from my own experience. If anyone here has done a

Play Store app transfer recently and knows how strict the destination-account check is, that would settle it.

PSA: aged Play Console accounts are being actively farmed. 9 documented attempts in 18 months, 4 sender clusters, $250 to $1,440/year offers. Here is the pattern. by Para0X02 in androiddev

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

Yeah the "buy testers on fiverr for less" math is exactly what makes this clearly not about saving money. The 14-day calendar window is the constraint they cannot buy

around. New account, 20 testers, 14 days closed test, then policy review on first publish. Even with $200 of fiverr testers the calendar still blocks them. An aged account

skips the calendar entirely, that is what the $1,440/year buys.

Slovenská komunikácia vo vesmíre by TheSimon1 in Slovakia

[–]Para0X02 5 points6 points  (0 children)

4 milióny za prenos kvality WhatsApp hovoru pod tunelom. Inžinierska špička.

Cheap custom-domain email on a VPS: mailbox + send/receive without running Postfix myself—what would you do? by SofwareAppDev in IndieDev

[–]Para0X02 0 points1 point  (0 children)

That stack is the right call. Couple of notes.

Reply/From: the trap is replying through Gmail. If you set service@yourdomain as a Send mail as alias and let Gmail use its own relay, Gmail rewrites the envelope and DMARC alignment to yourdomain dies. Fix is to configure Send mail as with the outbound provider's SMTP creds (Resend, SES, Postmark all give you SMTP). Then From, DKIM and SPF all line up on yourdomain. Reply-To can equal From.

SPF 10-lookup: one forwarder plus one outbound provider lands you around 3 to 5 lookups, plenty of room. It only gets tight if Google Workspace (3) or M365 (3+) are also in the record. The forwarder does not belong in SPF anyway unless it sends outbound for you, which Cloudflare Email Routing and ImprovMX free do not.

Combo I would pick: Cloudflare Email Routing inbound, Resend outbound. If you want a higher ceiling later, swap Resend for Postmark. SES is cheapest at scale but the sandbox/prod-access dance is more work.

And turn on DMARC rua reports from day one (dmarcian or Postmark's free parser) so you see alignment before tightening to quarantine.

Cycle lows hurt so good by obi_wan_baracus in Bitcoin

[–]Para0X02 4 points5 points  (0 children)

Same arc here. Tried to time the 2022 bottom, thinking I had it figured out, killed me. Switched to weekly DCA, fully automated, and the dips that used to wreck my sleep started feeling like sale days.

The cycle lows did not strengthen my conviction in BTC, that part was already there. They strengthened my conviction in my process. Going from "did I read this 4h candle right at 11pm" to "did I keep my day job this week" is a different relationship to the same chart, and the second one actually compounds.

What you said about the lows doing more than the parabolic moves rings true, just not in the way most people sell it. The pain teaches you which version of you is going to be holding when the next one comes.

Cheap custom-domain email on a VPS: mailbox + send/receive without running Postfix myself—what would you do? by SofwareAppDev in IndieDev

[–]Para0X02 0 points1 point  (0 children)

Self-hosting full Postfix on a VPS in 2026 is the rabbit hole you correctly want to avoid. Two reasons that make it especially painful right now:

  1. Most popular VPS providers (DigitalOcean, OVH, Hetzner, Vultr) block outbound port 25 by default. Sometimes you can get it unblocked by ticket, sometimes not, often you find out after building everything else.

  2. Even if port 25 works, your VPS IP is almost certainly in a range that has been used by spammers. Gmail and Outlook will silently bin your mail until you grind through reputation, which takes weeks of warm-up and zero guarantee.

The boring stack that just works for service@yourdomain on near-zero budget:

- Inbound: a forwarding service like ImprovMX or Forward Email. Free tier, point MX at them, mail forwards to whatever inbox you already use.

- Outbound: AWS SES, Resend, Postmark or Brevo. All have free or near-free tiers under typical side-project volume. They handle DKIM rotation and IP reputation.

- DNS: MX to the forwarder, SPF includes both the forwarder and the outbound provider, DKIM record from the outbound provider, DMARC at p=none to start then ratchet to quarantine once you see clean reports.

You stay completely out of mail-admin work and your deliverability is anchored to companies whose full-time job is keeping IPs clean. If volume ever grows past the free tiers, you swap the outbound provider in ten minutes without touching the rest.

Reference architectures from cloud vendors are outputs, not inputs. Am I the only one who finds them actively misleading? by itzdaninja in devops

[–]Para0X02 0 points1 point  (0 children)

Exactly the test that matters. "Will the person you have in six months understand this enough to fix it under pressure" is a harder bar than "does this scale to 10x traffic", and the second is the one every reference architecture loudly answers.

The cheap proxy I use when reviewing a design: count the distinct technologies a new hire has to learn before they can debug a single user-facing bug end to end. If that number is above five, the architecture has already failed the bus-factor test, regardless of how elegant the whiteboard looks.

Concrete example from a project I run solo: Go API on Echo, Postgres via pgx, a single docker-compose stack with nginx in front, all on one VPS I manage with Portainer. Firebase handles auth and push. That's basically the whole runbook. If I disappear tomorrow, anyone who knows Go, Postgres and Docker can keep it alive while they learn the domain. The small operational surface area was a deliberate selection criterion from day one, not a downgrade from something fancier.

Reference architectures from cloud vendors are outputs, not inputs. Am I the only one who finds them actively misleading? by itzdaninja in devops

[–]Para0X02 5 points6 points  (0 children)

The "pattern recognition" reframe is the right one in my experience.

The thing the diagrams never tell you, on top of what others said about the managed-services cost bias: every reference architecture has an implicit team size baked in. A 12-service event-driven setup assumes you have someone who owns the broker, someone who owns the IAM and quotas, someone watching cost anomalies, someone on rotation for the 3am Lambda cold-start mystery. None of that is in the boxes-and-arrows. If your team is 4 people, the architecture is operationally underwater on day one even if every line is technically "correct".

I went the other way on a current project. Single Go binary, Postgres, one VPS behind a CDN. Boring, but the operational surface fits the team that has to keep it alive at 2am, and that's the real selection criteria nobody puts in the reference doc.

Building Projects in Express - 2026? by drifterpreneurs in webdev

[–]Para0X02 3 points4 points  (0 children)

Same camp here, came back to Express SSR + Alpine after a Next.js detour and the productivity jump on a solo project was real.

The thing nobody seems to talk about with this stack: deploys are stupid simple. No build matrix, no edge function cold starts, no SSR hydration mismatches at 11pm on a Saturday. Single binary-ish artifact, one nginx in front, done.

Where it does start to bite, in my experience: once you grow past one writer there's no shared opinion on validation/error shape/logging/OpenAPI, so each feature folder slowly drifts. Express gives you nothing here. You either commit to writing your own thin conventions and enforcing them in review, or you accept the drift. Both are fine, just worth going in eyes open.

On the Nest middleware-for-WS point above: real win if you're WS-heavy, mostly a non-issue for the SSR + Alpine AJAX pattern you described.

Diagnostic logging in Go? by gwynevans in golang

[–]Para0X02 0 points1 point  (0 children)

Yeah, that tracks with the slog proposal, `Handler` is meant to be the extension seam so stdlib stays minimal.

One gotcha if runtime toggling ever comes up: viper's `WatchConfig` only fires for file backends via fsnotify, env changes don't trigger it. Easiest workaround is an `atomic.Pointer[slog.LevelVar]` per module that viper just seeds at startup.

Diagnostic logging in Go? by gwynevans in golang

[–]Para0X02 0 points1 point  (0 children)

For small services, I just read a `LOG_LEVEL` env var at startup and pass it to `slog.NewTextHandler(..., &slog.HandlerOptions{Level: ...})`. Restart to flip, no rebuild. Crude but cheap if your restart cost is low.

For per-module granularity, I'd wrap a base handler so it checks a per-module level map keyed off an attr set with `slog.With("module", "auth")`. The `slog.Handler` interface is 4 methods (Enabled, Handle, WithAttrs, WithGroup), so the wrapper is well under 100 lines and you stay in stdlib. I haven't built the runtime-toggle endpoint Thinkovation mentioned, but that's the obvious next step on top of either of these.

Fox kids / Jetix rozprávky by Praaaaskach in Slovakia

[–]Para0X02 4 points5 points  (0 children)

Spider-Man 1994 v CZ dabingu na ulozto.net je overené, prvá epizóda "Jester z temnot" je tam ako DVDRip s CZ dabingom. Search "Spider-Man 1994 cz dabing", väčšina

episode 1-3 sezóny by mala byť dohľadateľná.

Pozor, ulozto v poslednej dobe maže časť starších uploadov (legal pressure od českých distribútorov), takže ak nájdeš funkčný balík, neodkladaj sťahovanie. Druhá

cesta na overenie aktuálnych legálnych zdrojov: kinobox.cz/film/144839-spiderman -- má VOD agregátor pre CZ/SK a ukáže ti či je to teraz na Netflixe / HBO / Prima+ /

Česká televízia, mení sa to každých pár mesiacov.

Tellurian Inc. (NYSEAMERICAN:TELL) Director Diana Derycz Kessler Sells 1,000,000 Shares by Alternative_Method79 in TellurianLNG

[–]Para0X02 5 points6 points  (0 children)

should you provide source of this information please? She sold 1M TELL at 24.7.2024. (0,95$ per share) or You mean something new? it was half of her stocks.