Every time there's hype and eyes, the stock gets blasted. Why would this time have been any different?
I expect it to blast off when we least expect it. The only out is more shorting for the shorties. Because if they actually buy the shares, the stock will blast to infinity.
Honestly, with all the fuckery going on, nothing has changed. Gamestop has got an "out" for when it does happen and if people blame them they can say they offered up shares.
The company is not going bankrupt any time soon, making the shorts even more fucked. The drs numbers haven't changed, only the percentage. Locking down the float was always an unobtainable dream, but worth a shot. And even then if you believe the DD there are so many shorts that the dilution is just a drop in the water.
Their cash on hand is now >40% of their market cap, making this the smartest investment from an objective and squeeze-less point of view. Add in the shorting and fuckery that still goes on to this day, I don't see a problem.
Momentum was probably still going to lose if they didn't dilute, considering this is one of the most, if not the most manipulated stock on the market.
When MOASS happens, it happens. All the rest is just noise.
Well that would do it. Thanks for pointing out!
It thankfully seems to have been fixed thanks to @[email protected]. Running analyze verbose; in postgres.
The pgautoupgrade was added for the new version because this deployment is an all-in-one solution for running lemmy. And upgrading the databases turned out to be quite the effort until some user pointed the maintainer towards pgautoupgrade here.
I tried running lemmy before I found out about this, but this just makes it so much more convenient to run.
Thanks. I ran it. Hopefully it'll make a difference.
Edit: It looks like this did the trick. I'll keep monitoring to see if it sticks. Thanks again!
I think so. I have lemmy and everything needed running through a single docker container using Lemmy-Easy-Deploy.
I added pg_stat_statements, and ran it. This was the result:
# SELECT count(*) FROM pg_stat_activity;
count
-------
11
(1 row)
ERROR: extension "pg_stats_statements" is not available
Even though it's added in the customPostgresql.conf
shared_preload_libraries = 'auto_explain,pg_stat_statements'
ERROR: extension "pg_stats_statements" is not available
Even though it's added in the customPostgresql.conf
shared_preload_libraries = 'auto_explain,pg_stat_statements'
I have. And I tried to tweak it with no avail. But it was working within acceptable levels before the update.
Not for your use case. Only for their own streaming service. I've never been served an ad. And I've been using it for over a decade.