• 4 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle




  • Having the flexible screen facing externally on one fold seems quite reckless considering how fragile they still are by virtue of needing to be flexible. Having a Fold 4, the screen definitely relies on the thin film screen protector that the flexible screens come with. But because the screen is contained internally, it’s protected by the device.

    Having it unprotected means any drops on a surface that is able to hit the screen directly will most likely lead to cracks in the LED layer and kill the screen. And the geometry of the folded part would imply that any impacts will most certainly lead to cracks. You can test this by folding a piece of paper in a similar manner and then hitting the folded part. It’ll make tiny very sharp creases in the paper, and these creases are what kills the screen.

















  • From a technical standpoint, I can’t see media-heavy social media in the format of Facebook lasting too long in a federated environment considering the costs involved to maintain the server instance. Trying to do that while being free is absolutely unsustainable. Another shift in resource management would have to happen before platforms like that would be inexpensive and scalable.

    Currently, Lemmy instances are slowly and steadily growing with each user interaction within, and between instances. Most shared content is link aggregation meaning minimal server resources. But resource usage goes up much faster when images, or even videos are uploaded to be shared. This format will only grow more expensive over time, and definitely won’t last in the current format.




  • Oh hey you added in the comment stuff! It’s great for an initial release, though it definitely does need some refinement to be easily useable.

    • Comment feature buttons
      • They mostly work well, and look great! But tapping a comment does push the entire comment down as the buttons on top appear. Versus the ideal behavior of the comment position remaining absolute, and the buttons appear relative to it
      • Also, on narrow screens, the Next button does get pushed off a little bit
    • Done
      • Functions as expected, hides the extra buttons from the active comment
    • Hide
      • Correctly hides the comment when tapped
    • Show
      • This shouldn’t need to exist, as tapping on a hidden comment should automatically show it
    • Prev
      • Correctly activates the previous top comment, and shows the selected comment features. UI moves the selected comment just off-screen, so you have to scroll down some more to see it, even if it was already on-screen
    • Next
      • Same issues as the Prev button, comment selection is correct, but off-screen