Because they take skilled labor to use instead of being able to pour concrete into a mold. The last 5 decades have been a constant quest to find ways to cut skilled labor out of the economy.
$24/hour for how many man hours to lay actual brick wall and not just the brick facades in front of a stick wall that is so common now, and even that is giving way to brick veneer that is laid like tile over plywood.
@RupertvonRipp@NitroDubs@WashedOutGundamPilot@SpurgAnon I ended up at one of those 7/11 nock-off stores recently. I think they buy (or are given) expired stuffs for the store. The starburst was hard from at least a year's aging and have almost no flavor.
Every time I see "Paxlovid", I am reminded of the pasification drug fed into the air system in Serenity that made most people lie down and die and the rest turned in to homicidal reavers. That drug was named G-23 Paxilon Hydochloride.
I am having an issue attaching Soapbox to my own custom backend. When performing a login, I get three requests that Soapbox makes to the backend (/api/v1/apps, /oauth/token, /api/v1/accounts/verify_credentials). The last has the server providing this data:
But then, the login just sits there. I get no additional requests to the server and no modal error messagess and no errors on the dev console. I am pretty sure I'm not doing something correct, but I am getting no indication of what is wrong so I can correct it.
I installed using a modified version of step 5 on the page https://soapbox.pub/install/, My data is installed under assets/soapbox/, and assets appear to be loading mostly correctly (I have an outstanding bug where things load slowly)
C, enforced single-user, flat file database, asynchronous processing of inbox&outbox. I want the installation process to be as close as possible to: unzip, launch executable, answer prompts and then open browser.
After a week of development, and using existing code to get a head start, I have the beginnings of an ActivityPub server written. It currently does very little in the way of ActivityPub processing: there is an /inbox that dumps all requests to a queue for later processing (along with the information needed to validate the HTTP signature minis the public key), there is an /owner/actor and there is a very basic webfinger implementation.
This is enough to get the account viewable thru existing software (see @teknomunk), but not enough to actually interact with anyone. Implementing code to get incoming follow requests working is my next priority.
I'm already getting activities delivered (mastodon.social keeps wanting to Delete @bappity for some reason).
If this project doesn't stall, and enough projects I've started have stalled for me to hedge here, I expect to move to the new server when enough of the basic functionality is in place so that all my normal activities can be done without me switching accounts.
Self-taught and professional computer programmer. Self taught Japanese. Trained Electrical Engineer focused on digital chip design. Trained and former professional draftsman. Amateur gardener. Armchair chemist. I've melted and cast metal in my backyard.日本語勉強中。純血白人I don't support #CurrentThing. #PeakOiler #Prepper