They've been working on the redesign for awhile now, but the version everyone's used to (Teamspeak 3) still works perfectly fine. TS3 clients can connect to new Teamspeak servers, and new Teamspeak clients can connect to old teamspeak servers, just without the new features like screen share

My group still uses TS3 on a daily basis on a self hosted server

  • source
  • parent
  • context
  • [–] [S] 2 points 1 year ago

    That last part is a huge reason why I'm taking RSS more seriously. I don't want my information to be limited to what happens to get picked up by the news cycle or worse chosen by the algorithm. I'd much rather get the information from the source. So that definitely meets the criteria :D

  • source
  • parent
  • context
  • [–] [S] 1 point 1 year ago (1 child)

    Heyy I've been looking around at different android apps and I think I've also settled on "Read You." Thank you for the list, I haven't heard of lots of them like MariusHosting and they look interesting

    Which feeds do you watch for automation? I also like automating what I can lol

  • source
  • parent
  • context
  • I use Duplicati for my backups, and have backup retention set up like this:

    Save one backup each day for the past week, then save one each week for the past month, then save one each month for the past year.

    That way I have granual backups for anything recent, and the further back in the past you go the less frequent the backups are to save space

  • source
  • I still think material design 1 (which came out in 2014) is good, which focused on clarity with limited space. The problem started with material design 2 in 2018, which pushed for increased whitespace and homogeny in design. (And Microsoft's Metro... shudder)

    Material design 1 balanced clean and readable while maintaining depth (trying to emulate 3d space by "stacking cards of content" with shadows). But since most of MD1 was guidelines instead of, like, actual components developers could use, it was a double edged sword of forcing people to be a little creative in making their own UIs but cumbersome because you had to make it all yourself

    Material design 2 tried to "fix" this by making everything simpler and shipping a ton of premade components that developers could just slap together and call it a day. Good for speeding up development, unfortunate because everything now looks the same. It's also because of this that material design started to "break containment" and appear all over desktop applications/websites. It's never good when a mobile design language is applied to the larger desktop space

    That's why I really don't mind seeing material design 1 on either mobile or desktop, because it was designed to use space efficiently and interestingly. Material design 2 on the other hand favors whitespace and speed to the detriment of us all

  • source
  • parent
  • context
  • view more: ‹ prev next ›