IfWO Mastodon

Kim SudenlehtoWhat kind of <a href="https://firefish.social/tags/Moderation" rel="nofollow noopener noreferrer" target="_blank">#Moderation</a> would you wish a <a href="https://firefish.social/tags/SocialMedia" rel="nofollow noopener noreferrer" target="_blank">#SocialMedia</a> service like <a href="https://firefish.social/tags/Mastodon" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> or <a href="https://firefish.social/tags/FireFish" rel="nofollow noopener noreferrer" target="_blank">#FireFish</a> to have? If you're familiar with <a href="https://firefish.social/tags/ActivityPub" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a>, can it be implemented with it? I'm specifically looking for user moderation tools for <a href="https://firefish.social/tags/PeerToPeer" rel="nofollow noopener noreferrer" target="_blank">#PeerToPeer</a> <a href="https://firefish.social/tags/P2P" rel="nofollow noopener noreferrer" target="_blank">#P2P</a> solutions where service data can't be manually moderated by a central actor. The service data would exist until it is forgotten (no one is sharing it). Profile and post data would be saved in browser database (<a href="https://firefish.social/tags/IndexedDB" rel="nofollow noopener noreferrer" target="_blank">#IndexedDB</a>) and peer discovery would be handled by <a href="https://docs.holepunch.to/building-blocks/hyperswarm" rel="nofollow noopener noreferrer" target="_blank">#HyperSwarm</a> or similar. The whole service would be a <a href="https://firefish.social/tags/PWA" rel="nofollow noopener noreferrer" target="_blank">#PWA</a>, requiring zero server resources beyond loading the PWA, if possible. Currently I have this: - honor thread starter <a href="https://firefish.social/tags/blocklist" rel="nofollow noopener noreferrer" target="_blank">#blocklist</a> (by hiding and not sharing those comments - individual clients could still show these and share, resulting in less effective moderation) - allow thread starter to moderate their threads (don't know how to implement this, yet) - allow post and comment editing (implement post version checking and automatic updates - again, a client might ignore updates or collect history, resulting in less effective moderation) - profile reputation, automatic blocking based on reputation and shared blocklists, <a href="https://firefish.social/tags/whitelist" rel="nofollow noopener noreferrer" target="_blank">#whitelist</a> and shared whitelists, blocklist and shared blocklists (see above); essentially a <a href="https://firefish.social/tags/WebOfTrust" rel="nofollow noopener noreferrer" target="_blank">#WebOfTrust</a> implementation - visibility controls - sharing controls (for service data; by default interactions and own data would be saved locally and shared to network; data that is offline isn't reachable)

Olivier ForgetInteresting. It appears @denoland is implementing a key-value inside <a href="https://social.tchncs.de/tags/Deno" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Deno</a>: <a href="https://github.com/denoland/deno/pull/18232" rel="nofollow noopener noreferrer" target="_blank">https://github.com/denoland/deno/pull/18232</a>I had hoped they would implement <a href="https://social.tchncs.de/tags/indexedDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#indexedDB</a>, but this appears to be harder than it should be. <a href="https://github.com/denoland/deno/issues/1699#issuecomment-472237532" rel="nofollow noopener noreferrer" target="_blank">https://github.com/denoland/deno/issues/1699#issuecomment-472237532</a>I would prefer a standard, but I'll take it.In <a href="https://social.tchncs.de/tags/dropserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dropserver</a> apps I tend to import <a href="https://social.tchncs.de/tags/SQLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SQLite</a> as <a href="https://social.tchncs.de/tags/WASM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WASM</a> module, but that doubles the sandbox startup time. I can make do with a KV store if it comes for free. In many cases that will work well enough.<a href="https://deno.land/x/sqlite@v3.7.0" rel="nofollow noopener noreferrer" target="_blank">https://deno.land/x/sqlite@v3.7.0</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#indexeddb