• 1 Post
  • 22 Comments
Joined 20 days ago
cake
Cake day: June 5th, 2025

help-circle









  • Very nice project! Thank you for using OpenStreetMap! I love it when the project I contribute to gets used in interesting projects like this!

    But some quick notes, related to the map display: It’s called OpenStreetMap, there is no s at the end, written in CamelCase without spaces. The other more important problem is you forgot to include the attribution text on the map. For using OSM there is only one requirement, you have to display “© OpenStreetMap” somewhere on a corner of the map. More info about this on the website of the OSM foundation: https://osmfoundation.org/wiki/Licence/Attribution_Guidelines

    I see the attribution text is displayed on http://trails.tchncs.de/ but not on https://demo.wanderer.to/ so I don’t know what’s going on.

    The basemap display on the demo website uses the tile server from openstreeetmap.org. This is very discouraged, and also can give bad experience to users. The tiles on osm.org are raster tiles, they are regenerated automatically after a change in the map data, they are aimed as a tool for map contributors, not end users. You can read more about this here: https://operations.osmfoundation.org/policies/tiles/

    There is a new totally free maplibre compatible vector tile provider, which uses the same map data, I recommend to switch to OpenFreeMap. Users can also self host OpenFreeMap, so some really privacy minded users could totally self host the full project this way.




  • External 80 to internal 80 and external 443 to internal 443

    With this config you don’t have to deal with ports later, as http is 80, https is 443 by default.

    If you run some container on port 81, you have to deal with that in the reverse proxy, not in the router. E.g. redirect something.domian.tld to 192.168.0.103:81

    If you use docker check out nginxproxymanager, it has a very beginner friendly admin webui. You shouldn’t forward the admin ui’s port, you need to access it only from your lan.








  • Different instances of the same software. Like all lemmy instances running the same software, all piefed instances run the same piefed software. But it’s not important.

    The technology lemmy and piefed runs on is very interesting and complex, I don’t like to overwhelm users with the tech gibberish when I explain what is lemmy. The important thing: they don’t have to register everywhere, only at one instance, and they can read everything from that account, even if it’s ona different instance. For mobilapp use voyager for lemmy, intetstellar for piefed and mbin.

    Later when they explored the fediverse they will find the tech writeups organically, you don’t have to start with that.


  • I think just links for help communities where users can ask technical questions and find answers would be enough. You don’t know what your followers use, they can read the piefed community from a lot of places, you can follow it from lemmy or mastodon, so it’s possible that piefed related help would be irrelevant for most of them. These kind of technical writeups are common in “main” or “meta” communities, where you can assume your users are on the same instance as you, as the topic of the community is the instance.

    For general piefed help there is !piefed_help@piefed.social