no gui, but still super simple and enough for local testing:

• open a terminal
• cd folder/you/want/to/serve/from
• python -m http.server -b 127.0.0.1

open browser surf to http://127.0.0.1:8000/

can you define “machine”? if it’s a desktop: have you thought about an additional hdd/ssd? all the pros of dual booting, without the cons: you can simply unplug the windows drive if you install linux.

but still do a backup!

thanks for the insight, much appreciated!

thanks for your answer. that’s what i feared, but its good to be sure!

thanks for your comment and recommendation.

i use this at work, and its great. Only downside is, that the buttons are hard to identify and move depending on the size of the screenshot, so you always have to search for the function you need.

Does anyone have a workaround for this?

Even the internet archive is nothing in comparison to the image data used for street view.

honest curiosity, don’t want to flame war: do you have numbers for that?

stitching is no longer a requirement because of 360° cameras, is it? it could also be made on the client side if really needed. if people can use josm to contribute to osm, they can use some other software for stitching?!

have you seen that the internet archive has also quite high res books scans and videos?

if your aiming for covering every small street of the whole world tomorrow, you are right: it won’t work. but nothing would stop to start with a single city or a region?

lets agree to disagree :-)

you have a point there.

and yet we have the internet archive… so it seems to be possible.

any sane people would same the same about a map covering the whole world, and yet there is openstreetmap.

yes there are many challenges, but if you start small and grow from there it could work and maybe span a town or two in a couple of years…

i think you mix two concepts here:

the first is basically that you can post to multiple communities at once (community = tag)

the second is that users can assign tags/communities to existing posts, and vote for them

i like both and already thought about the first one, but not the second one… I first thought it might be a problem that if you add a community/tag to an existing post it will be immediately visible on said community/tag, but if this is a problem for said community, someone could down-vote there and it would vanish. but then you would need two up votes: one for community fit, and one for the post itself. could be a problem, if you post one link to a very popular community and a very small one, then the post would get many upvotes and be on the top of the small one…

how would you federate? it comes natural for lemmy to have each community on a seperate server, but how would you do this for a project like dmoz?

i don’t think it would be a good idea that one server could own “art” for example, and no one else could contribute. and on the other side it would not be a good idea if everyone could add sites for “art” as then it’s just a federated wiki? you still would have to fight spam? do all entries in “art” have the same priority? or should there be some voting, or verifying from other instances maybe? but then rough instances could vote for each other?!

how big is the spam problem on lemmy?

hoped to discover a good open source software for collaborative editing, but their solution is based on https://standardnotes.com/