“𝘞𝘦 𝘩𝘪𝘳𝘦𝘥 𝘢 𝘱𝘰𝘭𝘪𝘤𝘦𝘮𝘢𝘯 𝘢𝘯𝘥 𝘪𝘵’𝘴 𝘨𝘰𝘪𝘯𝘨 𝘳𝘦𝘢𝘭𝘭𝘺 𝘨𝘳𝘦𝘢𝘵.”
Has to be the dumbest Tweet in the universe when you consider around 80% of its customer base is Opensource folk who historically have been very uneasy with police forces around the world.
@dick_turpin Very much so. TBH their PR has been pretty prickly for a long time.
They seem to think giving customers no information and no detail over the supply chain issues is a virtue, rather than exceptionally frustrating.
It's just a bit sad that they are needlessly harming the good work they do do, for the lack of listening.
@dick_turpin It was a little tone deaf for sure. But I think their response to the criticism and their further doubling down on it was the bigger error.
"Dogpile"? Really? Way to fan the flames, @Raspberry_Pi
@bigcalm In general I'm not a fan of CSS frameworks which end up adding 300 classes to every element. Especially when you end up with things like: <table class="table"/>.
I've used http://getskeleton.com/ a couple of times and love it's simplicity.
Me, 20 years ago: "HTML is fine, with some light CSS. I don't need a bunch of JavaScript."
Me, 10 years ago: "Look at all the jQuery I pumped in this page! It's so sparkly! And Bootstrap makes it look great everywhere!"
Me, at present: "HTML is fine, with some light CSS. I don't need a bunch of JavaScript."
@bigcalm the middle?
@SimonB what needs?
@breinbaas yeh. I think 'to connect to' the words that do the heavy lifting.
I've always considered applications using the 'postgres' default database not to be best practice, especially when they are authing as the 'postgres' user.
Do other #postgresql people agree with that?
Last day (this Sunday) to submit your talk for FOSDEM PGDay and the PostgreSQL Devroom!
Please note that the event takes place in Brussels, no pre-recorded talks are considered at this point.
Hot take
Yes, plus also sentiments echoed in "Humans".
Hot take
Interesting point. Which could well hinge on the definition of 'use'.
This seems to usually be tested in court by how similar the outputs are to other existing works, often siding with the rights holders of the existing works.
I don't think that people will accept the view that a machine could be as 'lossy' as a human.
Hot take
Should the developer of the algorithm be considered to have a right to the resultant work?
Should the rights holders of the training data set be considered to have a right to the resultant work?
Or should the 'artist' who combined them and generated the work?
I don't think there is an easy answer here.
But I do think it's too simplistic to say that the licences of the works used to train the AI model can be ignored, which seems to be Github's current stance.
PostgreSQL, Linux, Java, and more. Lover of computers, electronics and Open Source. European. Lib Dem. Lead Technical Strategist nexteam.co.uk