diana_coman: http://logs.ossasepia.com/log/ossasepia/2020-04-09#1024066 - heh, for fun and all that, I saw both approaches taken to the extreme indeed ("all in db!!" "all on disk!!"); extremes are extremes after all.
ossabot: Logged on 2020-04-09 17:57:03 trinque: I worked for a guy once that very much did believe everything was better off living in the database, including all that.
diana_coman: http://logs.ossasepia.com/log/ossasepia/2020-04-09#1024061 - jfw, note that billymg brought up the things that are accessible/changeable currently via the UI, under Settings; and I went and looked there yesterday - there are things such as blog title, tagline, date and time format
ossabot: Logged on 2020-04-09 17:40:05 jfw: http://logs.ossasepia.com/log/ossasepia/2020-04-09#1023964 - this is true of course, "it's all just a bunch of ones and zeros anyway!" but I argue there is a meaningful distinction, similar to "code vs. data" even though code is a kind of data, and whether or not correctly realized as filesystem vs sql. Perhaps better put as presentation vs. content.
diana_coman: otoh looking at the current wp-config.php, it's short and sweet, with a bunch of configs for Wordpress to know where & what db it's meant to use; which yes, it's where it should be and fine as it is but I do NOT want to have in there now crammed all the obscurantist knobs from settings, no
diana_coman: jfw: in short, no, I am not pushing for some db-extremism, everything lives in the db, db config itself and circular definitions be damned; I am however pushing for keeping configs to a minimum, for moving indeed ALL content (that includes the blog title and the tagline(s), ffs!) and for NOT carrying blindly over "knobs and settings" just because "users are used to them".
diana_coman: for moving indeed ALL content to the DB*
diana_coman: (in principle I wouldn't even mind it all that much to move it instead all to the filesystem - the point is all in ONE place - but there are some advantages to choosing db over filesystem, at least currently so I'd stick with moving it all to the db)
feedbot: http://bvt-trace.net/2020/04/vsh-parts-67-handling-orphans-and-updated-keccak/ << bvt's backtrace -- v.sh parts 6&7: handling orphans and updated Keccak
feedbot: http://trilema.com/2020/erik-and-other-stories/ << Trilema -- Erik and other stories
diana_coman: sonofawitch is my experimental bot in ~140 lines of code total (and no shitty flasks and whatnots); I'll let it hang around to see how it behaves; feel free to poke it I guess.
diana_coman: (it shouldn't reply to any pokings)
trinque: interesting! diana_coman written in what?
diana_coman: trinque: gawk
trinque: sonofawitch indeed lol
diana_coman: runs on old 1.3 of centos 6 extraction
trinque: would be interested to see this wonder
trinque: what's opening sockets for it, netcat?
trinque: or can gawk do this itself?
diana_coman: trinque: https://www.gnu.org/software/gawk/manual/gawkinet/gawkinet.html#TCP-Connecting
diana_coman shall be back tomorrow
feedbot: http://trilema.com/2020/il-divo/ << Trilema -- Il Divo
feedbot: http://fixpoint.welshcomputing.com/2020/the-missing-adacore-public-download-index-vintage-2018-while-it-lasts/ << Fixpoint -- The missing Adacore public download index, vintage 2018, while it lasts
feedbot: http://trilema.com/2020/idiocracy-the-movie-or-marion-tenailleau-is-a-stupid-cunt/ << Trilema -- Idiocracy the movie, or Marion Tenailleau is a stupid cunt.