Notices by keithzg (keithzg@fediverse.keithzg.ca)
-
keithzg (keithzg@fediverse.keithzg.ca)'s status on Wednesday, 19-Jul-2023 06:59:27 JST 
keithzg
@coolboymew @freezenet Eh, I wish I could be that optimistic. Barring a radical change in political power in this country I would assume like previous shakeups of the media industry it will largely just mean more consolidation and costcutting while independent outlets continue to dwindle. People know they can go to ctv.ca, they don't know they can go to thenarwhal.ca, so the big outlets (alongside getting government subsidies) can still get traffic while without visibility on mainstream social media and related services the smaller ones which have appeared over the past years will have an even harder time getting noticed by the public. That's my much more pessimistic guess, at least. -
keithzg (keithzg@fediverse.keithzg.ca)'s status on Wednesday, 19-Jul-2023 06:31:06 JST
keithzg
@freezenet @coolboymew And here in Canada I'm sure the big players like Postmedia and Bell will get big handouts in return, with no stipulations like "and use that to actually pay people" so they'll just continue to cut coverage, especially local news and investigative journalism, anyways. Mind you all that has been and would happen without this bill or any reaction from Facebook and Google anyways. -
keithzg (keithzg@fediverse.keithzg.ca)'s status on Wednesday, 05-Jul-2023 06:26:20 JST
keithzg
@gourd @aral I have seen that take but I don't necessarily see hard evidence that's the case. One notable bit that doesn't line up is that they *are* launching in the UK, where theoretically the GDPR got folded into national laws. If they're unable to launch in the EU but are able to in the UK, that would then under this theory have to rely on some divergence in the UK fork of the GDPR. Maybe there is one, I can't say I know, but I haven't seen anyone propose what that might be. -
keithzg (keithzg@fediverse.keithzg.ca)'s status on Thursday, 23-Feb-2023 11:33:24 JST
keithzg
@lain @feld I don't thiiink so, I swear I've checked that at times when I've been getting the hard failure and when there's soft failures where some requests fail and I see popups in the web interface along the lines of
> Error fetching timeline: Unexpected token '<', "<html> <h"... is not valid JSON
That being said, in the logs for the Pleroma service itself I do at times see:
> (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2999ms. This means requests are coming in and your connection pool cannot serve them fast enough.
So maybe that's indeed the problem. Although it certainly wasn't a problem *before* I upgraded, and it immediately started happening after I did. -
keithzg (keithzg@fediverse.keithzg.ca)'s status on Thursday, 23-Feb-2023 11:33:23 JST
keithzg
@lain @feld Unfortunately I can't give a very specific version where this might have been introduced, if indeed it's actually a bug, because I was upgrading from a very old version (mid-2019). -
keithzg (keithzg@fediverse.keithzg.ca)'s status on Thursday, 23-Feb-2023 11:33:22 JST
keithzg
@feld @lain At this point I think I can confirm that RAM was the issue, as I have not seen this recur since I bumped the VM up to 2GB from 1GB.
This does make my leading theory (though not with anything approaching absolute certainty) that the current version of #Pleroma is more demanding in this regard than the ancient version I was on, because this certainly never was an issue before my upgrade.
It's possible that increased Fediverse traffic is to blame instead, but it was several months into this latest surge that I performed this upgrade, so the second-place suspect for me is just Ubuntu itself. I upgraded to Ubuntu Server 22.04 before upgrading Pleroma and didn't observe any problems until the Pleroma upgrade (at which point they started occurring within the hour at the time), but that could certainly have been just a(n un)lucky coincidence. -
keithzg (keithzg@fediverse.keithzg.ca)'s status on Saturday, 04-Feb-2023 22:20:56 JST
keithzg
I haven't had the time or effort to figure out why my #Pleroma instance keeps dying entirely periodically, or why no services being restarted can resurrect it, only rebooting the entire server works. But I've now "solved" the problem . . . I have an hourly cron job that reboots the server if it gets a 502 status. This is a truly insane solution that would not be acceptable if anyone else was using my site, but I find this acceptable personally ;)
If anyone has any ideas on how to fix this in a more *proper* manner, I'm all ears . . . -
keithzg (keithzg@fediverse.keithzg.ca)'s status on Saturday, 04-Feb-2023 22:20:46 JST
keithzg
@feld @lain OTP release, Ubuntu 22.04 server running on a DigitalOcean droplet with 1GB of RAM. It's especially baffling to me that I continue to get 502 errors even after I restart both the Pleroma service and nginx!
All ０７６萌ＳＮＳ content and data are available under the