Aufgrund des Artikels zur Fediverse Spamwelle von Codeberg (Link ganz unten) ist mir wieder Folgendes eingefallen.

Ich hatte da mal vor längerer Zeit eine Art Spam-Trust-Abo Addon für Friendica vorgeschlagen, mit dem die Blockliste einer anderen Instanz oder mehreren Instanzen abonniert werden kann, denen vertraut wird. So dass ...

1. die Information rein kommt, welche Instanzen und Accounts auf die Blocklisten gekommen sind, oder generell vorhanden sind, aber ohne dass diese automatisch übernommen werden. Aktuell ist die Info über solche Accounts oft Zufall oder durch proaktives Suchen im Fediverse auffindbar. Oder das Absuchen von Blocklisten auf github. Also maximal manuell.
2. Eine Option, in der Blöcke sofort übernommen werden und in einer Liste zur Bestätigung angezeigt werden. So dass immer klar ist, was neu und was alt ist.
3. Die 2. Option als temporäre Lösung verfügbar ist z.B. bei Urlaub, Krankheit usw.
4. Dieses Feature bidirektional mit jeder dieser Optionen funktioniert.

Leider wurde dieser Vorschlag recht rabiat mit etwas abstrusen Vorwürfen niedergemacht. Aber vielleicht ist jetzt die Zeit gekommen, mit einem kühlen Kopf über so eine Lösung nachzudenken.

Denkbar ist natürlich, dass hier ein größeres Trustnet aufgebaut werden kann, in dem es auch "rejects" gibt. Oder auch Trustkarma für Instanzen, die sehr seriös mit dem Thema umgehen oder eben kaum Trustkarma für Hyperventilierer und Empöristen. Das ist dann aber ein ganz anderes und recht komplexes Thema.

What we can learn from the Fediverse spam for Codeberg
https://blog.codeberg.org/what-we-can-learn-from-the-fediverse-spam-for-codeberg.html

#Fediverse #Friendica #Addon

@Urząd Ochrony Danych Osobowych Witam na #fediverse.
I od razu pytanie (😁) - jak należy rozumieć na podanej wyżej stronie #uodo fragment

"Z kolei na LinkedIn planowane jest publikowanie dłuższych i bardziej pogłębionych materiałów skierowanych przede wszystkich dla biznesu"?

Czy to znaczy, że będą przez uodo publikowane jakieś treści, do których dostęp będzie wymagać posiadania konta linkedin (bo będą wyłącznie na tym portalu) ?
Warto zwrócić uwagę, że serwery sieci fediverse oprócz braku reklam i algorytmów szeregujących treści zapewniają dostęp do publicznych postów bez algorytmów szpiegujących/profilujących/identyfikujących odbiorców co wydaje się szczególnie ważne w kontekście publikacji właśnie na temat ochrony danych osobowych.
Nie ma również żadnych przeszkód technicznych, żeby na fediverse (w tym na mastodonie) publikować teksty dowolnej długości - ew. limit znaków wpisu jest pod kontrolą administratora każdej instancji.

Decentralizacja w #Fediverse.

Zakładacie profile na nowych instancjach?
Zdziwienie, że na starych (innych) instancjach nie widzicie nowych wpisów?

Nieważne, czy to Mastodon, Pixelfed, PeerTube czy inny serwis, warto zadbać o obserwację tych nowych profili na jak największej liczbie popularnych instancji.

Bo ActivityPub działa podobnie do e-mail. Wysyła wpisy jedynie tam, gdzie są adresy i profile, które go obserwują.
Nie ma centralnego repozytorium wszystkich wpisów jak w serwisach centralizowanych (np. Twitter/FB/YouTube).

Więc zanim zaczniecie publikować treści z nowych profili, poproście znajome osoby z różnych instancji, by wasze nowe konto zaobserwowały. A już na pewno zaobserwujcie sami siebie z własnych innych profili. Wtedy te treści mają szansę się federować na inne serwery. Inaczej pozostaną dostępne jedynie na instancji oryginalnej.

Tak to działa od samych początków #fediwersum opartego o protokół #ActivityPub 😀

#FediTipsPL #FediPomoc

Drogie, drodzy, Fedisie i osoby PolSocialove ❤️

Macie od dzisiaj możliwość przekazać 1,5% ze swoich podatków na fundację FTdL @ftdl , która prowadzi kawałek polskiego #Fediverse.

Wiem, że macie swoje ulubione organizacje, pomyślcie o Fundacji, która nie ma innego finansowania niż Wasze Wsparcie 💶

Jeśli dacie się przekonać, a IMO warto, to w PiT należy wpisać nie tylko numer KRS (Fundacji FaniMani), ale i cel szczegółowy, który oznacza wsparcie FTdL.

– KRS: 0000507234
– cel szczegółowy: 85488

Wielkie dzięki za rozważenie i wsparcie 😀

Można też podbić tego tootka 🚀

Niech Polskie Fedi się rozwija, serwerów przybywa, a ludzie walą tutaj drzwiami i oknami 😀

#WspieramPolSocial #WspieramFTdL

Rebuilding FourSquare for ActivityPub using OpenStreetMap
https://shkspr.mobi/blog/2024/01/rebuilding-foursquare-for-activitypub-using-openstreetmap/

I used to like the original FourSquare. The "mayor" stuff was a bit silly, and my friends never left that many reviews, but I loved being able to signal to my friends "I am at this cool museum" or "We're at this pub if you want to meet" or "Spending the day at the park".

So, is there a way to recreate that early Web 2.0 experience with open data and ActivityPub? Let's find out!

This quest is divided into two parts.

1. Get nearby "Points of Interest" (POI) from OpenStreetMap.
2. Share a location on the Fediverse.

OpenStreetMap API

OpenStreetMap is the Wikipedia of maps. It is a freely available resource which anyone can edit (if they're skilled enough).

It also comes with a pretty decent API for querying things. For example, nw["amenity"]({{bbox}}); finds all "amenities" near a specific location.

As you can see, it has highlighted some useful areas - a pharmacy and a pub. But it has ignored other useful locations - the train station and the park. It has also included some things that we may not want - bike parking and a taxi rank.

What API call is needed to get useful locations of of OverPass?

It's possible to specify the type of thing to find using nw["amenity"="restaurant"]; - but adding every single type of thing would quickly end up with a very large query containing hundreds of types.

It is also possible to exclude specific types of places. This retrieves all amenities except for fast food joints:

nw["amenity"]({{bbox}});-nw["amenity"="fast_food"]({{bbox}});

Perhaps one solution is just to return everything and let the user decide if they want to check in to a telephone kiosk or a fire hydrant? That's a bit user-hostile.

Instead, this query returns everything which has a name nw["name"]({{bbox}});

That cuts out any unnamed things - like park benches and car-sharing spots. But it does add named roads and train lines.

It is possible to use filters to exclude results from OverPass. The best that I can come up with is: nw["name"][!"highway"][!"railway"][!"waterway"][!"power"]({{bbox}});

That gets everything which has a name, but isn't a highway or railway or waterway or powerline. It isn't perfect - but it will do!

This is the query which will retrieve the 25 nearest things within 100 metres of a specific latitude and longitude. It includes the name and any other tags, the location, and the OSM ID.

overpass-api.de/api/interpreter?data=[out:json];nw["name"][!"highway"][!"railway"][!"waterway"][!"power"](around:100,51.5202,-0.1040);out center qt 25;

ActivityPub

There's good news and bad news here. Firstly, ActivityStreams (which are subscribed to in ActivityPub) supports the concept of "Place" and "Location".

Once the user has a latitude and longitude, the can share it - along with a message, photo, or anything else.

Something like:

{    "@context": "https://www.w3.org/ns/activitystreams",    "type": "Note",    "content": "Here in NYC! <a href=\"https://www.openstreetmap.org/way/958999496\">John Lennon&#039;s Imagine Mosaic</a>.",    "attachment": [        {            "type": "Image",            "mediaType": "image\/jpeg",            "url": "https:\/\/fastly.4sqi.net\/img\/general\/590x786\/56367_9pxuZJD7d1hgPdaMFcFq1pipvTTMynBJsYcpHH-b8mU.jpg",            "name": "A photo of a mosaic which says &#039;Imagine&#039;."        }    ],    "location": {        "name": "John Lennon&#039;s Imagine",        "type": "Place",        "longitude": 40.77563,        "latitude": -73.97474    }}

It is worth noting that Mastodon doesn't (natively) support location - if you view my repost of that PixelFed post you'll see there's no location metadata attached. That's OK! It just means that the status needs to include human-readable data.

Similarly, Mastodon doesn't support the arrive vocabulary. So this will be limited to a message with a location attached.

Other ActivityPub services do support location.

Putting it all together

Well… that's a job for next week. Probably!

• Building a web site which gets the user's location is easy.
• Getting the data from OverPass should be straightforward.
• Creating an ActivityPub server which can post geotagged notes into the Fediverse might be a little beyond my skillset! Some testing with Darius Kazemi's AP Glitch suggests this should work.

If you'd like to help, please leave a comment.

https://shkspr.mobi/blog/2024/01/rebuilding-foursquare-for-activitypub-using-openstreetmap/

#ActivityPub #fediverse #FOURSQUARE #geolocation #OpenStreetMap

Terence Eden’s Blog

2024-01-27 12:34:55

Rebuilding FourSquare for ActivityPub using OpenStreetMap
https://shkspr.mobi/blog/2024/01/rebuilding-foursquare-for-activitypub-using-openstreetmap/

I used to like the original FourSquare. The "mayor" stuff was a bit silly, and my friends never left that many reviews, but I loved being able to signal to my friends "I am at this cool museum" or "We're at this pub if you want to meet" or "Spending the day at the park".

So, is there a way to recreate that early Web 2.0 experience with open data and ActivityPub? Let's find out!

This quest is divided into two parts.

1. Get nearby "Points of Interest" (POI) from OpenStreetMap.
2. Share a location on the Fediverse.

OpenStreetMap API

OpenStreetMap is the Wikipedia of maps. It is a freely available resource which anyone can edit (if they're skilled enough).

It also comes with a pretty decent API for querying things. For example, nw["amenity"]({{bbox}}); finds all "amenities" near a specific location.

As you can see, it has highlighted some useful areas - a pharmacy and a pub. But it has ignored other useful locations - the train station and the park. It has also included some things that we may not want - bike parking and a taxi rank.

What API call is needed to get useful locations of of OverPass?

It's possible to specify the type of thing to find using nw["amenity"="restaurant"]; - but adding every single type of thing would quickly end up with a very large query containing hundreds of types.

It is also possible to exclude specific types of places. This retrieves all amenities except for fast food joints:

nw["amenity"]({{bbox}});-nw["amenity"="fast_food"]({{bbox}});

Again, that would be complex.

Perhaps one solution is just to return everything and let the user decide if they want to check in to a telephone kiosk or a fire hydrant? That's a bit user-hostile.

Instead, this query returns everything which has a name nw["name"]({{bbox}});

That cuts out any unnamed things - like park benches and car-sharing spots. But it does add named roads and train lines.

It is possible to use filters to exclude results from OverPass. The best that I can come up with is: nw["name"][!"highway"][!"railway"][!"waterway"][!"power"]({{bbox}});

That gets everything which has a name, but isn't a highway or railway or waterway or powerline. It isn't perfect - but it will do!

This is the query which will retrieve the 25 nearest things within 100 metres of a specific latitude and longitude. It includes the name and any other tags, the location, and the OSM ID.

overpass-api.de/api/interpreter?data=[out:json];nw["name"][!"highway"][!"railway"][!"waterway"][!"power"](around:100,51.5202,-0.1040);out center qt 25;

ActivityPub

There's good news and bad news here. Firstly, ActivityStreams (which are subscribed to in ActivityPub) supports the concept of "Place" and "Location".

Once the user has a latitude and longitude, the can share it - along with a message, photo, or anything else.

Something like:

{    "@context": "https://www.w3.org/ns/activitystreams",    "type": "Note",    "content": "Here in NYC! <a href=\"https://www.openstreetmap.org/way/958999496\">John Lennon&#039;s Imagine Mosaic</a>.",    "attachment": [        {            "type": "Image",            "mediaType": "image\/jpeg",            "url": "https:\/\/fastly.4sqi.net\/img\/general\/590x786\/56367_9pxuZJD7d1hgPdaMFcFq1pipvTTMynBJsYcpHH-b8mU.jpg",            "name": "A photo of a mosaic which says &#039;Imagine&#039;."        }    ],    "location": {        "name": "John Lennon&#039;s Imagine",        "type": "Place",        "longitude": 40.77563,        "latitude": -73.97474    }}

For example, here's a PixelFed post with an attached location - and this is the JSON representation. That status can be reposted into other social networks.

It is worth noting that Mastodon doesn't (natively) support location - if you view my repost of that PixelFed post you'll see there's no location metadata attached. That's OK! It just means that the status needs to include human-readable data.

Similarly, Mastodon doesn't support the arrive vocabulary. So this will be limited to a message with a location attached.

Other ActivityPub services do support location.

Putting it all together

Well… that's a job for next week. Probably!

• Building a web site which gets the user's location is easy.
• Getting the data from OverPass should be straightforward.
• Creating an ActivityPub server which can post geotagged notes into the Fediverse might be a little beyond my skillset! Some testing with Darius Kazemi's AP Glitch suggests this should work.

If you'd like to help, please leave a comment.

https://shkspr.mobi/blog/2024/01/rebuilding-foursquare-for-activitypub-using-openstreetmap/

#ActivityPub #fediverse #FOURSQUARE #geolocation #OpenStreetMap

05 - Find nodes by applying multiple filters

A basic tutorial covering the key features of the Overpass language

^{osm-queries.ldodds.com}

I've been using Friendica for a few years, and after playing around with other software such as #Pleroma, #Misskey and #Lemmy, I've ended up returning to the old reliable in my personal server. I'm honestly surprised to see Friendica offering a more solid offering of capabilities than many other newer #Fediverse platforms, such as #Mastodon itself. However, it still seems to be missing a few important capabilities (some of them already implemented in other AP software, some of them being improvements to the already existing capabilities of Friendica) that I would like to see implemented eventually, to finally being able to move full-time to a single Fediverse software instead of spreading my server cycles between several web-apps. Feel free to add to this list, or to recommend workarounds for any of the issues I've listed below. Also, I plan to see how to learn enough PHP in order to send PRs for a few of these, but I want to check if there's any work in progress regarding any of these issues to avoid duplicate efforts.

Issues that already exist in the tracker, roughly sorted by priority:

• Import posts from Mastodon / Misskey exported backups: see issue 6004 in GitHub.
• Ability to vote in polls, not just have them read-only: see issue 11093 in GitHub.
• Ability to import #RSS feeds and not only ActivityPub accounts: see issue 13854 in GitHub.
• Post translation, using a backend such as #LibreTranslate: see issue 12948 in GitHub.
• Merge related notifications to prevent duplicates: see issue 9729 in GitHub.
• React with emoji, as in #Misskey and derivatives: see issue 6271 in GitHub.

Issues that are already managed with an add-on, but have issues:

• Proper support for Mastodon custom emojis: the "Mastodon Custom Emojis" add-on can handle them in post content, partially, and can't handle them in user names yet.
• Handling the "NSFW" tag in federated posts: the "NSFW" add-on can detect specific words on a post, but if the post does not include them (and yet uses the "mark as NSFW" option in Mastodon), the post will be shown regardless.

Implementing new views in order to work better as a replacement for other platforms:

• Feed reader view a la #FreshRSS / #Lemmy: collapse comments and content, optionally add buttons to go to the previous/next unread item, filter by read.
• Video player /gallery view a la #PeerTube / #Pixelfed: pin media to top and comments / voting buttons to bottom.
• Dashboard view a la Tweetdeck: allow multiple columns with different filters. This might require a rewrite of the logic for each page, as each filter is currently implemented on the interface as a PHP request bound to each page load. This might fall out of scope for the default Friendica interface, and might be better served with an external web-app.

Issues that don't seem to be tracked currently, but are mostly a "nice-to-have" and have a lower priority:

• Ability to mix "what's hot" sorting with circle filtering: useful for news for example.
• Export posts in Firefish-compatible format: not mandatory, but would be handy for data migration purposes. Alternatively, one could make Firefish itself compatible with Friendica-formatted backups.

!Friendica Support