I’m the administrator of kbin.life, a general purpose/tech orientated kbin instance.

  • 2 Posts
  • 511 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle

  • Yeah, but they’re not. That’s the modern world. But also even if it was a web server there’s usually ways to advertise the IP for the app to connect to. I’ve seen other stuff do that. So getting an IP is easy. Once the app knows the IP and if you really want to allow connections from outside to your IOT devices (I wouldn’t) it could remember the IP and allow that.

    You really don’t need to give a fixed IP to everything. I think I’ve given 1 or 2 things fixed IPv6 IPs. Everything else is fine with what it assigns itself.



  • Hah. But to be fair, ATM did have a specific use that it worked great for. That is the move to digital voice circuits. The small fixed cell size and built in QoS meant that if you had a fixed line size you could fit X voice channels, and they would all be extremely low latency and share the bandwidth fairly. You didn’t need to buffer beyond one cell of data and you didn’t need to include overhead beyond the cell headers.

    ATM was designed to handle the “future” or digital network needs. But, the immediate use was about voice frames and that likely dictated a lot of the design I’d expect.




  • I think in 99% of use cases, upgrading isn’t a problem. Most of the time new SQL versions are backward compatible. I’ve never personally had a problem upgrading a database for a product that expects an older version.

    They do have compatibility modes too, but those only go back so far too.

    But, I think companies with their production databases for perhaps older complex systems are likely very weary of upgrading their working database. This is most likely where this situation comes from. Imagine being the person responsible for IT, that upgraded the DB server and database to the latest version. Everything seemed to be working fine. Then accounts run their year-end process, it falls over and now there are months of data in the newer version that won’t work properly. It’d be an absolute pain to get things working again.

    Much safer to leave that SQL 2005 server doing what it does best. :P


  • I’d go further than that and say that deciding to leave the house or not, are both gambles.

    But in the context of spending money with the only net result being you lose money, make money or retain the same money with no other goods or services provided in return. Then gambling is the primary attribute of that spend.

    Bookmakers and investments meet that criteria, your other purchases are not.




  • There are, and I think the only real difference has been the community support. The community was behind the original pi and the guides, images and support show that, and it continues to this day.

    If this becomes “enshittified” then communities will grow around the alternatives, it’s likely there will be an overall winner (or winners per class) and we’ll move on. The device itself wasn’t ever the whole story.


  • Well, it’s generated in the same way as modern tones are in a telephone exchange, not a played sample. You can usually configure the tone frequencies (never tried on cisco ip phone, but asterisk allows it for its own generated tones and I had a cisco ATA that let you configure them).

    So, unless we’re limiting ourselves to the original mechanically generated dial-tones. I’ll consider them for all intents and purposes to be one and the same.

    E.g. for the UK on cisco/sipura ATAs you would use the configuration found here https://teamhelp.sipgate.co.uk/hc/en-gb/articles/208200875-UK-Regional-Settings-Cisco-Linksys-Sipura-Adaptors and as an example (dial tone)

    Dial Tone: 350@-19,440@-22;10(*/0/1+2)

    The comfort noise is also generally only added when there’s no other noise on the call. This is to prevent you thinking you were disconnected when no-one is talking.




  • Ironically I just left the startup world for a larger more established company and the code is some of the worst I’ve seen in a decade. e.g. core interface definitions without even have a sentence explaining the purpose of required functions. Think “you’re required to provide a function called “performControl()”, but to work out its responsibilities you’re going to have to reverse-engineer the codebase”. Worst of all this unprofessional crap is part of that ground-up 2nd attempt rewrite.

    I think this is actually quite common in commercial code. At least, for most of the code I’ve seen. Which is why I laugh most of the time when people imply commercial code is better than most open source code. It’s not, you just cannot see it.


  • And of course, if they can charge you for a static IP then defaulting to dynamic is imperative, isn’t it? Pretty sure they’d try that with IPv6 too just to keep the income stream.

    I’ve mentioned it elsewhere. Some ISPs here in the UK have a dynamic IPv6 prefix. Want a static one? Sure, pay up.

    I suppose to an extent this kind of thing is akin to low cost airlines. Sure you can “technically” get a flight for €15. But once you’ve made it even remotely bearable you’ll be paying around the cost of a full service airline. But, it does make it very hard to have a website doing a proper price comparison.

    I suspect it’s the same here. I pay a bit more than most ISPs. But for that, I get decent in country support, fixed IPv6 prefix and static IP (I actually have a legacy IP block, but you don’t get those included in the base price any more). Whereas plenty of other providers charge less, but will charge you for anything beyond the most basic of connections. It means my ISP always appears at the expensive end of price comparisons.


  • But this is another interesting thing. Dynamic IP addresses made sense, when we were dialling up for internet, and the internet wasn’t the utility it is now.

    Back then we’d dial up for a few hours in the evening or weekend. Businesses that didn’t have a permanent presence would connect in the day to send/receive emails etc. So, you could have 500 IP addresses to around 1500 users and re-use them successfully.

    But now, what is the real point in a dynamic IP? Everyone has a router switched on 24/7 sitting on an IP. What is the real difference, in cost in giving a static IP over a dynamic one? Sure, CGNAT saved them IP addresses. But, with always on dynamic just doesn’t make sense. Except, that you can charge for a static IP. The traffic added by the few people that want to run services is usually running against the tide of their normal traffic. So, that shouldn’t really be an extra cost to them either.

    If everyone that ran a website did the extra work (which is miniscule) to also operate on IPv6, and every ISP did the (admittedly more) work to provide IPv6 prefixes and ensure their supplied routers were configured for it, and that they had instructions to configure it on third party routers, IPv4 would become the minority pretty soon. It seems like it’s just commercial opportunity that’s holding us back now.