Just another Reddit migrant, not much to see here.

I subsist on a regular diet of games, light novels, and server administration.

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

help-circle

  • The title of that article does not support its conclusion. Lazy pasting what I commented the last time I saw this.

    Nothing has changed for LTS at all. Scroll down to the pretty graphs on https://ubuntu.com/about/release-cycle, and pay particular attention to how the ratio of orange to purple on the LTS graphs has changed over time. (it hasn’t) The base LTS support window has always been 5 years, and the extended window has always been another 5 years.

    What they did add was additional security updates for Universe packages, which are represented by the black line. Note that this black line is independent of the LTS coverage. From https://discourse.ubuntu.com/t/ubuntu-pro-faq/34042:

    Your Ubuntu LTS is still secured in exactly the same way it has always been, with five years of free security updates for the ‘main’ packages in the distribution, and best-effort security coverage for everything else. This has been the promise of Ubuntu since our first LTS in 2006, and remains exactly the same. In fact, thanks to our expanded security team, your LTS is better secured today than ever before, even without Ubuntu Pro.

    Ubuntu Pro is an additional stream of security updates and packages that meet compliance requirements such as FIPS or HIPAA, on top of an Ubuntu LTS. Ubuntu Pro was launched in public beta on 5 October, 2022, and moved to general availability on 26 January, 2023. Ubuntu Pro provides an SLA for security fixes for the entire distribution (‘main and universe’ packages) for ten years, with extensions for industrial use cases.

    You can also dig into this AskUbuntu answer for even more details, but the long and short of it is this has no impact on Ubuntu LTS whatsoever. Keep using it if that is your thing. Keep using something else if it is not.

    This old news will become newsworthy if Canonical starts shifting packages out of the main repo and into universe, which would in fact reduce the security update coverage of LTS releases. That said, the article has not asserted any evidence of this. Nothing to see here…for now.




  • having people go out for original research is basically saying “Let people make up bullshit.”… not a good idea.

    Yeah, I’ve seen what this does to fan wikis. There is a certain type of personality that thrives on having their version of reality be what is reflected in wiki articles, and they will revert any and all attempts to excise their personal theories. If admins step in to break up the edit war, it’s clearly “favoritism” and “admins should only exist in service to the users and have no say in content”. Some of these wiki addicts go out of their way to become the wiki equivalent of Reddit’s supermods in order to ensure that they have the upper hand in these content disputes.

    “No original research” is one of the core pillars of your ability to push back against delusional nonsense. If you’re determined to live without it, you need to have very strong content standards in its place to decide the difference between objective fact and someone’s conspiracy vomit. Good content policies save you from having to waste a bunch of time on bad faith arguments about why the content of your wiki pages have to abandon fact for massaging someone’s ego.

    (Somewhat of a tangent, but if you’re bored you can look into a brief history of AlexShepherd’s crusade against circumcision in the Silent Hill fandom. He’s not the only person I’ve seen thrive on wikis who don’t adopt an original research policy, but definitely the most entertaining read.)


  • I’m also here to expose bad excuses.

    Not being able to help someone who is refusing to provide technical detail is a pretty damn good excuse in this industry.

    If your goal is to expose the bad excuses of others, step one is to put in as much effort as you’re expecting from others. :P


    Edit for good measure: (links fixed, forgot about direct linking comments from outside of a lemmy instance)

    • Your instance was not federating with lemmy.world. [1]
    • You assumed that the blame had to rest on lemmy.world because you had “eliminate[d] all the possibilities [you] had at hand”. [2]
    • You made this post to vent about a bunch of unrelated nonsense and refused to provide technical detail that would assist the admins in troubleshooting. It’s a given fact that your privacy is your choice, but it’s also a given that you shouldn’t be a dick about it if you choose to withhold details, even from PM. For the record, the information being requested was the bare minimum for an instance administrator to troubleshoot network interactions with a remote instance.
    • A random (but cool) third party identified the issue with your instance not federating. [3]
    • Instead of apologizing, you proceeded to act like you were entitled to that solution from the admins you wrongly accused. [4] You are not god’s gift to the internet and they are not technical support for your instance.

    There’s no room for niceties here, you are either an asshole in denial or some brat who is too young to know any better. Sleep on it. Come to terms with that fact and make good on it, or don’t. You aren’t worth anyone’s energy, and I’m only bothering with this summary for everyone else’s sake. Your problem is fixed, it was never on lemmy.world’s side to begin with, and somehow you are still acting like the failure of the admins to figure out what was busted with your shit is some Sherlock gotcha moment.

    I am unaffiliated with lemmy.world and my toxicity does not represent the opinions of the admins. (but they’re probably thinking it)