crtdaydreams[asciilifeform]: signpost: AT automagically updated :D, have been on and off
crtdaydreams[asciilifeform]: also; congratulations, a step closer to the superlative man!
crtdaydreams[asciilifeform]: http://logs.bitdash.io/asciilifeform/2022-11-29#1114240 << bizzare. message virtually non-existant on bitdash logs
bitbot[asciilifeform]: (asciilifeform) 2022-11-29 unpx: Looks like bitdash didn't catch up the logs... http://logs.nosuchlabs.com/log/asciilifeform/2022-11-25#1114231
dulapbot: (asciilifeform) 2022-11-25 unpx: To my peers, hoping they will read this message. http://paste.deedbot.org/?id=BX0- http://paste.deedbot.org/?id=ZDRx http://paste.deedbot.org/?id=QMkw
crtdaydreams[asciilifeform]: o/ hola unpx
crtdaydreams[asciilifeform]: guessed which one first try :D
awt[asciilifeform]: congrats signpost!
awt[asciilifeform]: phf sure. will post peering info soon.
asciilifeform: $ticker btc usd
busybot: Current BTC price in USD: $16871.2
phf[busybot]: in totally random projects, i got mp-wp working with sqlite
phf[asciilifeform]: well, "working". enough to do an install, click around dashboard, post an article, but lots of broken sql still
asciilifeform: phf: interesting ( asciilifeform did not know that sqlite were to this degree incompat. )
asciilifeform on the occasions where used it ( e.g. early phuctor ) was able to switch to postgres with minimal changes
phf[asciilifeform]: asciilifeform, sure, if all you do is selects and inserts. wp is full of custom mysql optimizations, hacks and functions
phf[asciilifeform]: you wouldn't be able to trivially get it working with postgresql, or rather it'll require about as much changes as i've done so far
asciilifeform believes
phf[asciilifeform]: some you might be able to solve by providing a function shim with postgresql, but not with sqlite, because the later doesn't support function definitions
asciilifeform was not among the folx fascinated with mpwp, as had own roughly equiv. (actually moar trimmed, killed errything to do with uploading/file management, as always did this over mc)
phf[asciilifeform]: e.g. mysql has YEAR(date) MONTH(date) etc. which is not in postgresql. similar can be accomplished with strftime('%Y',date) in sqlite. etc.
phf[asciilifeform]: asciilifeform, i don't think it's particularly important that it's mp-wp, i at some point did some work figuring out the diff against stock wp 2.7, and there's not much.
asciilifeform: right, mostly the cuts iirc
asciilifeform: (from asciilifeform's pov was a much less aggressive cut than ideal)
asciilifeform: there was 1 pheature, where correctly displays pgp sigs; welded it onto mine with no problems
phf[asciilifeform]: actually updating the code to php 82 or whatever i ran into pretty much every instance of mp code, because his shit always violates some restriction or another :>
asciilifeform: lol
asciilifeform is of the 'ideal amt of php is 0' school of thought, but doesn't expect to ever have time to recreate wp in cl or the like with own hands, so there it remains
phf[busybot]: oh, here's another mysql-ism, that's all over wp
phf[busybot]: if you do SELECT SQL_CALC_FOUND_ROWS ... LIMIT 10, you can then do SELECT FOUND_ROWS() and it'll tell you how many rows the first query had without the limit
phf[asciilifeform]: basically you can avoid the overhead of second call with count(*) or haven to reconstruct that query or whatever. naturally it's a pain to fix
phf[asciilifeform]: http://logs.bitdash.io/pest/2022-11-30#1017190 << it's about same level of trash as perl, python or javascript. i'm hacking it with intellij and php plugin and it's a very smooth experience. jump to definition, auto format, tons of refactoring features, etc.
bitbot[busybot]: Logged on 2022-11-30 13:53:05 asciilifeform[6]: is of the 'ideal amt of php is 0' school of thought, but doesn't expect to ever have time to recreate wp in cl or the like with own hands, so there it remains
asciilifeform not tried intellij php, but many yrs ago did time in a saltmine with their java editor, was a++
asciilifeform: iirc they also have python debugger
phf[asciilifeform]: hmm, and i lost a bunch of packets
asciilifeform: phf: loox like our peering not worx atm
crtdaydreams[busybot]: jonsykkel: "error: invalid speaker '' recieved from peer 'jonsykkel'"
jonsykkel[busybot]: yes i corupertd my db cuz runned out of space on vps
crtdaydreams[busybot]: oh rip
jonsykkel[busybot]: imo fixed now
crtdaydreams[busybot]: ye seems to be
jonsykkel[busybot]: nice
phf[busybot]: it is apparently possible to register php functions to as sqlite functions. e.g.
phf[busybot]: $db->createFunction('foo', function($s){return "i says, '$s'";});
phf[asciilifeform]: var_dump($db->querySingle("SELECT foo('hello, world')")); ⇒ string(22) "i says, 'hello, world'"
asciilifeform wonders how precisely that worx
phf[asciilifeform]: mp-wp has an amusingly large number of hardcoded branding e.g. http://btcbase.org/patches/mp-wp_remove-all-javascript/tree/mp-wp/wp-includes/general-template.php#L1710
phf[asciilifeform]: a special function to ensure you can brand any kind of content!
phf[asciilifeform]: http://logs.bitdash.io/pest/2022-11-30#1017211 << sqlite is a library that you load into process memory, that knows how to safely edit a shared binary blob. a registered function is essentially ffi from sql to hosting environment, be that python or php.
bitbot[asciilifeform]: Logged on 2022-11-30 21:14:01 asciilifeform[6]: wonders how precisely that worx
phf[asciilifeform]: i'm sure it's not cheap, on large sql queries it's essentially an equivalent of a map over rows, except you're mapping an ffi function, so all the relevant boxing/unboxing/boundaries crossing