Hacker Newsnew | past | comments | ask | show | jobs | submit | procaryote's commentslogin

FOI is for administrative documents to increase transparency in government. Detailed 3D scans a museum does for research or preservation isn't an administrative document.

If you want a 3d scan of these statues, there's a lot of them around in scannable places like parks etc. If you just want to win, you're wasting everyone's time for no good reason.


Have you ever read this? https://eur-lex.europa.eu/eli/dir/2019/1024/oj/eng

I hope La Quadrature and company appeal this refusal to the EU.

Also even without the context above, a museum preventing people from experiencing and studying items from its collection (since the point clouds were apparently ruled such) is enough of a grounds for activist action against them.


What is the source of your knowledge of French FOI law? Are you already familiar with this topic?

The museum's own internal request for clarification said they are administrative documents.

  ...According to the advice of February 7, 2019 issued by the Commission d'accès aux documents administratifs (CADA)1, engaged by you, the files in question would constitute communicable administrative documents, insofar as they are developed and held by the Rodin Museum as part of its public service mission. In addition, CADA rejected various arguments in favor of of their non-communicability2. It also indicates that these documents are reusable, including commercially, but that the museum can establish a pricing for the reuse of its three-dimensional scans.
Quoted from the 20190627 English version of the letter.

Re: "FOI is for":

From FREEDOM OF INFORMATION IN FRANCE, LAW AND PRACTICE, Dr. Yseult Marique (Essex/Speyer), Dr. Emmanuel Slautsky (Université libre de Bruxelles) https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3033917

Page 19: "Before 2005 the reuse for commercial purposes of documents disclosed under the FOIA was restricted. Since 2005 and the implementation of Directive 2003/98/EC a right to reuse public information contained in administrative documents for purposes other than those for which the documents were initially prepared or received by the authority has been established under the conditions currently set out in book III of the CRPA. This right to reuse is made more effective by the fact that, whenever public information is electronically disclosed, it must be disclosed in an open standard that can easily be reused and automatically processed. This is important as inadequate standards significantly limit the possibilities for reusing administrative documents … The reuse of public information is normally free of charge. This principle is one of the main measures adopted in recent years in France to encourage the reuse of public information as part of the French policy of open data within the public sector. Public bodies are therefore compelled to allow economic operators to reuse valuable data generated in the public sector freely."

Page 39: "The FOIA has failed to trigger a revolution in how citizens request access to administrative documents. There is a fair number of requests. Sometimes these requests touch highly sensistive political matters (e.g. access to financial information related to President Sarkozy’s electoral campaing, Areva’s security failure etc.). However, all in all, the FOIA seems to be only used in marginal cases. The FDRA sought to bring a deep shake-up here. It sought to develop a stronger market logic with a clear demand-side and a clear offer-side to administrative data and documents. The pioneering idea that France seeks to put forward is that administrative information is economically valuable and that putting this information on the web will spur actors to use it, analyse it, dig into databases and eventually make valuable use of this newly acquired knowledge (i.e. because of economic uses or thanks to calling public bodies into account)."


Absolutely. An “activist” wasting time and money of museums (and probably taxpayers) worldwide due to a misleading interpretation of FOI.

It sounds like they are ready to give up human readability of code for a mostly untested idea macros _might_ help LLMs?

It's certainly the weakest argument I have seen today


Why enforce effort rather than outcome? Just have exams be without phones.

If someone manages to learn without doing the homework, or finds some way to learn better using an LLM, fine. The exam will show that.


Because we're afraid students might lack self control, or be unable to evaluate how well they absorbed the material.

Failing people who didn't learn anything during the course sounds like a desirable outcome

Given the education literally does not matter anymore for white collar work, I'm inclined to agree with you.

I'd rather a MUCH larger amount of professors and teachers come to class to find their classes deserted (by their own hand), and indeed, their own justification for existing gone. The world would be a lot better off. Gatekeepers are anti-human.


If education doesn't matter, you've had the wrong education.

Perhaps let them take a practice exam early on, so they can realise they'll fail the real one unless they actually study?

Education isn't a zero sum game. It's highly possible for people to do worse on basic skills without that being compensated by new unknown skills.

Hoping they're smarter than the tests show is a bad strategy for fixing the issue


so your take on declining test scores is that it means people are learning more?

No. My take is that test scores are a lousy measure of education. Maybe students are indeed learning less, and that would be worrying, but while we measure that using test score we simply cannot control for test taking ability.

what would be a better repeatable measure of education?

I am not a teacher, nor even an expert in the pedagogical sciences, as a layperson I can point out what looks wrong, but I need not know what is better.

Maybe asking teachers is better. Maybe a robust metric across generations and across population simply does not exist, and cannot exist, and we just have to accept that we cannot compare the education of kids in America today with the education of kids in Guatemala a decade ago.


It sounds like the title should be "the potential of audio AR", as nothing has really risen yet, and hasn't in the two years since the article was written

This is highly optional. You can lock phones up at the start of the school day or at the start of class

But you may be still trying to teach kids that are going through a form of withdrawal for several hours because it's not managed outside school.

If it's every lesson, every weekday, they'll get used to it

How do you take the phone from a child refusing to give it up? (It Needs parent buy-in, which is not guaranteed)

>How do you take the phone from a child refusing to give it up? (It Needs parent buy-in, which is not guaranteed)

It's not just a good idea. It's the law[0].

[0] https://www.governor.ny.gov/eliminating-distractions-new-yor...


My sons' school makes it a requirement of continued enrolment.

I've generally started to treat use of SELECT DISTINCT as a warning flag, as it's very common that it indicates bad code

Some use it because they don't understand uniqueness constraints and try to fix it in post so to say. Some use it because they forgot a join condition and are absolute amateurs. Some use it because it fixed a problem for them once and now they add it everywhere

These people seem to outnumber the people who use SELECT DISTINCT in a well thought out manner


This. 100%. So on point.

I'd only add one more observation.

Sometimes the root cause is poor table design (or in analytic/OLAP use cases poor ETL design without proper data validation checks or handling) where uniqueness is not enforced and that is the root cause that should be fixed if at all possible. A "first normal form" violation in the database design so to speak.

If that root cause is not addressed, then SELECT DISTINCT is more often necessary and the SELECT DISTINCT disease to be safe culture and behavior in the code base on top of the database just spreads.


Yeah, people have been advising against DISTINCT for ages. I guess that piece of common wisdom somehow got lost in this age of AI wonders. :D

Yeah, it's almost always more intention-revealing to use CTEs and WHERE EXISTS.

It's definitely a warning flag if you're applying it to full-ish rows. This situation seems much more innocuous to me.

Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: