A) TW Blue started as a clone of CN, actually.
B) it has huuuuuuge memory management issues (over 2 GB on a good day for me).
And C) try opening a huuuuuuge conversation. It will freeze literally everything but WX, because WX forces it's own thread down their throat.
I certainly see why people aren't that willing to fork over money, and it's actually quite understandable. But TW is not better in compareson imo.
#26 (edited by Turret 2021-01-13 16:12:27)
A) TW Blue started as a clone of CN, actually.
Actually TW Blue is a fork of the qube, which is a fork of qwitter. Chicken Nugget most likely uses adapted qwitter code, which may or may not even be legal under the terms of the GPL come to think about it due to the thing's closed source and proprietary nature, but no one can prove it.
#28 (edited by Minionslayer 2021-01-13 17:12:45)
Why the hell can't I bind a key to something including space or enter?
Edit: And not even the function keys work?!
Edit 2: I also don't like thus far that no Twitter client has shown DM by user, not just by one buffer for received, one for sent.
Edit 3: My mistake. You can actually do those things, you just need to type out eh key for some reason.
Edit 4: Okay it's fine, but $15?
@27: if you want to get into illegally used code, I don't think TW Blue is the hill to do that on. It uses NVDA's language handler, with all copyrights removed, and slight modifications. See languageHandler.py
@28: because he is literally giving you access to paid OCR and image description services.
Every Twitter client will have the buffer lag bullshit until the new streaming endpoints for api v2 are ready. AT this point, version 4 of Tweepy will enable use of those new endpoints.
Incidentally, TW Blue has already begun the migration to Tweepy about a week ago. I sure hope Q has done the same thing for Chicken Nugget. It looks like he has, considering it's back to using oAuth which was shut down along with streaming 2 years ago. Better still, if CN is still using Twython, that would be laughable. Twython might be the reason TW Blue has the memory issues and instability that it does. Python3 made it a lot better, but it still has threading/conversation issues.
I didn't read the entire topic, but does this use the new API? Is the streaming back?
“Please don't be dead. Because then I'd have to be the Sorcerer Supreme and there's no way I could rock the 'stache.” Peter Parker in New Avengers Volume 3
It does use the new API AFAIK, as otherwise it wouldn't work. And no, I think Twitter nuked streaming for good.
Not really. Streaming is supposed to be back with api v2. Tweepy just hasn't been updated to enable the new endpoints yet. You can tell it's not entirely v2 ready because of the holes that weren't in previous iterations of Nugget.
#34 (edited by haily_merry 2021-01-13 17:55:06)
@turret, no no, I was talking about chicken nugget being as it's A, close sourced, and B, proprietary, both going very much against the GPL which original qwitter was released under.
@34: where is your source on it using Quitter source though? Just because it took the idea doesn't mean it used code.
Like I said, it’s kind of hard to prove unless you have a copy of qwitters original source code, which I don’t, because it’s no longer on github, and you’d probably have to know the original code base quite well in order to notice anything anyway. It is the same developer though, and they’re similar enough to at least be suspicious.
@29, so, paying 15 $ for a streaming service that google can do for free? no thanks. You can open images in your browser and let google identify them. Not paying 15 bucks for image description when I can get it for free. Also TWBlue has the same features as CN as far as I can see.
Correction, it never was on github. He hosted it with, something. I don’t even remember what it was called, but some sort of database system. If you go to the wayback machine, they have some interesting archives for qwitter-client.net.
@marro, Yeah not the same OCR and image services. Don't expect to see the same results.
I use the twitter websight it works fine for me
I don't think these clients have memory management issues in the conventional sense. As in, I believe it's quite intentionally consuming that much RAM to cache past tweets and avoid lag when trying to load them from disk when browsing.
Wake me up when the world has unfucked itself
Is time really linear?
You can find me on discord: ironcross#8090, though I don't know why you'd want to.
Yeah, CN will do the exact opposite, it will literally save your entire session to disk, barring timelines you don't flag as being persistent across restarts. Unless, of course, you configure it to write nothing to disk, in which case it won't.
The problems with this system are that A, assuming streaming ever becomes a thing, if you're following a lot of users, oof. That's gonna suck for your hard drive, and probably your CPU as well. Also it apparently lags at startup for some systems with a lot of tweets cashed, though I haven't experienced this yet myself.
My thoughts in four words: too little; too late.
Exactly. Although I wonder if this is an interim update while we wait for Tweepy to adopt the new api v2 endpoints. THis thing can't possibly be using Twython due to Twython's deprecation.
#45 (edited by Lucas1853 2021-01-13 22:11:14)
I saw that Q was back to Twitter a few weeks ago or whatever. It figures that as soon as he comes back to the platform, he'll update the client he made for it. I remember he ragequit not only CN development, but using Twitter as a whole when the API thing happened. Both TWBlue and CN will get streaming when it happens, so I see no need to switch.
CN saves to disk, but if you let it do that for about a year it starts randomly freezing, so if you're going to try it maybe don't use that feature.
Or at least clear the cue from time to time. IN fact, plan on clearing the cue after every update for a while, as version 4.71 fixes some miner but nagging issues with link rendeirng. HOwever, past tweets stored with older versions will still have this problem, thus clearing the cue is necessary.
And speaking of saving to disk, it appears tha tChicken Nugget does not yet have support for the new Twitter archive format.
dont think so
Neither do I.
YouTube: https://www.youtube.com/channel/UCwUsiu … hp6dQOqoXA
Sometimes I upload things in both platforms. And really, thumb me up!