Is the app still maintained (and working)? #12
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Foxite/YoutubeDL#12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
With no update for a couple of months, YT apps usually break at least partly due to changes on YT's side. This app has not seen updates for 2 years now, so I wonder if it's still maintained and working. Your Readme links to my repo, where the app still resides – but if it's no longer operational and/or maintained, I'd have to remove it.
So could you please give a short status? No offense meant, we all have our "real lives" intervening here and there. But I try to keep my repo in good order so it remains useful 😉 Thanks in advance!
Unfortunately it's not maintained and probably doesn't work anymore.
It's a xamarin app which can only be developed for on Windows for some reason, and since I switched to Linux as my daily driver I don't want to have development stuff on my windows install.
To anyone reading this: if you need an alternative to this app, I highly suggest NewPipe as it mostly replaces the stock youtube app (or vanced for that matter) and has much better download functionality built in.
You can probably close the request for packaging on the fdroid gitlab as I'm not planning to maintain this app, or remake it in Java.
If anyone wants to take ownership feel free to ask here.
Thanks @Foxite! I'll remove it from my repo then. I don't know if there's an open RFP at F-Droid for it, but let me check… Ah, there it is. OK, will close that along (done), thanks for the pointer!
I leave it to you to close this issue (as you included a call to "anyone reading this"). I guess the Readme is now clear enough on that (you could of course also include the NewPipe pointer there).