yeag123

As other commenters have pointed out, 13.3 million gallons = ~40.8 acre-feet and this being Nebraska, the obvious comparison is agriculture (Corn and Soybeans being the main crop).

The average Nebraska farm is 989 acers[1] as of 2022 and uses roughly ~1,200 acre-feet of water (or roughly 390 million gallons) per year[2]. So a single average Nebraska farm uses roughly 30 times the water the Lincoln data center uses per year. There are 44,479 farms/ranches covering 44 million acres, which accounts for over 90% of the state's total land area.

Until I looked this up, I didn't appreciate the scale of water usage in farming (even in a state like Nebraska that gets a large amount of rainfall compared to Central or Southern California). I hope that the current data center environmental focus continues to shed light on our industrial water and electrical usage.

[1]http://farmflavor.com/nebraska/nebraska-crops-livestock/top-... [2]https://cropwatch.unl.edu/2024/2023-irrigation-and-water-man...

I've been working on this for about a year and a half, and decided to finally open source it.

I wanted an intelligent document processing SaaS (Document AI, Form Recognizer, the various PDF-to-JSON tools) that you could run on your own hardware.

The interesting bits:

- Three-tier extraction: PyMuPDF for digital PDFs (~50ms), Docling layout-only for scanned-but-readable, Docling+OCR for the rough stuff. Auto-fallback based on extracted character count. - Smart templates use vector similarity (Qdrant) to classify docs, then LLM extraction for fields — no regex, so layout drift doesn't break templates. - Local Ollama or Azure OpenAI, switchable per-user.

Built on top of Cole Medin's local-ai-packaged. Apache 2.0.

https://github.com/nickyeager/fetchtext

I’m working on a tool to automate manual document workflows, specifically for industries like manufacturing where accounting paperwork is still a manual burden.

The workflow: Upload doc → LLM extracts structured data → Generate new doc from template.

It’s API-first, includes webhooks, and is built to be self-hosted/self-provisioned for privacy. Still very much a WIP, but looking for feedback on the feature set and the extraction accuracy.

URL: https://fetchtext.io

Working on either a self hosted, or self "provisioned" document extraction platform. Trying to make it as flexible as possible, so businesses

I worked with manufacturing companies, and the amount of manual document extraction and manipulation, particularly from accounting documents, was always a large burden.

The goal is upload a document → extract structured fields via LLM → generate new documents from templates. Has a dashboard, with an API, along with a webhook, very much a WIP.

https://fetchtext.io

Quoteapro Inc | Software Engineer | San Francisco | Onsite or Remote | Full Time | https://quoteapro.com

Quoteapro is helping increase the global recycling rate by automating the complex world of scrap metal brokerage. We work with scrap yards and end processors to safely broker containers of recycled material worldwide. We build tools to grow domestic scrap processors network of buyers and automate tasks needed to sell in the export market.

Full job posting: https://angel.co/l/2iPxPG

Ideally you'd be:

-Detail and process oriented -As excited about developing innovative software as we are -Want to be part of a team of creative, confident, thoughtful people who are enthusiastic about increasing the level of global recycling -Comfortable working in an early-stage startup environment where things move extremely fast and requirements change frequently -Comfortable and have previous experience working with distributed team members

If you're interested please email nick@quoteapro.com.

Odesk sort of does this with feedback ratings: https://www.odesk.com/ I'm sure there are other freelance sites that do as well.

My understanding is that inorder for a developer to receive an xAuth application key, they have to first be vetted by a representative from twitter. This involves exchanging information regarding a summary of the app, how it will be using the API, etc. So there is still some existing measure of security regarding xAuth, although not nearly as much oauth.

A Chrome extension that I use pretty regularly for this sort of thing is Stay Focused: http://goo.gl/gHWFQ