qjkxbmwvz @ qjkxbmwvz @startrek.website

Posts

3

Comments

1,198

Joined

2 yr. ago

Wild turkeys can fly, too. It's impressive. I once came around a blind corner on my bike, there was a turkey in the road, and it took off in a manner I can only describe as 747esque --- it did not look like it should be able to fly, yet there it was, clearly flying.

Very cool. I know someone, in a fairly small but funded field, who had this sort of requirement --- Elsevier had the relevant publication, but they couldn't publish there due to access policies (or it was going to be painful to do so at any rate). So they started their own publication!

I forgot the specifics, but it essentially uses arXiv as the backend, and there's a (commercially available?) frontend that lets editors and reviewers do their thing. "Publishing" in this journal is essentially just endorsing an arXiv paper; so it's open access by design.

Really cool stuff. Their field is small enough that iirc they could kinda get critical mass to give Elsevier the finger and adopt this new platform. Warm fuzzy feeling thinking about it!

That's my Signal alert sound.

If the research was conducted with public money, it should be freely accessible by the public, change my mind...

It could be fun to implement this under *NIX for fun --- cronjob to take screenshots, some OCR, throw it in a database...I'd never want to use this "feature" but as an academic exercise it could be a fun project.

But having it implemented by my OS, and not by me...yikes. No thanks.

My 2¢ is that running Linux, you play the role of user and of sysadmin. On some distros you only put on the sysadmin hat once in a blue moon, but on others you're constantly wearing it.

My Arch experience is a few years out of date; I felt I played sysadmin more than, say, Debian Stable, but it wasn't too onerous. I also had an older Nvidia card, so there were some...fun issues now and then.

I use Debian on my machines now, and am happy. Try some different distributions! Even better, have /home on its own partition (better yet, own disk) --- changing distros can be nice and easy without worrying about your personal data.

I just tried that and got the same result. It's from a site that just quotes a snippet of an Onion article 🤦

Well, that's kinda besides the point right? The composition of "natural" food has huge variation. There is no "nutritional content of a banana." There's the nutritional content of this banana, of that banana, of an unripe banana, of a ripe banana, of an overripe banana...but these can be hugely different. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8266066/

For highly processed foods, I agree.

But for relatively unprocessed foods, seems completely reasonable to me at first glance. The relative sugar content of, say, an apple, is dependent on all sorts of parameters (sun, water, soil...). The gluten content of wheat, iron content of vegetables, all of these things are variable. The more "natural" a food is, the higher the variability (as opposed to, say, artificial candy --- that should be pretty uniform).

Yeah, but where's Starfleet HQ?!

Makefile in other comments. You'll need something like this on the title page (this assumes you use my Makefile which puts the version in VERSION.tex [that's the literal name of the file, not a placeholder]):

{\bf{\color{red}DOCUMENT REVISION:}} {\color{blue}\input{VERSION}}

I also had some Makefiles in other directories, e.g., for my media/ I had:

    
MAKE = make -s
RECURS = svgs/

recurs: $(RECURS)
        @$(foreach DIR, $(RECURS), \
                echo "MAKE      (CD)    $(CURDIR)/$(DIR)"; \
                $(MAKE) -C $(DIR) $(MAKECMDGOALS);)
        @echo "MAKE     (CD)    $(CURDIR)/"

all: recurs

clean:

allclean: recurs clean

  

and for media/svgs/:

    
SVG_FILES := $(wildcard *.svg)
PDFDIR := ./
PDF_FILES := $(patsubst %.svg,$(PDFDIR)/%.pdf,$(SVG_FILES))

all: $(PDF_FILES)

clean:
        @rm -f $(PDF_FILES)
        @echo "SH       (RM)    Tidying up derived PDFs"

allclean: clean

$(PDFDIR)/%.pdf: %.svg
        @inkscape -T --export-pdf=$@ $<
        @echo "INK      (PDF)   $<"


  

Sure thing. This also includes the beamer bit which I used for my defense. It's all pretty hacky but hope it's useful!

 # Makefile for compiling LaTeX documents.

    
#
# Errors aren't handled gracefully (tex doesn't write to stderr, it seems)
# If you encounter errors, use "make verbose"
#
# For small changes (probably those without references), use "make quick"
#
# Thanks to https://gist.github.com/Miliox/4035649 for dependency outline

TEX = pdflatex
BTEX = biber
MAKE = make -s
TEXFLAGS = -halt-on-error
# $(MAIN).log is dumb if we have multiple targets!
SILENT = > /dev/null || cat $(MAIN).log
SILENT_NOER = 2>/dev/null 1>/dev/null
EDITOR = vim -p
PDFVIEW = evince
MAIN = main
PRES = presentation
ALL = $(MAIN).pdf
RECURS = media/ manuscripts/
VERSION := $(shell git rev-parse --short HEAD | cut -c 1-4)$(shell git diff-index --quiet HEAD && (echo -n ' ';git log -1 --format=[%cd]) || (echo -n '* '; date -u '+[%c]'))

all: recurs $(ALL)
pres: $(PRES).pdf
scratch: scratch.pdf

scratch.pdf: scratch.tex
    @echo "TEX	(final)	$<"
    @$(TEX) $(TEXFLAGS) $< $(SILENT)

verbose: SILENT = ''
verbose: $(ALL)

recurs: $(RECURS)
    @$(foreach DIR, $(RECURS), \
        echo "MAKE	(CD)	$(CURDIR)/$(DIR)"; \
        $(MAKE) -C $(DIR) $(MAKECMDGOALS);)
    @echo "MAKE	(CD)	./"

clean:
    @echo "SH	(RM)	Not recursing; 'make allclean' to clear generated files."
    @rm -f *.aux *.log *.out *.pdf *.bbl *.blg *.toc *.lof *.lot *.bcf *.run.xml

allclean: recurs
    @echo "SH	(RM)	A clean directory is a happy directory"
    @rm -f *.aux *.log *.out *.pdf *.bbl *.blg *.toc *.lof *.lot *.bcf *.run.xml
version:
    @echo "SH      (ver) $(VERSION)"
    @echo $(VERSION) > VERSION.tex

nixpages: main.pdf
    @echo "PDF     (pdftk)"
    @pdftk main.pdf cat 1 4-end output final.pdf

quick: $(MAIN).tex version
    @echo "TEX	(final)	$<"
    @$(TEX) $(TEXFLAGS) $< $(SILENT)

$(MAIN).pdf: $(MAIN).tex $(MAIN).bbl all.tex tex/abstract.tex tex/intro.tex tex/appendix.tex tex/some_section.tex tex/some_other_section.tex
    @echo "TEX	(draft)	$<"
    @$(TEX) $(TEXFLAGS) --draftmode  $< $(SILENT)
    @echo "TEX	(final)	$<"
    @$(TEX) $(TEXFLAGS) $< $(SILENT)

$(MAIN).bbl: $(MAIN).aux
    @echo "BIB	(bib)	$(MAIN)"
    @$(BTEX) $(MAIN) > /dev/null
    
$(MAIN).aux: $(MAIN).tex $(MAIN).bib version
    @echo "TEX	(draft)	$<"
    @$(TEX) $(TEXFLAGS) --draftmode  $< $(SILENT)

$(PRES).pdf: $(PRES).tex $(PRES).bbl tex/beamer*.tex tex/slides/*.tex
    @echo "TEX	(draft)	$<"
    @$(TEX) $(TEXFLAGS) --draftmode  $< $(SILENT)
    @echo "TEX	(final)	$<"
    @$(TEX) $(TEXFLAGS) $< $(SILENT)
$(PRES).bbl: $(PRES).aux
    @echo "BIB	(bib)	$(PRES)"
    @$(BTEX) $(PRES) > /dev/null
$(PRES).aux: $(PRES).tex $(MAIN).bib
    @echo "TEX	(draft)	$<"
    @$(TEX) $(TEXFLAGS) --draftmode  $< $(SILENT)

edit:
    @echo "EDIT	(fork)	$(EDITOR)"
    @$(EDITOR) ./tex/*.tex *.tex

view:
    @echo "VIEW	(fork)	$(PDFVIEW)"
    @$(PDFVIEW) $(ALL) $(SILENT_NOER) &

  

I also added a Makefile for mine (LaTeX), and it would add the commit hash to the front page (with an asterisk if the repository had uncommitted changes).

So, if I gave a draft to someone and got feedback, I'd know exactly which revision it was.

Double-sided phone could be pretty neat.

Another option is to remove it and symlink it to a static version of your choosing. I believe NM won't replace a symlink. You can just remove the symlink when you're done and it should go back to normal...I think.

If you self host, or want to try it out, Immich is amazing. It feels very much like Google Photos, but you can run it completely locally. Great integration with desktop and mobile, both Android, and iOS.

I'm not affiliated at all with the project.

So it's a security camera pointing at your screen, but with AI involved.

Honestly though, this sounds like the kind of thing you could hack together with a shell script and OCR on a *NIX system in an afternoon. Cronjob to take screenshots and run them through OCR, keywords to a database. Add hooks to your window manager to take additional screenshots on relevant events (change desktop, application opens/new window on screen, etc.).

"People forget that the brain is the biggest erogenous zone."

--- Jackie Treehorn

Only additional thing I would do would be to try to ssh into it to. Sounds like that wouldn't have worked anyway. But if you can ssh into it while it's in a degraded-but-not-completely-borked state you can poke around, troubleshoot, and of course cleanly reboot.