• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle
  • Usually it’s a case of a well thought out decent post, but then you scroll down to comments and it’s “men are trash” and etc, so you end up with a bunch of fighting, which detracts from the original point.

    Prolly would be better if “comments on this are disabled” was more common practice.

    Or if administrative systems actually punished people heavily for saying stuff like “(any group of people) are trash”



  • pixxelkick@lemmy.worldtoSelfhosted@lemmy.worldstatic website generator
    link
    fedilink
    English
    arrow-up
    27
    arrow-down
    1
    ·
    edit-2
    2 months ago

    I use Hugo, it’s not super complicated.

    You basically just define templates in pseudo html for common content (header, nav panel, footer, etc), and then you write your articles in markdown and Hugo combines the two and outputs actual html files.

    You also have a content folder for js, css, and images which get output as is.

    That’s about all there is to it, it’s a pretty minimalist static site generator.

    Hosting wise you can just put it on github pages for free.


  • Well yeah, I’d hope so, that’s the entire point.

    Catcha’s data collection always was with the intent for training ai on these skills. That’s “the point” of them.

    It’s reasonable to expect that the older version of captchas can now be beaten by modern ai, because they’re often literally trained on that exact data to beat it.

    Captcha effectively is free to use on websites as a tool because the data collection is the “payment”, they then license that data out to people like OpenAI to train with for stuff like image recognition.

    It’s why ai is progressing so fast, captchas are one of humanity’s long term collected data silos that are very full now.

    We are going to have to keep progressing the complexity of catches as it will be the only way to catch modern AIs, and in turn it will collect more data to improve it.



  • Because having people download static map data for the entire planet just to play a game is untenable.

    You shouldn’t have to download the entire planet though.

    The game 100% should support installing local specific areas you wanna fly around, that anyone could then keep a copy of.

    If a user wanted to cache an entire 8 TB of the entire world on a drive, they should be able to just do that (and thus have forever support without worrying about internet services staying online)

    At least, as a snapshot of what the world looked like in 2024.

    I don’t see why users shouldn’t have the option to locally HD save the data if they want to, to avoid maxing out their internet bandwidth in one sitting.



  • Yeah this is just noticeable because most products weren’t even resealable, they just expected you to seal em yourself with a clip, twist em, put em in a container, etc.

    Now they are adding cheap resealable zips to the bag, which is nice in theory but the bag material has to be strong enough to support it.

    Actual ziplock baggies themselves are made of thick plastic that can take a bit of abuse.

    But cheap paper plastic hybrid materials a chip bag us made of can’t handle that sort of load, so it becomes the fail point.





  • I have no idea what people are fucking up tbh.

    It’s 2 button clicks to cast stuff, I just went and sanity checked.

    The internet is full of disinformation and idiots though so I usually just assume people are the issue, when I have the same hardware and zero issues.

    I don’t think chromecasts have even gotten any kind of major change updates in ages so it’s bizarre for it to change behavior.

    I’m gonna just keep going with “people are dumb” until someone posts some concrete example (IE an actual video) of wtf their issue is.

    The chromecast is designed so simply though that I can’t imagine wtf people are fucking up.



  • I wrote it up elsewhere, but I don’t mind the price point.

    The built in ethernet port covers a lot of that.

    A solid quality ethernet dongle is gonna be $25, so now that’s $75 for the 4k CCwGTV + ethernet.

    So you’re paying $25 extra for the better form factor (2 chained dongles look so bad), the extra ram, better processor, etc

    For some folks that might not matter, but I use Steam Link on my CCwGTV and those specs will likely make a tangible boost in gaming performance for quality, frame rate, latency, input lag, etc.

    So in my demographic of people gaming with em, I 100% expect it’ll be a popular upgrade.

    The ethernet part is pretty big, overall. Don’t overbook that.


  • The built in ethernet cable seems almost worth it.

    It’s around $15 to $20 to add on a usb c ethernet dongle to the existing CCwGTV dongle if you want high speed connection to it (which you prolly do if you wanna stream 4k or lower latency game with Steam Link )

    Better quality dongles are closer to $25 if you dont want it to crap out.

    So, assuming the onboard ethernet is comparable to a higher end dongle, you’d be looking at closer to $75 to get the same experience with the Older CCwGTV model. ($50 + $25)

    Add in the higher specs and the fact that chaining 2 dongles together looks ugly as fuck and easier to fail, and the +$25 remaining ($75 -> $100) is not actually too horrible of an extra price.

    $100 for a better form factor (the dongle does look bad), better specs, built in ethernet, it’s not terrible ngl.

    I game with Steam Link all the time on my CCwGTV so I 100% am gonna spend the money on better specs so I feel like I’m taking better advantage of my 4060ti I’m Steam linking to.

    If it has a better bluetooth card too that’s gonna be even bigger, better wireless controller range is awesome.

    That extra RAM is not something to scoff at.

    The extra storage is kinda dumb though, prolly the real cash grab. I doubt anyone was maxing out their CCwGTV storage capacity o_O




  • Why is this being framed this way.

    Rebranding the next gen of your product isn’t “killing” it, people are so fucking clickbaitable.

    It’s the same product, just next gen with better specs abd they’re going with a new simpler brand name than “Chromecast with Google TV” (yes that’s the actual product name before) and instead the next gen is named “Google TV Streamer”

    It’s the exact same thing, and all existing hardware will keep working.

    Chromecasts are standalone and effectively just running a modified version of Android. They can’t really be “killed” as they work over local network. Theoretically any chromecast will last forever as it’s functionality is based off a specified open source protocol, so as long as you have a device that can output it (cast), you can cast to your chromecast.

    So it’s impossible to “kill”. I have a gen 1 chromecast that still 100% works fine today.

    Newer Chromecasts ahem Google TVs just have more features, like apps you can install and sideload.

    People are dumb for falling for this clickbait title.


  • See as a C# dev, all the time I think to myself l, “Proffessionally, you should pick up and really learn C++ mate”

    Then I see blog posts like this where the author writes for pages and pages about how to get something as simple as await to work manually and I immediately am reminding why even after 11 years I still haven’t picked up C++ outside of little things for SBCs and whatnot.

    I can see the fun in building such things by hand, but at a certain point I want to be able to actually start a project and jump straight into writing the application itself, and not need a tonne of boilerplate just to get modern functionality.

    I will note for this statement:

    This is less of a problem if your coroutines are long-lived.

    Is typically true. Usually your coroutines (should) all spin up at the very start and all stay running for the entire app lifetime.

    Usually, in my opinion, constantly spinning up and spinning down coroutines is a code smell, and us remedied with some form of pub/sub model where your “background” coroutines should always be running, and they just idle waiting at some kind of subscribed pipe for events to respond to and process.

    That way you allocate everything you need at the start, then it all just sits and runs for the entire app lifespan.