• 0 Posts
  • 51 Comments
Joined 11 months ago
cake
Cake day: November 29th, 2023

help-circle

  • I still have PTSD from the era of the ‘polyphonic ringtone’ hype. Those were the ‘fancier’ ringtones that weren’t just your usual beep or bell.

    Usually you’d buy them by sending a text message to some expensive number and it would be sent to your phone. If you were dumb, you could get basically scammed into a ‘subscription’ so you’d get sent these expensive ringtones frequently. Many a teen got yelled at for that mistake in the late 90’s.

    If you were a tech savvy lad, you could hook your phone up to your Windows PC and upload shitty ringtones yourself as well as wallpapers and such.

    These days, who gives a shit? My iPhone ringtone is still the default ring. I honestly don’t care what it is, as it’s usually just annoying anyway.



  • It gets even wilder when you tell younger people that PC’s didn’t even come with storage drives in the early days. One of the earliest I used had to have software loaded through cassette tape. That was certainly a bit annoying, as it took quite a while and was error prone.

    These days I somewhat collect old hardware. I love things like my Macintosh Plus where you need to juggle disks in order to load software in the memory so you can use it. Nowadays a single text e-mail outweighs the entire OS for a system like that.



  • Guess I should stock up while I can huh?

    I’ve been a RPI fan since the beginning and have used their boards for all sorts of projects and tinkering. But it’s hard not to feel like it’s losing sight of what made it attractive in the first place: low power and low priced computing. It had its charm in buying a Pi Zero and just chucking emulators on it and handing them out to folks who might want to have a go.

    But with the more expensive, more powerful hardware you just can’t really use them for things like that anymore. Just too expensive and too much oomph for the use case.

    We’ll see if the company finds its way. But this usually isn’t a good sign…




  • Pretty much this, yes.

    There’s also the complexity of approach procedures that they need to follow in order to mitigate noise complaints. Back in the old days, they’d just fly from radio beacon to radio beacon, with look-out-the-window navigation for the final approach.

    These days, lots of airports are within or close to cities, which means a much more complex routing and specific altitude and speed restrictions. GPS made that possible; they’re simply too much workload for pilots.

    So yeah, in emergency situations where GPS fails completely, there’s going to be some changes to procedures needed in order to make that work. They’d also need to increase separation between planes in order to prevent problems.

    The simple solution is: nobody should fuck around with GPS since we literally all benefit from it.





  • He does excellent reviews and stuff in general.

    I actually watched it before the ‘controversy’ and I think it certainly was a fair assessment. He clearly states the goal of the product and where it falls short. None of his criticism seems unreasonable.

    Clearly, it’s trying to be an always-online communication, assistant and logging badge. Like a Star Trek commbadge on steroids. In theory, that’s a product that I’m very interested in. But when features are structurally unsound or actively annoying to use, well, I’m going to stick with the phone I’ve got.

    Ironically, his ‘bad review’ got me interested to see what a version 2 will be like. Assuming they make it that far.


  • No single bad review ever killed a product. Because we all know that some things are just a matter of opinion, user error, etc. Opinions are like assholes: everyone’s got one. If I’m interested, I’ll read several positive and negative opinions.

    But if your product is bad enough to warrant several bad reviews, that’s on you. Should’ve done better research, should’ve made a better product.






  • Well, the tech is of course still young. And there’s a distinct difference between:

    A) User error: a prompt that isn’t as good as it can be, with the user understanding for example the ‘order of operations’ that the AI model likes to work in.

    B) The tech flubbing things because it’s new and constantly in development

    C) The owners behind the tech injecting their own modifiers into the AI model in order to get a more diverse result.

    For example, in this case I understand the issue: the original prompt was ‘image of an American Founding Father riding a dinosaur, while eating a cheeseburger, in Paris.’ Doing it in one long sentence with several comma’s makes it harder for the AI to pin down the ‘main theme’ from my experience. Basically, it first thinks ‘George on a dinosaur’ with the burger and Paris as afterthoughts. But if you change the prompt around a bit to ‘An American Founding Father is eating a cheeseburger. He is riding on a dinosaur. In the background of the image, we see Paris, France.’, you end up with the correct result:

    Basically the same input, but by simply swapping around the wording it got the correct result. Other ‘inaccuracies’ are of course to be expected, since I didn’t really specify anything for the AI to go of. I didn’t give it a timeframe for one, so it wouldn’t ‘know’ not to have the Eiffel Tower and a modern handgun in it. Or that that flag would be completely wrong.

    The problem is with C) where you simply have no say in the modifiers that they inject into any prompt you send. Especially when the companies state that they are doing it on purpose so the AI will offer a more diverse result in general. You can write the best, most descriptive prompt and there will still be an unexpected outcome if it injects their modifiers in the right place of your prompt. That’s the issue.