Is this now effectively Abandonware?

[johnjjgraham]

There are so many issues plaguing YTC that are not getting fixed that by this point it seems like the project has been abandoned. It's gone from being updated almost daily to not at all. What's going on?

Half the time YTC doesn't even load anymore.

[Pontiac76]

It works fine. Use the developer version.

https://github.com/YePpHa/YouTubeCenter/wiki/Developer-Version

On Mon, Aug 10, 2015 at 5:18 AM, johnjjgraham notifications@github.com wrote:

There are so many issues plaguing YTC that are not getting fixed that by this point it seems like the project has been abandoned. It's gone from being updated almost daily to not at all. What's going on?

Half the time YTC doesn't even load anymore.

— Reply to this email directly or view it on GitHub https://github.com/YePpHa/YouTubeCenter/issues/1999.

[johnjjgraham]

I am. Works 50% of the time. Else it's just loads the non YTC Youtube page. And annotations never turn off, even when i've turned them off in YTC and in Youtube options.

[Nuriell]

YouTube got another restyling breaking some things, like now the Auto-Hide Bar Option will not work, the bars always disappear. But i think is hard too keep up with all those useless stylistical changes.

[Eisys]

It's really sad.. I absolutely love this addon. It still works fine for me though, thank god. Wish someone would take over and update it more often.

[eversins]

Dev build does not work properly on chrome, people are having lockups between 4-10 seconds when they visit youtube.

[Eisys]

That happens to me but it's been happening for a long time and Im used to it.

[ghost]

The thing is, Youtube has changed things almost weekly. More often than ever before.

[johnjjgraham]

Pass the torch to someone who cares about the project

[Jaitsu]

John - if you care so much about the project, then kindly go learn Javascript and fork this repository rather than insinuating that the developer doesn't care, especially when he's submitted code two days ago (the same day this issue was submitted). It's tough to keep up with a website that changes its code backend on a weekly basis with no warning and support 5 browsers, and fixing bugs isn't as simple as having a developer flip a switch.

[foss-]

ireun, can you close this issue? It's not a bug per se, it's a rather random rambling contributing not too much cluttering the issue section.

As Jaitsu pointed out: if something is not working in the open source world, contribute code or visit https://freedomsponsors.org/ to raise incentives to get a specific problem you are seeing fixed faster. End of story.

[meldroc]

I just got a new update today - seems to be running more smoothly now. Thank you, developers!

[SuperSajuuk]

Abandonware is a program that has to have had no support for several years and the developer no longer making contributions. While the contributions to the repository are very sparse, this isn't abandonware. But I agree with the sentiments of the OP: there are too many broken aspects of the script for it to be of much use. I just removed it since it was wasting memory and freezing constantly, doing me no favours at all: the only thing I had it for was the auto-expanding description.

If someone could possibly pull this feature out of the script and make it separate, I'd appreciate it: I know absolutely nothing about the JS used in this script, so cannot do it myself (so please don't even bother to post a reply to this if your suggestion is to "do it yourself").

[rdamiano]

Not sure which browser OP is talking about, but for Firefox users this add-on is and has been useless for the past few months.

Sure, it works, but give it a few minutes (and all of your memory) and it will become unresponsive and laggy. This issue has been known for months #1875, but has either been ignored or unnoticed by the developers.

Sadly, I'd call this abandonware, as the minor "superficial" updates that seem to occur every other week isn't fixing any of these types of major problems.

[Pontiac76]

I'm ONLY a FireFox user and use this script DAILY for a LOT of YT videos and I've NEVER experienced lag, memory issues, or anything of the sort. At all, ever. My browser stays up constantly on one of my monitors while I watch any number of videos a day. I also run a very clean browser with no fluff or addons or anything beyond this script.

If you're going to complain about software provided to you for free, with no contribution from yourself other than to complain and whine about it, then go get another tool to do what you need to do, or, pick up a Javascript book and write your own. Get this debate about whether this is abandonware or not out of tracker. It isn't wanted or needed.

On Sun, Aug 16, 2015 at 4:46 PM, Ralph notifications@github.com wrote:

Not sure which browser OP is talking about, but for Firefox users this add-on is and has been useless for the past few months.

Sure, it works, but give it a few minutes (and all of your memory) and it will become unresponsive and laggy. This issue has been known for months

1875 https://github.com/YePpHa/YouTubeCenter/issues/1875, but has

either been ignored or unnoticed by the developers.

Sadly, I'd call this abandonware, as the minor "superficial" updates that seem to occur every other week isn't fixing any of these types of major problems.

— Reply to this email directly or view it on GitHub https://github.com/YePpHa/YouTubeCenter/issues/1999#issuecomment-131619643 .

[rdamiano]

@Pontiac76 Not whining, stating facts. That's great that it works for you, but for many others that is not the case - I've even used a new FF profile to attempt to debug it, same issues. I have my own projects I take care of with my own sets of bugs and issues, no time to manage this one. Just trying to bring to attention a very critical bug to the developers that I haven't seen them even acknowledge.

[keLston]

@Pontiac76 Feel free to provide proof. Multiple users have submitted this issue on Reddit, on Firefox official forums, on Firefox bugtracker, and on this addon's github tracing the memory leak to this specific addon.

You are the sole user indicating that there is absolutely no memory leak issue with this addon and Firefox. Using Firefox 40.0.2 with standard addons (Noscript, Adblock, Ghostery) and some non specific addons still allows my Firefox to run under 350MB. I can even spam 10 Youtube videos concurrently using a different Youtube addon and only get up to 1GB usage for Firefox but Firefox will release that memory as soon as I close those tabs. But as soon as I install this script, all it takes is opening two videos to get memory usage ballooning to over 850MB and gets worse quickly. Firefox will NEVER release that memory with this script running.

Prove your claim.

I can prove mine. Since at least June 2015 - http://i.imgur.com/gDC2kQ7.jpg

Put up or shut up. Calling you out.

[Eisys]

Guys, guys.. Just use Youtube+ https://github.com/ParticleCore/Particle/wiki

[RohithKumarSp]

@eisys there's so much missing from that. and the video doesnt play if both extensions are enabled.

[Lucatir]

Please open a new ticket per issue or search if a issue report already exists and refrain from creating new tickets complaining about lack of updates. You can also check the link @Eisys posted.

Thanks for understanding.

[Pontiac76]

@Kelston If you wanna call me out, cool.

https://youtu.be/yko-Tfgu6O0

On Thu, Aug 27, 2015 at 4:54 PM, ErdeFB notifications@github.com wrote:

Closed #1999 https://github.com/YePpHa/YouTubeCenter/issues/1999.

— Reply to this email directly or view it on GitHub https://github.com/YePpHa/YouTubeCenter/issues/1999#event-394456785.

[rdamiano]

Gonna pop in and just say that back when I still used Youtube Center (2 months ago) with this FF bug, the lag/unresponsiveness would get worse over time (minutes) which I'm assuming corresponds to the memory leaking and amounting up. However, closing the Youtube tabs/windows would remedy the situation. Since the issue ticket is still live, I'll assume the bug still exists.

[vico93]

"Since the issue ticket is still live" @ErdeFB closed this

[rdamiano]

@vpontin The issue we're talking about is #1875

[vico93]

So go there and comment, this issue are closed. Simply

[rdamiano]

@vpontin Same to you.