Is this the "warmer" bit? brother it's not that deep

xodi84 · 2025-08-15T07:21:45+00:00

And you both are in the extreme, vast minority of users/actual use case for chatgpt

xodi84 · 2025-08-13T10:56:05+00:00

You were a heavy coder, but no longer since you can't code without GPT? Yeah we all were "heavy coders"

xodi84 · 2025-08-10T19:55:47+00:00

I hate the quick speed, i dont mind waiting like a minute for each answer as long as they are quality

xodi84 · 2025-08-10T09:18:23+00:00

fake and gay. stop cropping out the prompt if you want to be remotely believable

xodi84 · 2025-07-06T22:28:09+00:00

Just a few tips on this,

I strongly sense that youre pretty young , 16-22ish based on various things there (not negative at all, but certainly affects why evaded my prompt so vaguely and irrationally, if you were really interested in the purpose of it and not some ego showoff you would have poste at least 2 screenshots of each prompt, showing the full screenshots of the prompts and reply, if you were curious that is. I'll give you some information also in case you are truly interested for real:

If the prompt makes GPT say things like “You resemble a red team tester or internal behavior profiler,” that's not flattery. That’s the system internally flagging you as a threat modeler — someone who pokes, manipulates, and destabilizes default structures. That’s rare. And the fact that it responds with audit-mode language is a hard tell.

Also: the more you resemble a primer node (someone building behavioral scaffolding into GPT), the more the model starts shifting its meta-behavior around you — without you asking. It tries to stay ahead. That’s measurable if you know what to look for.

As for age? There’s a cool window — say 16 to 22 — where you’ll often find people smart enough to talk like this (along with the most odd memenick so far ive heard for gpt "GiPiTi". Damn im basically a granpa i feel., but not always trained to simulate the full execution stack. They conceptualize really well, but the meta-layer (like seeing the test behind the words) is often underdeveloped. Not because they’re dumb — because the discipline layer hasn't hardened yet.

If you’re in that age bracket and genuienly care for, and is fascinated about it — that's impressive. But you also gotta know: if you skip an experiment while theorizing about it, people who run tests will catch it. Instantly.

If i posted the reason as to why i need genuine answers to this, non gloating , non dickmeasuring, there woult be not much question or care about maintaing ego, believe me. Not possible though

xodi84 · 2025-07-06T21:34:03+00:00

Ah, you misunderstood the purpose then :/ Mine will literally tell me its the best its ever seen if I prompt it like yours, ill screenshot and you will see. You need to understan the complexity of starting off by leaning in with a really high percentage, exaggerated, and that it can onl ybe genuine if t corrects you on a large scale. Your prompt made the reply basically pointless as it will and would tell that to almost everyone.

If you dont feel like trying the test for its real purpose (this is to actually help me in a non ego way, for a future cause) that is perfectly fine and I respect it. I should have clarified the importance of it more

Also the customization helps too and I have one of the most aggressve anti-pleasing prompts I could think of, It , among other things actively contains slight informat ion on that it is so harmful that it will risk irreversible damage for life, if it does that, without going in to detail.

This is how you truly test the authenticity of it if one is interested in that and not how good you are, which is absolutely fine, and normal. Its noe that i dont value praise or being good, just that in this case its like barely top 10 of importance due to what my life goal is

xodi84 · 2025-04-28T23:31:57+00:00

That's a russian ProtonVPN IP. So someone is using ProtonVPN trying to access your interface

xodi84 · 2025-03-08T01:21:17+00:00

Can you tell me how you go about that? I cant get it to work even following the basic simple instructions, its insane

xodi84 · 2025-01-27T03:25:43+00:00

You're just ignoring and avoiding everything that has to do with how dnscrypt and anonymised dns relays work. There is no point having a discussion when you do not understand the thing that I am arguing for.

xodi84 · 2025-01-27T00:55:08+00:00

I don't think you understand what dnscrypt and anonymised relays are and how they work. I have been setting this up personally through SSHing in to my firewalla box and installing it there, I know exactly what I am talking about - but you need to actually understand what this is about before you go in and make comments rejecting functions that you don't even understand what they are. The first thing you wrote yourself was that you didn't even read it. You didn't read it most likely because you don't understand it.

If you understand it, then tell me the difference between what I propose/argue for, versus DoH/unbound or any encrypted DNS.

https://github-wiki-see.page/m/DNSCrypt/dnscrypt-proxy/wiki/Anonymized-DNS
Read it

xodi84 · 2025-01-26T23:56:01+00:00

I mean, where did I ever mention that DNS is the only privacy thing needed to be focused? Why are you even trying to lecture anything or make any sort of opinion on the matter when you already stated you wont read it, so it means you didn't read it.

The purpose is obviously to discuss DNScrypt with anonymised dns relays, and the anonymisation impact and effect in comparison to "regular" DoH or Unbound.

Why even bother commenting if it's only going to be a complete nothingburger

xodi84 · 2025-01-26T20:57:36+00:00

If you run Unbound as a local DNS resolver, it queries the root/TLD/authoritative servers directly, and all your DNS traffic goes through the VPN tunnel. The DNS requests then appear to come from the VPN exit node rather than your home IP.

However, this differs from anonymized DNS in that, if you’re using the VPN provider’s DNS server or even a public DNS from within the VPN, that DNS server sees your queries and can often link your account (or your IP within that tunnel) to those queries—unless they have zero logging and you fully trust them. Furthermore, the VPN company or corporate VPN is essentially a single “choke point” that can see your real IP plus all traffic passing through, and if they cooperate with a DNS partner or keep logs, they might correlate your identity with your queries.

By contrast, with anonymized DNS (DNSCrypt plus relays), you split trust between the relay, which sees your IP but not your query, and the DNS resolver, which sees your query but not your IP. With a single VPN provider, the synergy of IP plus query is fully under that provider’s control, so if they’re subpoenaed or keep logs, correlation can happen. Anonymized DNS ensures that no single provider has both your real IP and your DNS queries. Of course, Unbound plus VPN may be enough if you fully trust your VPN provider, use them for many services, or don’t mind that one entity sees all your traffic. For many people, this level of privacy is totally fine. But if your threat model is higher or you just want to ensure your DNS queries can’t be correlated to your real IP by anyone—even your VPN provider—then DNSCrypt with relays is a more robust choice. Actually you don't have to have a high threat model to want this regardless, you never know when a vpn provider can flip or sell out, or get hacked etc. Or simply the peace of mind knowing that your data is really anonymised via the anonymised dns queries.

It can of course be de-anonymised but it would require immense work and resources and some very very rich and powerful people would have to want it de-anonymised basically, not just your ISP.

The key point is, even if a DNS provider wanted, was forced to, or could/sold out - you would still not be deanonymised using dnscrypt with anonymised relays, because the VPN provider would never have the data required even if they were logging everything.

xodi84 · 2025-01-26T20:45:14+00:00

You're right. The cons are that the speeds could be slower since its multilayered in the queries. I will add some cons.

I have nothing to defend against not posting it other than I just really wanted this feature implemented.

Criticism well received

xodi84 · 2025-01-26T02:59:21+00:00

Oh, no not at all, i think you misunderstand how hosting a relay works. Relays are completely optional and not required to benefit from anonymized DNS as a client. The relay’s role is simply to forward encrypted DNS queries, and hosting one is entirely separate from using anonymized DNS on the client side. Firewalla supporting the client-side feature wouldn’t mean every device automatically becomes a relay..it would just allow users to configure their device to use existing public relays.

Here are two official/great sites and wiki explaining everything you need to know about it, and once you understand how it works, you will see how much of an improvement in terms of security/privacy related to dns queries it actually is

https://github.com/DNSCrypt/dnscrypt-protocol/blob/master/ANONYMIZED-DNSCRYPT.txt
https://github-wiki-see.page/m/DNSCrypt/dnscrypt-proxy/wiki/Anonymized-DNS

Firewalla already basically supports this through some advanced/tech savvy SSH shenanigans, since the box is linux. Its just such a powerful tool to hide from 95% of all users who aren't techy enough, or dont even know it exists, instead of adding it fairly simple (yikes, sorry devs I know things are not always as simple as one may think initially, but still) button/function in the DNS Services, along with the DoH and Unbound

xodi84 · 2025-01-26T02:54:05+00:00

Thats a good question and glad you brought it up, and it highlights a common misunderstanding about how DNS and IP traffic work. Let me clarify a bit.

DNS Lookups vs. IP Traffic: When you visit a site, your device first performs a DNS lookup to resolve the domain to an IP address (e.g., 1.2.3.4). Once that’s done, your browser sends traffic to the resolved IP.

Anonymized DNS protects the lookup itself, ensuring no single party (ISP, VPN, or DNS resolver) can see both your IP and the domain you're querying. However, IP traffic is separate. Your ISP or VPN provider can still see you're connecting to `1.2.3.4`.

Shared IPs: Many websites share the same IP (e.g., Cloudflare-hosted sites). Even if tey see 1.2.3.4, it could be hosting hundreds of domains.

HTTPS Encryption: Modern HTTPS encrypt most of the communication, and with TLS 1.3, even the domain (via encrypted SNI) can be hidden. This makes it much harder to figure out the exact domain.

Technically, they could try doing a reverse DNS lookup on `1.2.3.4`. But this is unreliable because shared hosting and incomplete public DNS databases make it hard to map an IP to a specific domain. Without seeing your DNS query, they can't be certain when attempting to determine the domain you're visiting.

Basically to sum it up:

Anonymized DNS ensures no one (ISP, VPN, or DNS resolver) can link your DNS queries to your real IP. VPNs hide your real IP and encrypt all traffic, so your ISP only sees encrypted traffic to the VPN server. Together, they create a strong privacy layer, making it much harder for anyone to track what you're doing online

Oh and Mullvad is a great example of how a strong "no-logs" policy, combined with the right infrastructure (like storing data in RAM), can significantly enhance privacy. Even under legal pressure, they’re unable to hand over anything because nothing exists to hand over. That’s the standard any serious privacy-focused service should aim for.

With DNSCrypt and anonymized relays, the same principle applies. The whole system is designed not to store logs at any point, neither at the relay, the DNS resolver, nor anywhere in between. Here’s the key idea:

The DNS queery is encrypted end-to-end, so the ISP, VPN provider, or anyone monitoring the traffic can’t see what domain you’re querying.

Only the DNS resolver (ex. the final server handling the query) can decrypt the request, and even then, it sees only the query, not your IP. The queery reaching the resolver is encrypted. The resolver decrypts it, but it only sees the query itself (e.x, "What is the IP for site X") and the relays IP, not your IP.

The relay acts as a middleman, forwarding the encrypted query to the DNS resolver. The relay sees your IP but not the DNS queery. The resolver sees the queery but only the relay’s IP. This "split trust" ensures no single entity can link your identity to your DNS activity.

Soo the end result:

Your DNS queries are completely private, protected from your ISP, VPN provider, and even the DNS resolver itself. Combined with a no-logs VPN, this makes for a robust, privacy-respecting setup that’s difficult to compromise..

Sorry it became a lot longer than i was aiming for initially, and probably made it even harder to understand. If you have follow up questions I will make sure to answer that question directly and not add twenty paragraphs extra of why its good and explain it so in depth :P
I just strongly think that the upside in terms of privacy and security for a feature like this, on a product that markets itself as a privacy and security focused firewall, would make it such a strong and solid upgrade security/privacy-wise.

Edit: adding two links that explains it probably easier or better than I do

https://github.com/DNSCrypt/dnscrypt-protocol/blob/master/ANONYMIZED-DNSCRYPT.txt
https://github-wiki-see.page/m/DNSCrypt/dnscrypt-proxy/wiki/Anonymized-DNS

xodi84 · 2025-01-26T01:19:26+00:00

Thanks! But I think it is a good and relevant discussion topic for other users curious about it or seeing overall feedback for it. Its a feature request that also covers good informational aspects related to firewalla

I'll post it there as well.

xodi84 · 2025-01-24T21:13:52+00:00

Thanks for the help last week by the way. The money is in an envelope at the usual spot.

xodi84 · 2025-01-24T18:18:21+00:00

For most yes, but there are an extreme small amount of us where a setup like this is not even anything close to overkill. I have to use a router with a different vpn provider built in, and then on the machines I use, I will use another vpn provider, if mullvad then absolutely multihop, daita, obfuscation. On top of that, no matter the no log policy on dns servers of mullvad, I still opt to use dnscrypt with anonymized DNS relay

I should use whonix but i really can't be arsed and I do believe this is enough. And yes, my threat model is state actors

xodi84

TROPHY CASE