bnyro

joined 2 years ago
MODERATOR OF
[–] [email protected] 3 points 1 month ago

Server Adaptive Bitrate Streaming, see https://github.com/LuanRT/googlevideo/blob/main/src/core/ServerAbrStream.ts. It's a format Google developed to be used by YouTube internally, there's no other service that uses it and thus it's also not supported by any player libraries.

[–] [email protected] 2 points 2 years ago (1 children)

YouTube is facing issues at the moment, so just get a coffee and wait for some time.

[–] [email protected] 1 points 2 years ago (3 children)

Feed -> Subscriptions -> "+" icon at the top

[–] [email protected] 2 points 2 years ago

Press the three dot menu -> Settings -> Instances -> Select a different instance.

Which instance you choose is up to you, a list of them and their locations can be found at https://github.com/TeamPiped/Piped/wiki/Instances.

[–] [email protected] 1 points 2 years ago (1 children)

Even if an instance is responding quick for some time, it's not guaranteed it's also stable and has enough capacity to handle all the traffic.

[–] [email protected] 1 points 2 years ago (2 children)

That's not an issue an update would solve, I assume you're using the app with an account and the instance you use just has been down for some time?

[–] [email protected] 3 points 2 years ago (1 children)

There's also https://status.piped.video which allows you to view the uptimes of all public instances, and their might be added something like that to the instances api in the future too.

[–] [email protected] 2 points 2 years ago (1 children)

This has been fixed in https://github.com/libre-tube/LibreTube/pull/4736. (Not sure if you're the person that submitted the issue or someone else did.)

 

Hey everyone, I’m happy to share Lemoa with you - a Gtk client for the Lemmyverse. You can install it via Flathub, or if you don’t use Flatpak you can build it yourself - the instructions can be found in the README. Please keep in mind that the project is still in beta, if you come across bugs please feel free to open an issue at the GitHub repo.

[–] [email protected] 7 points 2 years ago

Yes, that's a dependency of the relm4 crate we're using, I haven't yet figured out if we can disable it. The app doesn't use any libadwaita component though.

[–] [email protected] 1 points 2 years ago

Requested here: https://programming.dev/post/320260. Please upvote it in order to become considered as a new community on programming.dev :)

[–] [email protected] 5 points 2 years ago (2 children)

Yes, I don't want to move the project to libadwaita either because I dislike its flat design and don't use the GNOME environment in general. And I love theming Gtk apps :)

[–] [email protected] 4 points 2 years ago (1 children)

Not yet, but it would indeed be a good idea :) I created a request for a community here: https://programming.dev/post/320260. Not exactly sure if that fits programming.dev, we'll see :)

 

Just a quick update on Lemoa (Gtk client for Lemmy), which I posted about a week ago. It can now be installed via Flathub and now supports the most important authentication features such as writing, editing, and voting posts and comments as well as viewing the notificaiton inbox and writing or reading private messages.

121
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]
 

Hello everyone, I recently started working on a Gtk client for Lemmy written in Rust, called Lemoa and the awesome Relm4 crate.

So far, it supports most of the basic things that do not require a login, like viewing trending posts, browsing communities, viewing profiles, etc... Login features are planned to become added within the next one or two weeks, so that Lemoa can be used as a replacement for the web UI on a desktop.

Screenshot of an example community page:

Id you want to feel free to already try it at "alpha stage" (installation instructions are in the Readme).

Feedback and any kind of contributions welcome!

PS: I'm sorry if that's the wrong place to post about it, I didn't know where else to.

view more: next ›