2mo ago

How do you feel about MS-DOS inspired UI for a Lemmy Client?

A open source monospace component library crafted for React interfaces built with variable fonts, React applications, and React websites that prioritize simplicity

Personally, it would be my favourite even if it were just a RSS feeder app where colours would only pour from media or link embeds but I can’t stop the idea of even having the messenger conform to this style where we replace emojis with Kaomojis even.

If it were me, I would also go as far as hiding a mini snake game as an easter egg ✌︎

20 comments

I would instantly put it as the default for my server
- Username checks out
  
  Bring it to !usernamechecksout@lemmy.zip

Eh, I think there's a need for appropriate technology here. Lemmy is inherently a multi-modal platform, with images, links, and text. I like the browser skins and apps that browse Lemmy.
As an educational project or simply for fun I say go for it.
- Yeah cool idea but for the less tech adept like myself I’d be scared off. Voyager is perfect for me.
  
  I am using Arctic (｡❛◡˂)✧

How about hackernews-inspired Lemmy client?

How does Lemmy render in w3m, lynx or links?
- Not well - at least in Lynx, content doesn't load at all. You basically get the sidebar.
  Piefed looks great though. Obviously not the feel of a native terminal app, but seemingly fully functional and everything makes sense.
  
  Interesting. I remember seeing a screenshot of someone browsing Lemmy on a terminal, not sure what they were using

I would also go as far as hiding a mini snake game as an easter egg
If you want some code for that I have my own C++ version I made for an ESP32 with OLED screen, it can easily be adapted to most other languages. I did it to get some programming practice. I have Tetris too. All you gotta do is replace the GPIO button inputs with keyboard inputs (or some other boolean on/off user input element) and replace the graphics framework and routines as well (it's only simple stuff like lines, boxes, and setting individual pixels). The whole thing runs in a "neverending" while loop, first checking inputs, then checking collisions, then redrawing any objects that need to move to another position.
I can upload to my GitHub and link them later after work. They do use OOP though, treating each sprite on the board as its own object, and feeding pointers to them into a collision detection routine every game tick. I dunno, some people have a visceral hate for OOP.