@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?
strypey
joined 6 years ago
@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+?
@regalia
> I recommend actually looking at what it looks like on the site, it’s extremely different then how it looks on mastodon
Yes, I'm familiar. I've been following Lemmy development for several years, as part of research for fediverse.party. That's the background to my comments about the algorithm determining what appears on a Lemmy front page.
If you're proposing that there's a more complicated algorithm at work, what do you think it is?
@regalia
> Are you replying from Mastodon right now
Yes. Here's the post you just replied to, on the public-facing web page of the Mastodon server I use:
@regalia
> the algo for active/hot favor large communties, so smaller ones tend not to show up on the front page
I presume it's the same as what determines which posts appear on the front page of a Mastodon server; chronological order of posts. That would favour the larger communities, since people post there more often.
The other limiting factor, I presume, is a Lemmy server only knows about the communities its accounts are members of. Larger communities will have members on more servers.
@regalia
> our algo doesn’t do a good job of promoting smaller communities
Lemmy has an algo for that?
@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.
view more: next ›
@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.
@MapAmore @openstreetmap @everydoor