• 185 Posts
  • 131 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2024

help-circle
  • What about pedestrians trying to cross these streets you want to blaze along?

    Nothing changes for them. Pedestrians have the right of way on a crosswalk regardless of whether a signal is in play. It’s the cyclists responsibility to avoid the pedestrian which is generally a matter of cycling behind the pedestrian, sometimes slowing down a bit if needed.

    What about bicyclists who need to merge, or perhaps are not as fast as you?

    No need for stopping; just vary speed as needed.


  • Do you not yield to traffic in roundabouts??

    Depends on if the traffic is cars or cycles as far as whether yielding requires a stop. Cars move a lot of mass very fast so I must stop if timing forces me to. And that’s frequent. Roundabout traffic in the form of cycles does not require stopping. I’ve seen it 1st hand at Critical Mass events. You only need to vary your speed, unless the round about is so clusterfucked with bikes that you need to stop, which is rare and would never be a realistic scenario outside of Critical Mass. But if it were, I would argue that the civil engineers fucked up… that the roundabout is not proportioned for the capacity it needs to serve. Regardless, in the very worst of cases you never need to be stopped at a roundabout when there is no traffic. Stops also only last as long as necessary. They are not artificially imposed by the timing of a traffic light.











  • Someone would need to query the data and encode it to JSON/etc. on the fly. There may not be a way to do this without having one of the programmers directly connect to the DB and run custom queries.

    I use sqlite. They are probably using some heavier duty db but for sqlite exporting JSON is trivial so I would be surprised if other DBs did not have a similar mechanism. And to be clear, I said to the library that I prefer JSON but would handle whatever open format they prefer, be it XML or CSV.

    To dump everything blindly would be irresponsible. It’s possible the DB could lock up or that incorrect/inappropriate data could be queried.

    This does not sound like a realistic problem. I might imagine if they had a DB of all ISBNs, they would obviously have to use a query that limits to their catalog. Apart from that, I don’t see what would be inappropriate. If it’s in their catalog, why hide it? Not sure what you have in mind but I should say it’s not the US where there would be some right wing concern to prevent children from getting sex education type of material, or the Christian right trying to make Darwin’s theories hard to reach.

    If you are thinking in terms of sensitive info, like accounts of people and what they borrow, it would be irresponsible if that kind of info were not in a separate table.

    Their software is either homebrew or off the shelf. If it’s off the shelf, they may need to put in a support ticket and have their vendor figure it out. It’s highly unlikely there is a government employee or team sitting around and waiting for your request.

    I was expecting my request to be ignored, as open data requests often are – and rarely fufilled in my experience even when they answer. But in the case at hand, they first responded favorably, saying essentially: we can give you some data but your request is vague… what exactly do you want? I basically replied with “everything”. So they were not opposed to exporting some data, but the volume involved (100s of 1000s of records) seems to be a show-stopper.

    I believe that the library has a point about not performing this amount of work on an individual request.

    I might agree that it’s a bit much to serve one person. They also said it would take disproportionate resources when they have a whole public to serve. But I was figuring “build it, and they will come”. There would be a first person to make a request. I am a bit disappointed that if it were made available that we could not expect many people to exploit the option to be free from the UIs limitations.


  • You seem to be saying: find out what you want and ask the library for it. I tried that once. I asked for a particular book. The librarian basically said “nope, we don’t have it… but English bookstore X might have it”.

    Note that I am generally interested in English content in a non-English region. There are some English books and media for whatever reason (certainly with DVDs it’s because the original film is often in English) but asking them to procure something in English is probably a long shot… a bigger ask than asking them for a DB of what they have.

    So, to me it seems like the main reason you would want this list in the first place is not to waste time deciding on something only for it to not be at the library in the end.

    The point in doing an SQL intersection between a long list of some sort and their DB is to find what they already have that may be interesting. It’s not to discover what they don’t have.











  • I think it should be feasible, if you can reach them. I’m done with github, who forced 2FA on my acct via email confirmation before my email address died. I’m not going to dance for Microsoft in order to give my attention and interaction to MS users.

    In principle, I think if someone were to set up a TeX-specific forgejo/gitea instance, it would be attractive for LaTeX devs because they probably are not getting much benefit from be centralised on Github anyway. It was likely an arbitrary choice for them. If there were a LaTeX-themed git community, it would be attractive.


  • I harvested the CTAN DB to research this. The results:

       1390 github.com
         90 gitlab.com
         36 sourceforge.net
         31 codeberg.org
         20 tug.org
         18 framagit.org
         16 bitbucket.org
         10 git.gnu.org.ua
          8 gitlab.gutenberg-asso.fr
          8 gitee.com
          6 dickimaw-books.com
          5 puszcza.gnu.org.ua
          5 heptapod.host
          3 git.robertalessi.net
          3 git.framasoft.org
          2 lists.tug.org
          2 git.sr.ht
          2 gitlab.ti.bfh.ch
          2 gitlab.inria.fr
          2 gitlab.adullact.net
          2 gitea.com
          1 uds-datalab.github.io
          1 tufte-latex.github.io
          1 todo.sr.ht
          1 texnia.com
          1 svn.tuxfamily.org
          1 svn.gnu.org.ua
          1 svn.code.sf.net
          1 svenharder.github.io
          1 savannah.nongnu.org
          1 savannah.gnu.org
          1 repo.or.cz
          1 qa.parsilatex.com
          1 plmlab.math.cnrs.fr
          1 osda.ws
          1 latex-project.org
          1 humenda.github.io
          1 guitex.org
          1 git.umaneti.net
          1 git.savannah.nongnu.org
          1 git.savannah.gnu.org
          1 git.ortolo.eu
          1 git.linta.de
          1 gitlab.science.ru.nl
          1 gitlab.reutlingen-university.de
          1 gitlab.git.nrw
          1 gitlab.fi.muni.cz
          1 forge.apps.education.fr
          1 bastien-dumont.onmypc.net
          1 archiv.dante.de
    

    The 3 most common forges for LaTeX projects are shitty centralised walled-gardens (MS Github, Gitlab, & Sourceforge). Only 174 projects out of 1690 are using open access free-world/decentralised forges (~10%).

    It is disturbing indeed. It also means reporting bugs on ~90% of LaTeX pkgs requires dancing with an evil gatekeeper, licking boots, etc.



  • A lawyer once told me there are a few left-leaning AGs who genuinely take the consumer protection role seriously. He named off a few states where he said you can expect decent treatment of compaints. Then he said a lot of AGs have no interest in the job at all. That they are just looking to climb the ladder and get a CV that enables them to run for governor. I think I have been quite unlucky with the states that are relevant to where I get burnt as a consumer. Though I don’t suppose that’s chance. The shittiest corporations are likely to select right-leaning anti-consumer states for their HQ.