• 0 Posts
  • 15 Comments
Joined 2 months ago
cake
Cake day: February 14th, 2025

help-circle

  • Doesn’t the message you received basically say the graphene devs don’t want it discussed in /r/privacy ?

    If I were involved in a project with any sort of following I wouldn’t want it discussed in a large, general, subreddit either. If it is, you either need to engage with people there to minimise any misinformation, or you just have to let people spread nonsense about your product.

    That said, asking why /r/privacy exists when the devs of privacy-related projects don’t want to participate is a good question. The answer is, the mods are fief lords who would rather preside over a sham than nothing at all.

    Honestly, I can’t think of any good reason to be a moderator of /r/privacy on reddit




  • It depends what purpose that paperwork is intended for.

    If the regulatory paperwork it’s managing is designed to influence behaviour, perhaps having an LLM do the work will make it less effective in that regard.

    Learning and understanding is hard work. An LLM can’t do that for you.

    Sure it can summarise instructions for you to show you what’s more pertinent in a given instance, but is that the same as someone who knows what to do because they’ve been wading around in the logs and regs for the last decade?

    It seems like, whether you’re using an LLM to write a business report, or a legal submission, or a SOP for running a nuclear reactor, it can be a great tool but requires high level knowledge on the part of the user to review the output.

    As always, there’s a risk that a user just won’t identify a problem in the information produced.

    I don’t think this means LLMs should not be used in high risk roles, it just demonstrates the importance of robust policies surrounding their use.







  • This is what I do. Changing the port to a higher number will prevent almost all bots.

    I understand that obscurity is not security but not getting probed is nice.

    Also ssh keys are a must.

    I do log in as root though.

    However, I block all IPs other than mine from connecting to this port in my host’s firewall. I only need to log in from home, or my office, and in a crisis I can just log in to OVH and add whitelist my IP.



  • Nah we just need a fancy team name for the not-absolute-fuck-head countries.

    I mean EU is Europe and I fucking love you guys but down here in Australia we can’t just up and move the continent to Europe.

    I don’t think the name should be dependent on membership like BRICS or whatever because you don’t want to have to rebrand when you kick someone out or let someone in.

    I think it should include a word like collaborative because honestly, that’s what it’s about - we’re better off working together.

    It’s also important to choose a name with a catchy acronym that isn’t already taken.

    Maybe Collaborative Union of Nice Terran States.


  • I feel like most commenters here haven’t understood what you’re proposing.

    I’ve thought about doing this, I’ve seen other commenters say they’re doing it. It’s not a terrible idea. I haven’t done it myself because … it’s just not a priority and I’m not sure it ever will be. Anyway …

    If you’re willing to set up and self host your own email stack like mail-in-a-box or whatever, then configuring a separate outbound SMTP server is fairly trivial in comparisson.

    If you already had your own stack set up to be self hosted you would ordinarily be using the SMTP server there-with to send emails.

    Firstly configure your client to use whatever other SMTP server you have access to. I think it’s possible to use mailgun or one of those API transactional senders. You could get a cheap plan with mxroute or any other email host and just use the SMTP server.

    Suppose your client is Thunderbird and you set up your account like smtp.mxroute.com for outbound and imap.myserver.com for email storage. When you send an email tbird transmits it through mxroute and then stores it on your imap server at myserver.com in your sent folder.

    The potentially complex part is configuring spf & DKIM records on your domain.

    SPF

    I’m not sure if I’ll be able to explain this clearly but… suppose a recipient’s spam service receives an email purportedly from marauding_giberish@myserver.com but transmitted by smtp.mxroute.com. That spam service will look up the DNS records for myserver.com and inspect the records for the spf record. This record pretty much lists which servers are authorised to transmit email from addresses ending in myserver.com. So with a more typical set up an spf record might be:

    “v=spf1 include:myserver.com -all”

    This would indicate that only the smtp server at myserver.com can transmit email from your domain.

    You would edit that to include the mxroute smtp server like this:

    “v=spf1 include:mxroute.com include:myserver.com -all”

    This way, recipients can confirm that the owner of myserver.com domain has formally designated mxroute as an authorised recipient.

    DKIM

    Your SMTP server will have a public & private key pair which it uses to sign outbound messages. Recipients can use the public key to confirm the signature and thereby confirm that the message has not been altered in flight.

    Whatever SMTP server you use will tell you the public key and instruct you to add that to the DNS records of your custom domain.

    That’s the one that looks like this:

    “v=DKIM1; k=rsa; p=MIIBIj [ … it’s a long key … ] op3Nbzgv35kzrPQme+uhtVcJP”

    Once this is in place recipients of your emails can query the DNS for myserver.com and find this public key, and use it to confirm that the signature on the email they received is authentic.