Live data from Hacker News

Lost and Found

walzr.com

11–16 of 16 posts

Re: Lost and Found

#11
post #5
post #3

I was thinking this was directory "lost+found", but it is about "lost and found" at places like airports.

Go ahead and cut a notch out of my expertise card, but in all my years playing with UNIX, I’ve never used that directory.

I have had items put there a few time on an fsck. Not often but it has happened.

Re: Lost and Found

#12
>When something turns up at a stadium or an airport, staff photograph it, log it, and wait. Hundreds of places use one software tool for managing lost items, and I scraped their archives: thousands of accidental portraits of lost stuff.

Where? What Software? What Archive?

So many photos of peoples lock screens with clearly visible faces...

Re: Lost and Found

#13
post #6

scraped from....where? The Lost & Found systems are all public? Sorry I haven't had to dig something out of a lost & found that wasn't a cardboard box under a front desk or whatever...

It is scraped from Pixit. They sell lost/found, evidence + seized item management systems. [1] The listings are public; it was cool OP turned this into a mini art piece. [1] https://www.pixithq.com/

Is there really enough market for an actual software solution like this?

I worked alongside the lost&found office at an old job, we just had a spreadsheet and a book...

Re: Lost and Found

#14
Something is wrong with this websites scroll. Perhaps due to pictures loading. It feels that you scroll but see the same pictures.

Re: Lost and Found

#16
post #5
post #3

I was thinking this was directory "lost+found", but it is about "lost and found" at places like airports.

Go ahead and cut a notch out of my expertise card, but in all my years playing with UNIX, I’ve never used that directory.

I think the most common use case was when a file descriptor was still open in some process, but the file itself had been completely unlink'd from the filesystem. Most often it was some sort of temporary file.

Anyway the /lost+found link would be its inode number, I think. And then you could recover it after fsck had relinked it into the hierarchy. It would have to put them there, because it had no idea what pathname it had used when it was a real file.

Post reply on HN