I’ve been using the iOS beta. I can’t speak to the Mac beta. For iOS, the execution needs work, but I think I actually agree with the sentiment that content should own the entire screen and the controls should float over the content. However, there are some serious readability concerns that they need to sort out. But think of Instagram from 5 years ago compared to TikTok. TikTok really demonstrated how the content should take over the screen, and now every major social media app has a TikTok style vertical feed that fills your entire screen. I don’t use TikTok, but I enjoy apps that let content take up the screen. Apple does things that are genuinely really frustrating like refusing to redesign the Magic Mouse or putting the power button on the bottom of the Mac Mini. But in this case, I think maybe we should let Apple Cook - pun intended - but push back on obvious flaws like readability.

What comes after new?

Now sports cars have paddle shifters so people can pretend to drive manual

alias nano=nvim

The command chest sheet in that article is wrong. gg is first line of the document, not H

I use neovim btw

Yeah! Whatever you feel most comfortable doing. I’m really hoping to get on the Play Store soon and be done with this nonsense. I’m actually brand new to Matrix, but you can just DM me right? I don’t need to do anything?
@moseschrute:matrix.org

Omg that’s so funny. There is no reason I can think of to collab but I kinda want to just based on the name

Totally, I respect your desire for privacy. Hoping to have Blorp on the Play Store soon and be done with this nonsense. They should also unlock open testing soon which means I won’t need to ask people for emails.

GitHub, Matric, DM honestly whatever is easiest for you. I’m happy to turn your messages into formal tickets. I really appreciate you taking the time to try my app!

Anything you’re willing to submit. Just say what you like and what you don’t like.

Out of curiositity what other backends were you hoping it supported? PieFed or Mbin?

I have actually never tried Mbin, but I was talking to the PieFed devs the other day. PieFed API isn’t even stable yet, and they emphasized that they want the flexibility to implement features independent of Lemmy. For that reason, I see their API as a moving target that will slowly drift away from Lemmy. They are differnt projects with different goals. I think I can ship a better product if I focus on doing one platform really well.

If you were talking about Mbin, I would be happy to do more reserach to determine if it’s a similar situation or not.

His neck line is so much funnier in a silhouette

Let’s just say hypothetically I vibe coded my vim config. Where would that put me?

How tf do you not support an operating system. Like you gotta go out of your way to detect and block the operating system. Like if you put in 0 effort it would probably work but your company really spent money making their product less accessible for no reason.

I like jakewvincent/mkdnflow.nvim for editing markdown, though tbh I’ve mostly just used it to check/uncheck todo lists.

To be fair, we should probably all start migrating to cybersecurity positions. They’ll need it when they discover how many vulnerabilities were created by all the non-programmers vibe coding.

I really think the issue would be load on server bandwidth (depending who’s hosting the image). 2mb is not good for client performance, but in the grand scheme of things it’s not that much data. Video streaming consumes so much more. I would like to see smaller images so clients can load a feed of images faster. It’s also annoying because Lemmy doesn’t always tell you the size of the images. So the height of posts will shift in your feed as images are loaded.

lemmy shouldn’t require posters to compress their own images. Compression should happen automatically. It will save both the severs and end users bandwidth

Wait, you’re telling me he was not the chief engineer of space x whole simultaneously being the world champion at a video game?

Not good enough. You should really be inspecting your CPU with a microscope.