• 1 Post
  • 285 Comments
Joined 5 years ago
cake
Cake day: January 21st, 2021

help-circle
  • They are legal if you follow the regulations. The problem with the “rideshare” companies is that they don’t. We should just call them “unregulated taxis” rather than pretending that they are a different service. I think just about every taxi company these days is on some app or another (often the same that call unregulated cabs in countries that actually got their shit together and banned the unregulated ones).










  • kevincox@lemmy.mltocats@lemmy.worldTalking to your cat
    link
    fedilink
    arrow-up
    4
    arrow-down
    8
    ·
    5 months ago

    No, this is the right meaning royal we. If you say “we are going into battle” it is talking about the person being talked to not the person talking. So in this case “We don’t eat that” would be implying that the cat doesn’t eat that, not actually saying anything about the speaker even though “we” would imply they are included.


  • Reverse DNS is different than static IP.

    But yes for outbound email, if you can’t control reverse DNS you will have pain. (Inbound is totally fine) You can in theory just use whatever hostname the ISP’s reverse DNS resolves to however you will get some spam score (or be rejected) as it doesn’t match your “from” domain.

    Outbound email is a huge pain really no matter what. Unless you have a long-term lease on the IP and it isn’t in a bad network you really have to pay someone else if you want reliable delivery.


  • Its a problem but it isn’t a major problem. I am using rspamd without any sort of exotic configuration (basically just enabling things that are provided, not my own rules) and I only get a few spam messages leaking through a week. Maybe slightly worse than GMail but not considerably slow.

    IMHO the only real missing thing out of the box is contacts checking. Which is a huge thing because it is great to have reliable delivery from contacts. But my false-positive ratio is so low anyways that it isn’t a big issue and things like the known_senders module mostly mitigates it.


  • Yes, blocking port 25 outbound is incredibly common by default. Even on some server connections. It is probably better overall for exactly the reasons that you mentioned.

    Or just don’t self-host email

    IMHO this is a bit overblown. Hosting inbound is fairly easy. Mail senders (probably for the worst) are very forgiving even if your TLS cert is expired you will probably get mail. Plus senders are supposed to retry for days if you have downtime.

    However it is unfortunately true that due to spam sending is a huge pain because IPv4 reputation is a huge component. Sure you can get GMail to trust your domain after a month or so of sending if you have decent volume. But other providers who you may mail once a year are just going to go off of IP reputation. However email was basically designed for forwarding and you can use a service like AWS SES to forward your email from a trusted IP pretty easily. If you are low volume (like personal mail) there are tons of services that will do this for free.








  • I think this is a little confused. Unless your WiFi is open someone seeing your network can’t find out what the WAN IP is.

    And getting your ip can connect the people directly to your box

    “Connect” is a strong word here. Yeah, they can send traffic at it. But that shouldn’t do anything.

    A trace route command to this IP could return intermediate equipment of your isp, helping to pinpoint your town or even your street.

    This is the most reasonable concern. Depending on your ISP and location the IP itself or packet tracing you can get a pretty good idea of the user’s location.