• 1 Post
  • 35 Comments
Joined 2 years ago
cake
Cake day: October 4th, 2023

help-circle



  • If you mean a post, you can only chose one image to be the target of your post, but you can embed more in the text of your post.

    If you mean a comment, I’m not sure the source of confusion. You can embed multiple images. The Lemmy Web UI should work, as well as all the clients I’ve used.

    You just need to have the text:

    ![](url-to-image)
    

    …in your comment text.

    Most Lemmy home instances will be runnimg a pict-rs instance, and let you upload an image to it with a button near the comment text field and also add the above text to display that image in your comment in one go.

    If you’re trying and it’s failing, there can be a maximum byte size placed on the pict-rs upload by your home instance, and it’s possible that maybe your first image is below it and your second is not. There are also some image formats that wouldn’t be recognized, if you’re using something exotic for your second image — that could also cause the upload to fail.



  • Flashlights produce orders of magnitude more light than any smartphone.

    Flashlights can definitely put out a lot more light (and store more power) than a cell phone light, but for a lot of close-up stuff, the cell phone is fine.

    I’m skeptical that flashlights will go away, as @RegularJoe@lemmy.world is proposing. But I do think that smartphones are a partial replacement.

    In urban areas, I don’t need a bright flashlight much, because there’s fixed lighting all over, but in more rural areas, if you’re outside at night and walking around, you do tend to need a flashlight.

    I also don’t know how much more change there will be. Like, people already have smartphones pretty much everywhere. I think that most of the replacement that will happen has probably already happened.









  • I think that the question of whether an industry would benefit is a hard one. It depends on your perspective and what benefits one is gonna aim for.

    I think that if I had to choose one category, I’d do CAD.

    So, this covers a wide range of different industries and roles. 3D and 2D mechanical engineering. Chip and circuit board design. Designing 3D objects for 3D printers.

    There is open-source CAD software out there, of varying degrees of sophistication and for different purposes. But in general, I kind of expected to stumble into a huge wealth of world-beating software. I mean, it’s a field with a lot of technically-oriented people who don’t mostly compete on the software as their core competency. I could see a lot of people wanting to scratch itches, and the situation to be kinda like it is for mathematics software, with strong open-source entrants. But that isn’t the case. There’s very much usable stuff, depending upon what you want to do. But the big boys in the field are proprietary.

    There’s FreeCAD. I use openscad to do code-oriented design of objects for 3d printers. I wouldn’t call Blender a CAD package, more a modeler, though it’s adjacent to the field and there is some CAD-related add-on stuff. There’s QCAD. I don’t know how practical BRL-CAD is today, but it’s out there.



  • I have a Bluetooth Ultimate (keep in mind that 8BitDo makes a wide range of “Ultimate” controllers with extremely-confusingly-similar names, which don’t have the same hardware and have a wide range of prices, so be very careful when buying to ensure that you’re getting what you want; for example, when I bought mine, the “Bluetooth Ultimate” had Hall effect thumbsticks and the “Ultimate” did not. The “Bluetooth Ultimate” didn’t have a Xbox-style face button layout available, just a Nintendo one; you could remap this in software, of course, but the gamepad itself couldn’t do the mapping. Then there’s an “Ultimate C”, and it sounds like also an “Ultimate 2”).

    I’m fine with its ergonomics.

    But, then…I’m also fine with the ergonomics of a bunch of other gamepads that I have.

    My own take is that pretty much all controller ergonomics are fine. The only gamepad I’ve ever used that I’d call outright bad was the original rectangular NES gamepad from the 1980s. These have a hard, squared-off D-pad that will absolutely kill your thumb with enough use.

    Probably dishonorable mention goes to a wired Logitech controller dating to the 1990s, and to a lesser extent, a later Logitech controller; these had a D-pad that rolled to the diagonal too easily.

    All modern controllers that I’ve used are noticeably more-comfortable for extended use than gamepads from the '80s and '90s.

    I’ve owned a wide range of Playstation, Xbox, third-party, etc controllers, not to mention joysticks and other game control devices, and I’ve always been generally pretty happy with the ergonomics. That doesn’t mean that they don’t differ, but it’s pretty doable to adapt to the differences. Symmetric Playstation-style thumbstick layout, asymmetric Xbox-layout. Some are heavier, but nothing enough to really bug me. Nintendo face button layout vs XBox face button layout can be remapped in software. I’ve been able to adapt to different trigger pull force levels. Clicky face buttons that are popular on some new controllers versus no-tactile-feedback buttons. Controller bodies of slightly different size and shape. A new, different controller might feel weird at first, but in general, I’ve found that the brain is pretty good at bridging the differences.

    Some have more buttons, and in recent years I’ve had enough bad luck with stick drift that I’ve moved to Hall effect thumbsticks. Some don’t have rumble motors. Some have RGB lights. One could prefer a gamepad over another for various functionality reasons, but…I think that on ergonomics, vendors have pretty much done a good job.


  • I mean, you can run a Linux phone now:

    !linuxphones@lemmy.ca

    Downside is that aren’t going to have a large software library optimized for touchscreen use. The hardware options are pretty disappointing compared to Android. Not all hardware functionality may be supported, if it’s on a repurposed Android phone. Android or iOS software is mostly designed to expect that it’s on a fast/WiFi connection some of the time and on a slow/limited mobile data link some of the time and be able to act accordingly; most GNU/Linux software is not. Battery life is often not fantastic.

    I still haven’t been pushed over the edge, but I’m definitely keeping my eye on it. I’m just not willing to develop software for Android. I know that GNU/Linux phones will stay open. I am not at all sure that Android won’t wind up locked down by Google at some point, and over the years, it’s definitely shifted in the locked-down direction.

    My current approach is to carry around a Linux laptop and try to shift my usage more towards using the Android phone as a tethering device for the laptop, to get Internet access everywhere. That’s not always reasonable — you need to sit down to use the laptop — but the only thing that the phone really has to be used for is dealing with text messages and calls. If you really wanted to do so, as long as the laptop was on, you could run SIP to get VoIP service off the Internet from a provider of that from the laptop over the phone’s data service, not even rely on the phone’s calling functionality. The laptop isn’t really set up to be able to idle at very low power the way a phone is, be able to wake up when a call comes in, though, so it’s not really appropriate for incoming calls.

    If I need to access something one-handed without sitting down, I can fall back to using the phone.

    And it does have some nice benefits, like having a real keyboard, a considerably more-powerful system, a much larger library of software, a better screen and speakers, a 3.5mm headphones jack (all those phone space constraints go away on a laptop!) and so forth. You can move the phone to somewhere where its radio has good reception and just have it relay to the laptop, which isn’t an option if you’re using the phone itself as the computing device.

    You can, though I don’t, even run Android software on the laptop via Waydroid.

    I don’t presently use it in this role, but there’s a software package, KDE Connect, that lets one interface a phone and a Linux desktop (well, laptop in this case), and do things like happily type away in text message conversations on the laptop, if one has the laptop up and running.

    I’m thinking that that approach also makes it easier to shift my use to a GNU/Linux phone down the line, since mostly, all I absolutely need from a GNU/Linux phone then is to act as a tethering device, handle phone calls and texts. It’s sorta the baby-steps way to move off Android, get my dependence down to the point where moving is no big deal.




  • tal@lemmy.todaytoTechnology@lemmy.worldOpen Source Blackout
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    2 days ago

    Just loss of access to Web sites alone is pretty problematic in 2025, not even getting to open source packages.

    If I lost access to Web search engines and Wikipedia, I’d lose a lot of important tools.

    Ironically, software might be one of the less-problematic areas, as I have (probably out of date) local git repositories of a lot of software. But I don’t have local Wikipedia or local documentatation on a host of things. Maybe in 2025, local LLMs could act as a limited stopgap for some Web searching stuff.