Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone
  • 0 Votes
    1 Posts
    13 Views
    Grenofen Wood, Lower Walkham Valley, West #DevonThough undoubtedly wooded for centuries, many trees there today are not ancient. From early C19th to 1880s, area was heavily mined for tin and copper, with wood for various purposes in great demand. End of mining meant regrowth of trees amongst lumps and bumps and derelict buildings. Yet it's the kind of moist sheltered habitat that creates temperate rainforest, full of almost luminous moss at this time of year.#Mosstodon #TemperateRainforest

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    0 Views
    Quando i dati diventano intelligence: la lezione strategica della Charles de Gaulle📌 Link all'articolo : https://www.redhotcyber.com/post/quando-i-dati-diventano-intelligence-la-lezione-strategica-della-charles-de-gaulle/#redhotcyber #news #intelligenza #datipubblici #gps #strava #sicurezzainformatica #hacking #cybersecurity #portaerei
  • 0 Votes
    1 Posts
    3 Views
    So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629. You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type. The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant. I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse. What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks. #fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue
  • 0 Votes
    3 Posts
    2 Views
    @LukefromDC @TexasObserver They cant stop ALL of us ✊
  • 0 Votes
    1 Posts
    0 Views
    Week in Fediverse 2026-03-20Servers- Akkoma v2026.03- Bonfire v1.0.2- PeerTube v8.1.3- Mitra v4.20.0- NodeBB v4.10.0- GoToSocial v0.21.2- Funkwhale v2.0.0- Ktistec v3.3.4- ActivityPub for WordPress v8.0.2- PeerTube v8.1.3- ties v0.2.0- Wafrn v2026.03.02- PieFed v1.6.13- Some updates to ActivityBot- tags.pub: Global hashtag serverClients- Fedilab v3.37.1- tinmop v0.9.9.141421356237309504- tooi v0.23.0- Holos v1.0.0- Voyager v2.44.0- Aria v1.4.6Tools and Plugins- mastodon-bookmark-rss: A small app to let you connect your mastodon bookmarks to your RSS reader- smol overlays: Chat overlay and emoji wall for Owncast streamersFor developers- activitypub-federation-rust v0.5.11Protocol- FEP-3ab2: ActivityPub Event Streaming API- FEP-34ec: Notification Collection Endpoint- FEP-db70: RemoveAll Collection Activity- FEP-c07e: add product type to object- FEP-c195: JSONPath Filtering for ActivityPub Collection Retrieval- FEP-f011: Full-Text Search Query Syntax for ActivityPub- FEP-a1d1: ActivityPub Patch- FEP-c81b: Agent Social Attribution for ActivityPubArticles- Openness, transparency and reach: three reasons why public institutions should embrace the Fediverse- The Purpose of Protocols-----#WeekInFediverse #Fediverse #ActivityPubPrevious edition: https://mitra.social/objects/019ce933-238d-11fb-304d-c3557c940c30