![](https://mastodon.nzoss.nz/system/accounts/avatars/000/021/439/original/a485d9a3a4c0673e.jpg)
![](https://lemmy.magnor.ovh/api/v3/image_proxy?url=https%3A%2F%2Flemmy.ml%2Fpictrs%2Fimage%2Fst9xYggWap.png)
Free human being of this Earth. Be excellent to each other! All my posts here are CC BY-SA 4.0 (or later).
#Vegan #Permaculture #Transition #PeerProduction #FreeCode #CreativeCommons #SciFi #Comedy #Juggling
Timezone: UTC+12
@glowl
> if you are willing to do a bit of reading in the wiki, i like the editing plugin for OsmAnd
Thanks, I’ll have a look. Having editing it in the map app I already use sounds good.
@glowl
> SCEE (Street complete Extended Edition) that allows for a lot more tags to be edited and some more nifty customization options
This sounds powerful. Would you recommend it for a beginner?
@MapAmore
> If you don’t like to map them directly yourself, when you’re on site
I have ADHD. If I can’t do it right away when I notice the problem, I’m unlikely to remember. So what I need is an Android app that makes it quick and easy to submit an update (with appropriate license) whenever I notice a discrepancy.
@glowl
> Havent tried OSM Go yet, but can recommend streetcomplete and every door
Are these available on F-Droid?
@MapAmore
I use @openstreetmap a lot, via #OSMAnd+, and I’d love to give back to the map commons. The biggest problems I see are not with the basic data (streets etc), since the NZ govt’s own map data is released under CC license, and updates to it are quickly imported into #OSM.
Rather what I see is outdated info about what can be found at a given address. Any advice of helping to update that kind of data? Is it part of OSM or other data commons used by OSMAnd+?
deleted by creator
@deadsuperhero
> development of a Go-based backend implementation, Dendrite
Also Rust-based homeserver implementations like Construct and Conduit. Both of which are usable, although missing a few nice-to-have added features. Eg Conduit is still working on;
“E2EE emoji comparison over federation (E2EE chat works)… Outgoing read receipts, typing, presence over federation”
@deadsuperhero
> the reference implementation everyone uses by default is known to be bloated and slow, and poor at scaling
This doesn’t seem to stop the fediverse growing (*cough* Mastodon *cough*).
@smileyhead
> But noone figured out how to prevent that in federated systems
You’ve basically got a choice been a centralised service where metadata can be limited but E2EE is mostly pointless (you have to trust the service operators’ E2EE deployment), or a decentralised network where E2EE is reliable, but it’s harder to limit metadata.
Which one is best depends on the situation/ threat model.
@deadsuperhero
> I’d really love to see a “modern” WhatsApp-like take on an XMPP messenger, but I haven’t found any
Have you looked at @snikket_im ?
@theKalash
> Lemmy neads a feature where people can “merge” communities from different instances so it appears like a single one
I’m confused by this. I’ll admit I haven’t used Lemmy much yet, but I thought communities do exist across all servers? So if I join “c/fediverse” on any one server, and you join “c/fediverse” on any other server, we’re joining the same community. Is that not how it works?
@Hexadecimalkink
> Did peerfed ever figure out the bandwidth issues? Is there a way this can scale?
If this is the PeerFed you meant, I’m guessing the answer to both these questions is ‘no’;
“This paper has been archived and no longer reflects the author’s current thinking.”
https://github.com/joshdoman/peerfed-paper
Although I do find this concept intriguing;
“The system consists of two convertible assets, interest-bearing cash and a paid-in-kind perpetual bond.”
https://github.com/joshdoman/peerfed-paper/blob/main/peerfed.pdf
@yogthos