IfWO Mastodon

0 Beiträge0 Beteiligte0 Beiträge heute

leChris :mastodon:<a href="https://digitalcourage.social/@nielso" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nielso</a> Mit diesen vier Domains als Ausnahmeregeln (<a href="https://digitalcourage.social/tags/Whitelist" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Whitelist</a>) in Verbindung mit der Isolation der App in <a href="https://digitalcourage.social/tags/RethinkDNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RethinkDNS</a> sieht man keine <a href="https://digitalcourage.social/tags/Werbung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Werbung</a> auf <a href="https://digitalcourage.social/tags/Kleinanzeigen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kleinanzeigen</a>.

Holger Moller<a href="https://bildung.social/tags/TIL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TIL</a> Heute habe ich gelernt, dass mein <a href="https://bildung.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a>-Phone eine <a href="https://bildung.social/tags/Whitelist" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Whitelist</a>-Funktion hat, um VIP-Anrufe trotz eingeschaltetem Nicht-Stören-Modus durchzulassen. Früher hatte ich dafür mal ne spezielle App, aber die funktioniert leider nicht mehr. Und momentan bekomme ich viele Anrufe und deshalb auch viele zur Unzeit. Problem gefixt 🙃 <a href="https://www.heise.de/tipps-tricks/Android-Trotz-Lautlos-Modus-bestimmte-Anrufe-erhalten-3918912.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.heise.de/tipps-tricks/Android-Trotz-Lautlos-Modus-bestimmte-Anrufe-erhalten-3918912.html</a>

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)

Wikinaut<a href="https://berlin.social/tags/Tipp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tipp</a> <a href="https://berlin.social/tags/Fritzbox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fritzbox</a> <a href="https://berlin.social/tags/Whitelist" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Whitelist</a>FritzOS 7.50<a href="https://berlin.social/tags/AVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AVM</a> hat meinen Vorschlag implementiert, dass alle Anrufe _ohne_ Telefonbucheintrag umgeleitet werden könnnen.Telefonbuch/bücher sind nun de fakto eine "Whiteliste" für Anrufe, die durchkommen dürfen.Das war bisher nicht möglich!AVM FritzOS 7.50Telephony: Call handling allows call blocks and call diversion (e.g. to answering machine) for callers „not in the telephone book” (telephone book as positive list)<a href="https://en.avm.de/release-notes-fritzos-750/" rel="nofollow noopener noreferrer" target="_blank">https://en.avm.de/release-notes-fritzos-750/</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#whitelist