taizou @lion@computerfairi.es
Joined Jun 2017
@RavenWorks .. and I fixed it anyway
thanks for spotting that
@RavenWorks yknow what I think those have been broken for two years lol
the white page is saved in the wayback machine going back to 2021 https://web.archive.org/web/20211201052225/http://blog.12bit.club/?date=2014-02
@RavenWorks thanks. they sure are. hmm it's giving a 500 but not logging any errors which is annoying
restarted the container today & it came up on a different subnet so all my mysql config stopped working lollll
apparently you can configure it to use a specific subnet in docker compose, so, I did that, and now it works again
i've switched over the public version of that site to use it now, so if you want to poke around https://blog.12bit.club/ and see if anything looks broken then feel free
taizou
boosted
and this is a version of my blog now running through php-fpm in docker!! it seems to work perfectly, loads just as fast as the old version
i'm not switching over to this for the public ver yet in case i find some problems but this is very very promising
for once i can go to bed on a high note instead of an "ugh fuck this" note
so I got the bastard working!!!!!!!!
I think my main misconception was that the docker internal host thing was like, magically mapping things to appear to connect from localhost on the host so I wouldn't have to do anything special to allow them to connect
but that's not the case, the container connects from its own IP address so I had to allow that through the firewall & allow mysql users to connect from it
@Ninji Yeah I did indeed have to do that
and it works!!!!!!! thanks for your help
@Ninji that did work yeah - but I also realised i need to actually let the container connect through the firewall & I'm getting somewhere now 
like i'm now at the point of getting normal mysql access denied errors, i can work with this
@Ninji no, how do I find that out
@Ninji nah i'm not running mysql through docker at all, it's just an existing setup on the host machine, i'm trying to connect to that from inside the container
I still can't resolve this mysql issue though. So like for background I have extra_hosts: - "host.docker.internal:host-gateway"
configured in my docker-compose file & that's supposed to map the host machine's internal network to the hostname docker.internal.host inside the container
And that works, for some things, e.g. I can ping it, I can connect to its web server port. But not for mysql! It just times out! I don't know how to debug this!!!!
This seems bad??!?!? I very nearly misconfigured my container in a way that would have accidentally left a port exposed, but I thought "oh well it wouldn't have been _too_ bad cos the firewall would block it anyway", but apparently, no, docker just says Fuck your firewall
so...i got docker installed on the server... got my container up and running... web server pointed at it... all that worked fine
the new and cool problem i now face is that it's unable to connect to the mysql server on the host, despite this working fine for me locally. it doesn't even fail in a useful way either, it just times out. if i ping the hostname that's supposed to map to the host's internal network, it responds fine. but doesn't respond for mysql
going to fucking bed again
Realised why that was happening, the table dump actually had TABLESPACE `innodb_system` in it, which caused the reimported table to always go in the massive ibdata file. Have converted everything to file per table properly now. But that was still kind of a futile exercise considering theres still no way to shrink ibdata without dumping, deleting and recreating all the databases. And I'm just not gonna do that until I fucking need to because I have plenty of space for docker atm
taizou
boosted
game genie 2, prototype, 'developed for the snes, it allowed users to find their own cheat codes, to activate cheats during gameplay, switch to slow-motion & automatically save/restore high-scores into battery-backed memory on the device. a prototype was completed, but not released. only one exists, owned by richard aplin, one of its original creators' https://en.wikipedia.org/wiki/Game_Genie
taizou
boosted
I so, so, so don't want to drive any new car that can do this:
A federal appeals court refused to bring back a class action lawsuit alleging four auto manufacturers had violated Washington state’s privacy laws by using vehicles’ on-board infotainment systems to record and intercept customers’ private text messages and mobile phone call logs.
The court ruled that the practice does not meet the threshold for an illegal privacy violation under state law, handing a big win to automakers Honda, Toyota, Volkswagen and General Motors, which are defendants in five related class action suits focused on the issue.
The plaintiffs had appealed a prior judge’s dismissal. But the appeals court ruled Tuesday that the interception and recording of mobile phone activity did not meet the Washington Privacy Act’s standard that a plaintiff must prove that “his or her business, his or her person, or his or her reputation” has been threatened.
A suit filed against Honda in 2021, argu[ed] that beginning in at least 2014 infotainment systems in the company’s vehicles began downloading and storing a copy of all text messages on smartphones when they were connected to the system.
An Annapolis, Maryland-based company, Berla Corporation, provides the technology to some car manufacturers but does not offer it to the general public, the lawsuit said. Once messages are downloaded, Berla’s software makes it impossible for vehicle owners to access their communications and call logs but does provide law enforcement with access, the lawsuit said.
Many car manufacturers are selling car owners’ data to advertisers as a revenue boosting tactic, according to earlier reporting by Recorded Future News. Automakers are exponentially increasing the number of sensors they place in their cars every year with little regulation of the practice.
https://therecord.media/class-action-lawsuit-cars-text-messages-privacy
Joined Jun 2017
