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

Big news for the #Fediverse!


Gli ultimi otto messaggi ricevuti dalla Federazione
  • @fabio this is getting annoying, every time you save your site you are sending a new version of all your likes so this thread gets bumped to the top of my feed

    read more

  • @macgirvin that's interesting, I hadn't thought of using punycode. Like @edent@mastodon.social my exposure to it was strictly limited to domains (and even then only to counter domain spoofing)

    read more

  • @edent@mastodon.social -- It's also used for the username component of email addresses iirc; as these are originally also specified as 7-bit US-ASCII. So I convert local usernames with idn. Just something I did out of habit really. You can use UTF-8 if you want, so I'm only saying that punycode seems to federate better based on my experience. We tested this with a bunch of fediverse software at the time and it just worked. We'll accept either.

    read more

  • @macgirvin
    I thought Punycode was only for domain names. Are you saying you also use it for the user part?

    read more

  • @edent@mastodon.social -- I've just tested and that account also works fine with Hubzilla. I will mention that your implementation in this case uses url-encoded usernames while ours uses punycode. They should be able to interact just fine, but the fact that there are multiple ways to arrive at a solution could cause a bit of confusion for implementers.

    You'll need to use punycode if you wish to federate with the diaspora protocol or email or any other projects or protocols which restrict the character set for usernames. So it might end up being a more flexible solution in the long run and should work fine with every other fediverse project today. ASCII-restricted software will just use the xn-- name; and all their links and buttons should work fine.

    Url-encoding should also work, but perhaps not so universally and easily as punycode; as witnessed by the number of issues documented in this thread.

    read more

  • @apps look @julian isn't this sorta what you were just talking about with hashtag combining schemes

    read more

  • @jandi
    Yes, that would really help. I will set the priority in the Weblate project for the part used to understand tags inside messages. Thank you for your continuous support on projects :)

    read more

  • @edent@mastodon.social -- Just looked again... this was first introduced as a hidden feature in redmatrix around 2013-2014, and so may also be available currently in Hubzilla (behind the "system.unicode_usernames" feature toggle). There were some major changes in 2019 that to my knowledge weren't ever backported. I think these only applied to local usernames and not remote usernames, but the functionality in hubzilla still might need to be verified.

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    10 Views
    Frequently /me [from DE] thinks about #Datensparsamkeit The officially best [en] explainer is https://martinfowler.com/bliki/Datensparsamkeit.html@mfowler I became a Carteret Islands person once.Looking at my shell neclace.My wish for christmas is that you read it and carefully think about all the things you publish in terms of accessibility but also formats and size.An example:For @clemensg I did the yearly #ActivityPub #Atlas - it comes with millions and millions of geohashed places for OSM, wikidata, official sources and, well openaddresses [.io] They publish primarily in texts with lines of geojson.The whole planet is about 46 GB … … …An exmple:DE in this "format" is about 3.2 GBDE in CSV would be maybe 1.5 GB If we normalize and publish it compressed, it is [incl geohashes] about 800MB. If we now compress the geohashes, expanding it clientside the 3.2 GB becomes 250 MB …Maybe we can't save tons of powerplants like banning bitcoin would.But together we can save lots of energy.#geojson 💣
  • 0 Votes
    1 Posts
    7 Views
    In PieFed v1.4 it will be possible to label posts as having AI generated content. Labelled posts will get a little badge near their title, similar to how nsfw and nsfl content is labelled. Mods and authors can change this value on a post in the same way they do flair and nsfw, using the little tags button in the bottom right or in 'More options' when editing their post. Account settings for blocking: [image: rIJ6kQKrU9ygU9p.png] Similar to how NSFW works, each user can control how those posts are listed on the home page, etc. The default is 'Label as AI', which just adds the badge. People averse to AI-generated content might want to change this to 'Hide completely'. Also similar to NSFW, entire communities can be assigned as 'AI content' and that will auto-tag every post inside as being AI generated. If the community mods have this value unset (e.g. Lemmy communities, which don't have this functionality) then the instance admin can manually override the community's AI Generated setting.
  • 0 Votes
    3 Posts
    15 Views
    @thomasjwebb Yes, that would be Lockdown mode, where you only allow activities/access to servers you define, it requires they sign fetches, but most software does by now!
  • Bonfire Social 1.0rc3 release

    Fediverso fediverse
    1
    0 Votes
    1 Posts
    13 Views
    This post did not contain any content.