Are there any Perl dists for Windows that I can actually just . . . like . . . install normally? Or can anyone explain to me how to install #ActiveState#Perl with this bizarre, seemingly git-backed setup they have which seems to just result in a folder empty other than a single .yaml file (and for which the uninstall command for the "state" utility I seem to be supposed to use just throws an error and gives up)?
The cli utility in question told me to use state learn to find out how to use it but that just takes me to https://platform.activestate.com/state-tool-cheat-sheet which seems to put me no closer to my goal of “just have Perl installed”
Abandoned ship, though I remain very very curious how this was considered reasonable by anyone. Though in fairness these days as soon as I see a .yaml file anywhere I tend to go “oh, shit, this is some software with insane build and usage nonsense that only corporate devs think is remotely acceptable”.
Conversely, #StrawberryPerl installed very easily and obviously, and all I needed to do was add its bin folder to my %PATH% et voila, it built the part of PostgreSQL I needed to build just fine.
Seems pretty silly the #PostgreSQL docs recommend, borderline insist, on using ActiveState Perl when Strawberry Perl provides #Perl in a far more “actually provides it to you” way :P
And yeah I certainly am not too worried, with how trivial of an effort it has been for me to spin up and maintain my own instance (and not even of Mastodon, yet seamlessly interoperating with Mastodon) I don't think we're in any danger of losing this social space outside of corporate ownership.
@clacke@gemlog Not to cheer for Meta but it sure makes a strong contrast that their offering has public web access (and link previews and whatnot) on day one while both Elon's Twitter and Jack's replacement Twitter currently don't. That alone makes me think Threads is indeed poised to replace Twitter in mainstream usage.
@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.
@mpjgregoire@gemlog On paper I wouldn't entirely disagree with you, though I personally think they should have aired it (and also share @gemlog's weariness with faked doc stuff), but all of that is beside the point in this exact conversation. My point is just that it's notably a concession according to some sources, and demonstrates an example of the political pressure the BBC is constantly under these days without it needing to be a formal order from government:
> Senior sources at the BBC told the Guardian that the decision not to show the sixth episode was made to fend off potential critique from the political right. This week the Telegraph newspaper attacked the BBC for creating the series and for taking funding from “two charities previously criticised for their political lobbying” – the WWF and RSPB.
@mpjgregoire@gemlog Oh it's definitely pure politics, even if merely mediated by the systems and procedures and culture put in place by (or simply distorted by the gravity of) a party or movement.
Pressure can be applied informally, or outright without explicit communication. A political appointee here, a firing there, or even just a promotion or two where the choice senda a clear message, and people will get the idea, and won't need written directives from the politicians or parties in question to know what they're expected to do in future scenarios and to feel the pressure to act accordingly. Particularly when it's in regards to an incident being very loudly and publicly litigated in the social and formal media!
@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.
@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).
@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.
@gemlog My hours are basically whenever I feel like they are; some days I legitimately forget to do any work; most technical decisions are within my remit so I rarely have to implement anyone else's bad ideas.
Alas, as a company that makes software to be run on Windows machines, using Visual Studio is not unreasonable, and all the developers are quite used to it; but when I had to make a GUI program from scratch myself a while back, I instead used Qt Creator, and the other main program we ship that I write and maintain is just a CLI program written in Python, so in neither case do I have to deal with much of Microsoft's crap!
That's pretty neat, albeit maybe only that useful when I foolishly forget that the switch for the `unzip` command to do the same is `-l`, but I do forget that embarrassingly oftenly. Ironically now I've probably tied the two together enough in my memory that I'll remember both every time this comes up, heh.
Embed this noticekeithzg (keithzg@fediverse.keithzg.ca)'s status on Saturday, 04-Feb-2023 22:21:28 JST
keithzgI 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 . . .