That or debug was my guess
@antranigv @dvl ok.. what does -D do?
@j @phen314 To note at least in my case the instance was primarily slow because of the concurrent number of connections; it wasn't CPU or IO or database constrained,I used up the max number of sockets allocated to the service and things had to wait in line behind slow connections; had I configured the proxy with a larger inbound connection pool I may have been fine; but that just potentially opens me up to a different kind of DDoS 🤷
If it happens more frequently I will try to tune it better.
@phen314 Could I get some more context here?
@stefano I *want* to say that didn't exist when I set up my instance in ~april 2017. I WANT to say that, because I remember looking VERY hard for that... but I see that document was created in ~may 2017, with the pull request on april 24, 2016 (about a week after I sett things up).. so it probably DID exist... but at least the PR says it was "poorly documented"
Oh well, as a single user instance, maybe I just nuke myself back to nothing
@stefano
"As with LOCAL_DOMAIN, WEB_DOMAIN cannot be safely changed once set, as this will confuse remote servers that know of your previous settings and may break communication with them or make it unreliable. As the issues lie with remote servers’ understanding of your accounts, re-installing Mastodon from scratch will not fix the issue. Therefore, please be extremely cautious when setting up LOCAL_DOMAIN and WEB_DOMAIN."
Well, 💩
@stefano Hey. I have a question for you, your mastodon address is '@bsd.cafe' yet your mastodon service instance is mastodon.bsd.cafe. How did you do that? I wanted to do that for my domain, but I couldn't (at the time)
@a2_4am That is pretty deliciously evil and clever at the same time
@scanlime this game was so amazing and wonderful. It is really shocking and sad there isn’t anything like it.
I don’t mean like the java port, but i mean brand new games like it in the genre.
Just built FreeBSD 14.1-STABLE. First thing I tested was my USB earbuds. Plugging in changes hw.snd.default_auto from 1 to 0. Audio works - tested with spotifyd and Firefox/Youtube. Unplugging the earbuds results in hw.snd.default_auto going back to 1, and audio is then coming from my laptop's speakers - as you'd expect. And if I plug them back in, the audio is back in my earbuds, even in Firefox/Youtube - this definitely did not work before!
So, maybe a small step for mankind, but a giant leap for audio-related usability on desktop FreeBSD.
Thank you, @FreeBSDFoundation for sponsoring the work on the audio stack! https://www.freebsd.org/status/report-2024-01-2024-03/#_audio_stack_improvements
(I don't know if it was this work or something else that did the trick, but still!)
@emaste all diffs now updated -U99999 :)
@emaste the other 2 are:
https://reviews.freebsd.org/D45056 (this one actually has some movement)
and:
https://reviews.freebsd.org/D41509
(this one moved, and then stalled, imp was looking at it and then not it seems)
@emaste It is one logical change; it is allowing NSCD to respond to getgrouplist(3). but that is an entirely different 'kind' of call (the way NSCD is structured is around 'database' and 'key' and 'method'. So if you have database 'group' and key 'name' and method 'name lookup', well, that is 'get group entry by name'. In this case the 'name' isn't the group name, it is a user name, and the response isn't a group entry, but a list of groups.
@emaste since you're doing patches...
https://reviews.freebsd.org/D38047
😃
I've got 3 in total that I am trying to get in in time for 14.1 . 2 of which have been open for > 6 months
@matuzalem ah, excellent, and I see my current one there even!
FreeBSD enthusiast and regular contributor. I have opinions!