• 0 Posts
  • 45 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle

  • It’s pretty common to own a domain but not actually host the email server; doing on-premises email is a security PITA and most providers simply blacklist large swathes of residential and leasable (e.g. VPS) IPs.

    Unfortunately, if you get someone else to host your email, they often charge by the account, not by the domain. Setting up a new mailbox is therefore irritatingly expensive.

    A catch-all email works well, though, and is free from most of the hosting providers. Downside is you get spam…

    Jane@JaneDoe certainly seems more common than mail@JaneDoe.




  • Indeed, the US has a major lack of fixed-line competition and lack of regulation. Starlink doesn’t really help with that, at least in urban areas.

    I’m not familiar with the wireless situation. You’re saying that there are significant coverage discrepancies to the point where many if not most consumers are choosing a carrier based on coverage, not pricing/plans? There’s always areas with unequal coverage but I didn’t think they were that common.

    Here in NZ, the state funding for very rural 4G broadband (Rural Broadband Initiative 2 / RBI-2) went to the Rural Connectivity Group, setting up sites used and owned equally by all three providers, to reduce costs where capacity isn’t the constraint.


  • You definitely would have legal issues redistributing the ad-free version.

    Sponsor block works partly because it simply automates something the user is already allowed to do - it’s legally very safe. No modification or distribution of the source file is necessary, only some metadata.

    It’s an approach that works against the one-off sponsorships read by the actual performers, but isn’t effective against ads dynamically inserted by the download server.

    One option could be to crowdsource a database of signatures of audio ads, Shazam style. This could then be used by software controlled by the user (c.f. SB browser extension) to detect the ads and skip them, or have the software cut the ads out of files the user had legitimately downloaded, regardless of which podcast or where the ads appear.

    Sponsorships by the actual content producers could then be handled in the same way as SB: check the podcast ID and total track length is right (to ensure no ads were missed) then flag and skip certain timestamps.


  • Starlink plugs the rural coverage gaps, but in urban areas it’s still more expensive than either conventional fixed-line connections or wireless (4G/5G) broadband. Even in rural areas, while it’s the best option, it’s rarely the cheapest, at least in the NZ market I’m familiar with.

    It also doesn’t have the bandwidth per square kilometre/mile to serve urban areas well, and it’s probably never going to work in apartment buildings.

    This is a funding/subsidisation issue, not so much a technical one. I imagine Starlink connections are eligible for the current subsidy, but in most cases it’s probably going to conventional DSL/cable/fibre/4G connections.


  • The screen turning off when it automatically locks is an added bonus; the priority is to be able to command the system to simultaneously lock and turn off the screen. You’re correct that the setting at zero seconds safely achieves that.

    I’ve had other, more stupid uses for running commands, though I don’t think any are actively in use.

    Taking actions on network reconfiguration, charge completion, and SMART failure are all things that spring to mind. It’s nice to be able to set those kinds of things in a GUI rather than putting them in /etc/something.d


  • What I want is not (just) that the screen turns off when the lock timer times out, but that I can push ‘lock’ or a key combination and have the system lock and the screen turn off immediately.

    The new ‘when locked, turn off screen’ setting should help with this, but setting it too low will presumably make it hard to unlock.

    For running backups, ‘after a period of inactivity’ could help.

    It still seems like the removal of a useful feature.





  • Aggregate bandwidth now rivals or slightly exceeds gigabit wired connections.

    Where that aggregate bandwidth is shared amongst large numbers of users, bandwidth per user can suffer dramatically.

    Low density areas may be fine, but cube farms are an issue especially when staff are doing data intensive or latency sensitive tasks.

    If you’re giving employees docking stations for their laptops, running ethernet to those docking stations is a no-brainer.

    Moving most of the traffic to wired connections frees up spectrum/bandwidth for situations that do need to be wireless.