• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: August 26th, 2025

help-circle




  • I think you’ve vastly underestimated how much digital media people consume…

    But setting that aside, there are real efficiency wins from scale. I am a self-hoster, I have a fleet of machines I manage with Nix, I run local LLMs and do real work on consumer gaming hardware, i’m a huge fan of federated and distributed peer systems. I am 100% for that. The cloud is just somebody else’s computer. And I’m saying we also need the gigantic warehouses. Absolutely.

    The issue is zoning and environmental concerns and the effect on communities and strain on public infrastructure. All issues worsened by the AI boom and incentivized by capitalism.

    There’s a way to do datacenters right and its been done before. You just need legislation and enforcement. The problem isn’t datacenters: the problem is that the same people putting up datacenters are the same people who own your politicians


  • Using nix to maintain my fleet with automated updates so I didn’t really need to worry about it thankfully; just checking that I had relevant/patched versions. All my services are nice and up to date so didn’t even have to take anything down (yay)

    What I’m excited for today is to progress personal slop project (be gentle) I started yesterday. Hoping it’ll just be one or two weekends.

    I’ve been hallucinating a transcoding suite/workbench. Includes experimental sampling matrix of ffmpeg settings with a composable / layer-based project configuration; rust egui+mpv desktop client. Then the hosted orchestration server can distribute ffmpeg jobs across my worker machines (via my local headscale tailnet). Output produces a project+metadata bundle that includes hand-picked source:result JXL frame comparisons alongside both human readable reports and client readable configuration that makes the projects (more or less) reproducible (with worker tool env versioning via nix flake.lock) and logs provenance.

    I intend for this to be a replacement to the piles of crappy python scripts I’ve been using for the last decade; my current workflow is to move files into host-labeled ingest folders with an argument string in a text file, then ssh to the host to run the job.

    But what I’m most excited for is the experimentation matrix. I hope that it will reduce my electricity usage and disk thrashing; it will let me sample settings for ~1minute of footage around the sample frame and let me iterate my tuning much faster. Currently, it’s faster (in terms of hands-on time) to just transcode whole episodes or even entire seasons multiple times with different settings and then just discard the ones that underperform. Extremely wasteful; testing a settings matrix is something I’ve always wanted, but never had the time to build (and still don’t, hence slop).



  • I’m all over this multi-dimensional spectrum…

    I think AI is terrible for society; at least how society is currently structured. I also think society is terrible for AI.

    The reason AI sucks, and the reason we’re even calling this tier of ML “AI” to begin with, is because of global capitalism’s incentives. And the reasons “AI” is bad for society is because our society is globally capitalist. From jobs, to loneliness, to disinformation, to the environment, to education, to the lack of critical thinking,… Everything AI makes worse is already weakened by our societal systems, and they incentivize using AI to further degrade them in order to expand, control, and extract.

    I love AI and the world, in theory. I hate AI and the world for how they exist right now.


  • You would understand a one-time fee for an active, ongoing, online service?? I’m a fucking communist, please don’t make me defend capitalism…

    Even back in the day, people would buy versions of software on disks and updates were limited. There’s a reason why the idea of perpetual licenses died hard and fast and every company everywhere either reneged or died.

    I pay for Kagi. If they offered a “one-time lifetime purchase” I’d probably just stop because that would be a giant red flashing neon warning sign.


  • ImgurRefugee114@reddthat.comtoTechnology@lemmy.world•A Markdown File Should Just Open
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    13 days ago

    not in spite of it

    I agree.

    Everyone can write in Markdown already, I’ve seen people physically write asterisks for emphasis on paper (edit: I’m not saying markdown came first…). But not everyone can see it rendered.

    This is mostly addressing the latter, so that we don’t all have to just imagine what the formatting looks like, and so that it can be used in settings where currently it would fit perfectly well, but it isn’t acceptable because it isn’t rendered.

    I’m perfectly comfortable reading a raw Markdown file. That doesn’t really fly in a business setting. or in most places where people want formatting. There’s a reason people don’t just write [bold] in the middle of their resume/report/paper and expect the reader to visualize it with their mind’s eye.

    The problem is that everybody knows Markdown, not everyone knows that it is Markdown or that Markdown files exist. And even if they do, they still can’t use it because support isn’t as ubiquitous as the formatting syntax. Making MD files more accessible would mean that people can use the knowledge they already have and learn more and be able to use it places where they want to.

    Currently, people who could otherwise just use markdown are forced to use proprietary formats that are supported by their organizations or that they can expect the recipient open, like a a docx or PDF


  • Your first paragraph makes a very good point. I could understand that as an impulsive motivation. Thanks.

    Yes, I also don’t want Markdown turning into a binary format. Absolutely. In fairness, I can see the risk of that in some situations. e.g. my professional obsidian vaults are so heavy on JS and custom plugins that the render is significantly detached from the source text, using dynamic elements. I guess I could see an unfortunate world where people push into that. But I only really see that as if it is a complete replacement for other document formats, which I don’t think it is. It’s sort of like text++ rather than odt–

    I don’t see markdown replacing advanced formats in all cases like that, but I think it’s sufficient, even in its most basic forms, for the vast majority of people.


  • Oh yeah, I’m not gonna lie, I’m totally crashing out in the comments.

    To be clear, my point isn’t so much that people are aggressive, but rather that they’re hostile to the message of the article, which is as far as I can tell objectively a good thing that everyone should desire: more success for markdown, easier to use for more people.

    How this is drawing such near-universal criticism (at the time of writing) is utterly dumbfounding to me.


  • Yeah, it just confuses me why people here are arguing against the idea that markdown should be more accessible to the normal user. I read this the moment I woke up and it’s been driving me a little mad. The formatting is literally one of the most ubiquitous things you can come across on the internet.

    I understand that maybe this is something Microsoft et al would not rather pursue because they have their own proprietary formats they want to push instead… But why was every Lemmy comment here attacking the article? Do we not like free and open source standards any more? Do we not want these things to succeed?

    Like, if you just want to say the author is a dumbass, then sure, but I don’t understand why people are so aggressive against the idea of making Markdown easier to use…


  • They’re not solving anything, though. They’re pointing at a problem and saying it should be solved. That’s pretty different. Why the hell am I defending this so hard? Why the hell is everyone here attacking it so hard? I am so confused. It is not a bad thing to mark down to succeed or have more support. You all confuse me very much. Is this a tankie community? It’s really hard to follow the complete lack of logic.


  • Not to mention that you are doing all that for a document format that the non-tech/average user has never even heard of probably.

    Just wanted to point out that literally everyone already uses it, in these very comments no less. On discord, in game chats that don’t support it, in regular text files. Literally, everywhere on the web, grandmas are using Markdown.

    I know this is hard to hear, but…

    Making Markdown files easier to use for the normal person is not a bad thing.


  • ImgurRefugee114@reddthat.comtoTechnology@lemmy.world•A Markdown File Should Just Open
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    4
    ·
    edit-2
    13 days ago

    Holy fuck you guys are stupid…

    “Full hardware support” for a text format? The standards he likes? They said they wanted cross-platform support and named the biggest and most ubiquitous standards there are. You know, the ones you used to type your comment.

    What the fuck are you on about? Where’s this agro coming from?

    “I think people should be able to use markdown easier” >screaming nerd rage ensues


  • ImgurRefugee114@reddthat.comtoTechnology@lemmy.world•A Markdown File Should Just Open
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    7
    ·
    edit-2
    13 days ago

    I’m not sure why you’re criticizing the article by mentioning nuances as if they didn’t also mention them in the article…

    The point is that when they average person double clicks an MD file, it should probably open and display.

    They’re also like a bazillion different PDF and TXT formats, but viewers for them are rather ubiquitous.

    You might say that nobody uses PDF viewers because they just opened them in a browser. Well, that’s also a suitable approach for MD.

    The support doesn’t have to be comprehensive. I don’t think they’re asking for the God of all viewers and editors that supports every different styling and switches between them automatically.

    The idea is that if you send someone a markdown file, they should be able to read it without having to go into a menu and opening with a text editor. You know, like Normies do with a bunch of far more complex standards already…

    My guess is that this is because Markdown is mainly used by technical folk, and they’re fucking stupid when it comes to end-user experience and just haven’t considered it much. And the other reason is that the big players would rather push their proprietary formats so they don’t want to see adoption of Markdown.

    The author is right. Widespread, ubiquitous support is far overdue for such a simple format. Your remarks about cellphones not opening text files isn’t a great argument against not opening markdown files; frankly, I think it’s absurd that they don’t, and that should be pointed out rather than used as an example of why we shouldn’t bother for MD. If an OS shipped on a floppy drive could have a text editor out of the box, I’m pretty sure your fancy multi-gigabyte smartphone in $current_year could do it too.

    I swear, these comments are depressingly stupid. Imagine arguing about this for any other format…

    Yes, markdown should be more accessible and its files should be easier to use. Why? Because everybody uses it already, even if they don’t know what it is. That’s how ubiquitous it is, and supporting it out of the box is what you’re arguing against. It’s hard to comprehend. Are you employed by Microsoft?