Skip to main content

Search

Items tagged with: fediverse


I made a thing to help me find RSS feeds, and I really liked it. So I made it prettier so you can use it too, if RSS feeds are your thing.

As it turns out, in my corner of the fediverse there’s a ton of them…

https://rss-is-dead.lol

#rss #fediverse


Hey #Fediverse, and #MastoMods!

For my MA thesis, I am looking to research #moderation on Mastodon, and specifically moderators' experiences with it, how it is enacted on their instance, as well as what it entails.

Are you a moderator of an open registration, general interest instance? If you would be willing to participate in a one-off, 45-60 minute-long (online) interview, please reply to this toot or reach me at k.k.matusewicz@student.rug.nl. Thank you in advance!

Boosts are appreciated:)


Krásné páteční #dobréRáno přátelé #fediverse
Dnes to bude pohoda den. Dopoledne musím k našim, tak to bude určitě něco dobrého ke kávě a v pět jdu se synem do kina na druhý díl Duny 👍.


Good morning #Fediverse!

Hope the day is well for everyone. Let’s start it off with our #KoffeeWithKyle chat and see what’s on the agenda.

For me, it’s just the usual day job stuff. I also am having to up the resources for the #AllThingsTech blog as it is currently down because we underestimated the interest we’d get.

Later today will be relaxing and working on week 3 of school.

#GoodMorning #HappyWednesday #AIArt


Just realized one of my favorite place is the perfect Fediverse IRL café

• Lofi hip hop music
• Multicultural
• Random mismatched furniture
• A copy of “Das Kapital” on display
• Library with free to take books
• Gender neutral bathroom
• "Barista antifascista" stickers

#Fediverse #Mastodon #Berlin


Good morning and happy Sunday #Fediverse

How is everyone doing today and what do we all have planned for today?

It's very possible the wife and I might head to the mall today, but not sure. We definitely need to catch up on some TV shows that we are behind on, so maybe that too will happen today as we keep putting it off.

Other than, just a relaxing day hopefully.

#MorningMoments #GoodMorning #HappySunday


#PieFed adds audio posts:

https://piefed.social/post/44964

#fediverse


Now you can create audio posts


When you make a normal 'link' post, if the url ends with .mp3 then PieFed will provide audio player controls on the page and put a little speaker icon on the post teaser, shown in lists of posts.

Go to https://piefed.social/post/44964 to see it in action.



What do you think of when you hear the word "Fediverse'?

Please note that this is only a question about the meaning of the term, not wich protocol is better or if bridges between protcols are a good or bad thing.

Boost for more reach would be nice. :blushy:

#fediverse #activitypub #Mastodon #bluesky

  • Instances connected by using the ActivityPub protocol. (65%, 27 votes)
  • Any network of connected Servers regardles the used protocol. (17%, 7 votes)
  • Something else, I wrote in the comments. (12%, 5 votes)
  • No opinion about that. (4%, 2 votes)
  • I never heard the term Fediverse. (0%, 0 votes)
41 voters. Poll end: in 2 weeks


Regular Fediverse federation check.

According to @fedidb (https://fedidb.org) 22,37% of monthly active Fediverse users are currently on mastodon.social.

I very much welcome the upcoming Mastodon feature that closes registrations if the mods and admins abandon the server (no activity for a week), but when do we finally close servers automatically that have 10k active users?

I'll post about this somewhat regularly under #FederationCheck, but if someone wants to automate that with a bot feel free.

#Fediverse #FediverseMeta #federation #MastodonSocial #Mastodon


Krásné středeční #dobréRáno přátelé #fediverse
No co vám budu vyprávět, vůbec se mi nechce.


Are you seeing spam? A poll

The fediverse is dealing with a major spam attack -- Heise has some coverage (in German).

But not everybody is seeing spam. Are you? If so how much?

@fediversenews #fediverse #spam

PS: if you are seeing spam, there's also afollowon poll asking where

  • No spam -- lucky me! (83%, 10 votes)
  • Just a bit (16%, 2 votes)
  • A lot (0%, 0 votes)
  • So much that I'm almost ready to log off (0%, 0 votes)
12 voters. Poll end: 1 week ago


Looks like someone really kicked the hornet’s nest recently on mastodon by announcing (not even deploying) a Mastodon-BlueSky bridge. Just take a look at the github comments here to get an idea of how this was received.

Plenty of people way more experienced than myself have weighted on this issue so I don’t feel the need to leave my two cents. However I wanted to talk about a very common counter-argument made towards those who do not want such bridges to exist. Namely, that Fediverse already provides the tools towards not having such a bridge be an issue: The allow-list model.

The idea being that if your ActivityPub server by default rejects all federation except towards trusted instances, then such bridges pose no problems whatsoever. The bridge (and any potential undercover APub scrappers) would not be able to get to your instance anyway.

Naturally, the counterargument is that this is way too limiting to one’s reach, and they shouldn’t be forced into isolation like this. Unfortunately the alternative here appears to try and scold others into submission, and this is unlikely to be long term solution. Eventually the Eternal September will come to the Fediverse. If you spent the past few years relying on peer pressure to enforce social norms, then the influx of people who do not share your values is going to make that tactic moot.

In fact, we can already see the pushback to the scolding tactics unfolding right now.

The solution then has to be a way to improve the way we handle such scenarios. Improve the tooling and our tactics so that such bridges and scrappers cannot be an issue.

A lot of the frustration I feel also comes down to the limited set of tools provided by Mastodon and other Fediverse services. A lot of the time, the improvement of tooling is stubbornly refused by the privileged core developers who don’t feel the need to support the needs of the marginalized communities. But that doesn’t mean the tooling couldn’t be expanded to be more flexible.

So let’s think about the Allow-List model for a moment. The biggest issue of an Allow-List is not necessarily that the origin server restricts themselves from the discussion. In fact they’re probably perfectly happy with that. The problem is that if this became the norm, it massively restricts the biggest strength of the Fediverse, which is for anyone to create and run their own server.

If I make a new server and most of everyone I want to interact with is in Allow-List mode, how do I even get in? We then have to start creating informal communication channels where one has to apply to join the allow-circle. Such processes have way too many drawbacks to list, such as naturally marginalizing Neurodivergent people with Rejection Sensitivity Dysphoria, balkanizing the Fediverse, empowering whisper networks and so on.

I want to instead suggest an alternative hybrid approach: The Feeler network. (provisional name)

The idea is thus: You have your well protected servers in Allow-List mode. These are the servers which require protection from constant harassment when their posts are spread publicly. These servers have a few “Feeler” instances they trust on their allow-list. Those servers in turn do not have an allow-mode turned on, but rely on blocklist like usual. Their users would be those privileged enough to be able to handle the occasional abuse or troll coming their way before blocking them.

So far so good. Nothing changes here. However what if those Feeler servers could also use the wider reach to see which instances are cool and announce that to their trusted servers? So a new instance appears in your federation. You, as a Feeler server, interact with them for a bit and nothing suspicious happens, and their users seem all to be ideologically aligned enough. You then add them into a public “endorsed list”. Now all the servers in your trust circle who are in allow-mode see this endorsement and automatically add them to their allow-lists. Bam! Problem solved. New servers have a way to be seen and eventually come into reach with Allow-List instances through a sort of organic probation period, and allow-listed servers can keep expanding their reach without private communications, and arduous application processes.

Now you might argue: “Hey Db0, yes my feelers can see my allow-list server posts, but if they boost them, now anyone can see them, and now they will be bridged to bluesky and I’m back in a bad spot!”

Yes this is possible, but also technically solvable. All we need to do is to make the Feeler servers only federate boosted posts from servers in allow-mode, to the servers that the ones in the allow-list already allow. So let’s say Server T1 and T2 are instances in allow-list mode which trust each other. Server F1 is a Feeler server trusted by T1 and T2. Server S1 is an external instance that is not blocked by F1, but not yet endorsed either. User in F1 boosts a post from T1. Normally a user in S1 would see that post by following that user. All we need to do is to change the software so that if F1 boosts a post from T1, the boost would only federate towards T2 and other instances in T1’s allow-list, instead of everyone. Sure this would require a bit more boost complexity, but it’s nothing impossible. Let’s call this “protected boost”.

Of course, this would require all Apub software to expose an “Endorsement” list for this to work. This is where the big difficulty comes from, as you now have to herd the cats that are the multitude of APub developers to add new functionality. Fortunately, this is where tools like the Fediseer can cover for the lack of development, or outright rejection by your software developer. The Fediseer already provides endorsement functionality along with a full REST API, so you can already implement this Feeler functionality by a few simple scripts!

The “protected boost” mode would require mastodon developers to do some work of course, as that relies in the software internals which cannot be easily hacked by server admins. But this too can potentially just be a patch to the software that only Feeler-admins would need to run.

The best part of this approach is that it doesn’t require any communication whatsoever. All it needs is for the “Feeler” admins to be actively curating their endorsements (either on the Fediseer, or locally if it’s ever added to the SW). Then all allow-list server has to do is choose which Feelers they trust and “subscribe” to their endorsement list for their own allow-list. And of course, they can synchronize or expand their allow-list further as they wish. This approach naturally makes the distributed nature of the Fediverse into a strength, instead of a weakness!

Now personally, I’m a big proponent of the “human touch” in social networks, so I feel that endorsement lists should be a manual mechanism. But if you want to take this to the next level, you could also easily set up a mechanism where newly discovered instances would automatically pass into your endorsement list after X weeks/months of interaction with your user without reports and X-amount of likes or whatever. Assuming admins on-point, this could make widely Feeler servers as a trusted gateway into a well protected space on the fedi, where bad actors would find it extraordinarily difficult to infiltrate, regardless of how many instances they spawn. And it this network would still keep increasing each reach constantly, without adding an extraordinary amount of load to its admins.

Barring the “protected boost” mode, this concept is already possible through the Fediseer. The scripts to do this work already exist as well. All it requires is for people to attempt to use it and see how it functions!

Do point out pitfalls you foresee in this approach and we can discuss how to potentially address them.

https://dbzer0.com/blog/can-we-improve-the-fediverse-allow-list-model/

#fediseer #fediverse #mastodon


In short, who are you yelling at? Who do you expect to "fix" things for you? Right now people are coming down on the guy who is building the bridge to bluesky. That specific guy. They're yelling at him and telling him to make different decisions to protect their personal privacy. Is that what people think they signed up for with the fediverse? Fighting with other individual humans and trying to force them to do what you want?


An interesting proposal for addressing the spam and misuse problem in ActivityPub and the Fediverse:
https://dbzer0.com/blog/can-we-improve-the-fediverse-allow-list-model/
#fediverse #ActivityPub #SpamPrevention


Looks like someone really kicked the hornet’s nest recently on mastodon by announcing (not even deploying) a Mastodon-BlueSky bridge. Just take a look at the github comments here to get an idea of how this was received.

Plenty of people way more experienced than myself have weighted on this issue so I don’t feel the need to leave my two cents. However I wanted to talk about a very common counter-argument made towards those who do not want such bridges to exist. Namely, that Fediverse already provides the tools towards not having such a bridge be an issue: The allow-list model.

The idea being that if your ActivityPub server by default rejects all federation except towards trusted instances, then such bridges pose no problems whatsoever. The bridge (and any potential undercover APub scrappers) would not be able to get to your instance anyway.

Naturally, the counterargument is that this is way too limiting to one’s reach, and they shouldn’t be forced into isolation like this. Unfortunately the alternative here appears to try and scold others into submission, and this is unlikely to be long term solution. Eventually the Eternal September will come to the Fediverse. If you spent the past few years relying on peer pressure to enforce social norms, then the influx of people who do not share your values is going to make that tactic moot.

In fact, we can already see the pushback to the scolding tactics unfolding right now.

The solution then has to be a way to improve the way we handle such scenarios. Improve the tooling and our tactics so that such bridges and scrappers cannot be an issue.

A lot of the frustration I feel also comes down to the limited set of tools provided by Mastodon and other Fediverse services. A lot of the time, the improvement of tooling is stubbornly refused by the privileged core developers who don’t feel the need to support the needs of the marginalized communities. But that doesn’t mean the tooling couldn’t be expanded to be more flexible.

So let’s think about the Allow-List model for a moment. The biggest issue of an Allow-List is not necessarily that the origin server restricts themselves from the discussion. In fact they’re probably perfectly happy with that. The problem is that if this became the norm, it massively restricts the biggest strength of the Fediverse, which is for anyone to create and run their own server.

If I make a new server and most of everyone I want to interact with is in Allow-List mode, how do I even get in? We then have to start creating informal communication channels where one has to apply to join the allow-circle. Such processes have way too many drawbacks to list, such as naturally marginalizing Neurodivergent people with Rejection Sensitivity Dysphoria, balkanizing the Fediverse, empowering whisper networks and so on.

I want to instead suggest an alternative hybrid approach: The Feeler network. (provisional name)

The idea is thus: You have your well protected servers in Allow-List mode. These are the servers which require protection from constant harassment when their posts are spread publicly. These servers have a few “Feeler” instances they trust on their allow-list. Those servers in turn do not have an allow-mode turned on, but rely on blocklist like usual. Their users would be those privileged enough to be able to handle the occasional abuse or troll coming their way before blocking them.

So far so good. Nothing changes here. However what if those Feeler servers could also use the wider reach to see which instances are cool and announce that to their trusted servers? So a new instance appears in your federation. You, as a Feeler server, interact with them for a bit and nothing suspicious happens, and their users seem all to be ideologically aligned enough. You then add them into a public “endorsed list”. Now all the servers in your trust circle who are in allow-mode see this endorsement and automatically add them to their allow-lists. Bam! Problem solved. New servers have a way to be seen and eventually come into reach with Allow-List instances through a sort of organic probation period, and allow-listed servers can keep expanding their reach without private communications, and arduous application processes.

Now you might argue: “Hey Db0, yes my feelers can see my allow-list server posts, but if they boost them, now anyone can see them, and now they will be bridged to bluesky and I’m back in a bad spot!”

Yes this is possible, but also technically solvable. All we need to do is to make the Feeler servers only federate boosted posts from servers in allow-mode, to the servers that the ones in the allow-list already allow. So let’s say Server T1 and T2 are instances in allow-list mode which trust each other. Server F1 is a Feeler server trusted by T1 and T2. Server S1 is an external instance that is not blocked by F1, but not yet endorsed either. User in F1 boosts a post from T1. Normally a user in S1 would see that post by following that user. All we need to do is to change the software so that if F1 boosts a post from T1, the boost would only federate towards T2 and other instances in T1’s allow-list, instead of everyone. Sure this would require a bit more boost complexity, but it’s nothing impossible. Let’s call this “protected boost”.

Of course, this would require all Apub software to expose an “Endorsement” list for this to work. This is where the big difficulty comes from, as you now have to herd the cats that are the multitude of APub developers to add new functionality. Fortunately, this is where tools like the Fediseer can cover for the lack of development, or outright rejection by your software developer. The Fediseer already provides endorsement functionality along with a full REST API, so you can already implement this Feeler functionality by a few simple scripts!

The “protected boost” mode would require mastodon developers to do some work of course, as that relies in the software internals which cannot be easily hacked by server admins. But this too can potentially just be a patch to the software that only Feeler-admins would need to run.

The best part of this approach is that it doesn’t require any communication whatsoever. All it needs is for the “Feeler” admins to be actively curating their endorsements (either on the Fediseer, or locally if it’s ever added to the SW). Then all allow-list server has to do is choose which Feelers they trust and “subscribe” to their endorsement list for their own allow-list. And of course, they can synchronize or expand their allow-list further as they wish. This approach naturally makes the distributed nature of the Fediverse into a strength, instead of a weakness!

Now personally, I’m a big proponent of the “human touch” in social networks, so I feel that endorsement lists should be a manual mechanism. But if you want to take this to the next level, you could also easily set up a mechanism where newly discovered instances would automatically pass into your endorsement list after X weeks/months of interaction with your user without reports and X-amount of likes or whatever. Assuming admins on-point, this could make widely Feeler servers as a trusted gateway into a well protected space on the fedi, where bad actors would find it extraordinarily difficult to infiltrate, regardless of how many instances they spawn. And it this network would still keep increasing each reach constantly, without adding an extraordinary amount of load to its admins.

Barring the “protected boost” mode, this concept is already possible through the Fediseer. The scripts to do this work already exist as well. All it requires is for people to attempt to use it and see how it functions!

Do point out pitfalls you foresee in this approach and we can discuss how to potentially address them.

https://dbzer0.com/blog/can-we-improve-the-fediverse-allow-list-model/

#fediseer #fediverse #mastodon



:boost_love: Boost if you think groups like @NGIZero and others should band together and fund a hard fork of #Mastodon that prioritizes trust and safety, and the needs of #Fediverse admins to protect their users from abuse.

⭐ Favorite if you would support with a little money, too.

#MastoAdmin #FediAdmin #spam #ForkTogether


Alright, what is the #fediverse?

"Social networks that..."

  • Natively support ActivityPub (72%, 43 votes)
  • Support other common protocols (6%, 4 votes)
  • May use a third party bridge (10%, 6 votes)
  • Not sure (10%, 6 votes)
59 voters. Poll end: 1 week ago


In *theory* you should be able to follow this test user:

@你好@i18n.viii.fi

But I can't find any Fediverse software which actually supports non-ASCII usernames.

If you are able to see the user, its description, and its avatar - please send me a screenshot 🙂

#Fediverse #ActivityPub #Unicode


So apparently server administrators on the #Fediverse won’t be able to name custom emoji in their native languages and expect them to work in Mastodon, because according to @Gargron non-ASCII signs are hard to input and diacritics shouldn’t change the meaning of words:

https://github.com/mastodon/mastodon/pull/28572#issuecomment-1878952504

No, in my view emoji identifiers shouldn’t be ‘straightforward to input for everyone’. Custom emoji are local to a server; they should be straightforward to input for the users of that server. People from other servers don’t ever have to type their names (unless their administrators choose to add them to their own server), so their ability to type them is completely irrelevant.

Why should a server made specifically for people speaking Russian or Japanese have to use ASCII for their emoji identifiers? Their users have no trouble typing Cyrillic or Kanji signs; it’s what they already do when they make a post; it’s how they normally talk. Why force them to use a different language/alphabet when typing emoji identifiers?

Moreover, linking the username issue makes no sense whatsoever. Usernames are typed across servers and it makes sense to impose stricter technical limitations so more people can read, write and recognise them. This is not the case for emoji; you rarely ever need to type other servers’ emoji identifiers. Normally you don’t even get to see them; you only get to see the picture they represent! Assuming server admins do their job responsibly, there is zero added confusion for anyone involved.

I understand that Unicode is complex, language support is challenging and compromises might be necessary at times. But can we please accept the existence of different languages and writing systems as a reality that we should try to accommodate for, rather than change or circumvent? Yes, a and á are different signs. Yes, they might radically change the meaning of a word. That’s not a proposition for us to accept or reject; that’s the reality of our multilingual world, and should be the basis of our discussion.

#lang_en #accessibility #a11y #custom_emoji #development #emoji #emojos #free_software #internationalisation #internationalization #i18n #languages #localisation #localization #l10n #Mastodon #multilingual #programming #software #Unicode


Internationalise The Fediverse
https://shkspr.mobi/blog/2024/02/internationalise-the-fediverse/

We live in the future now. It is OK to use Unicode everywhere.

It seems bizarre to me that modern Internet services sometimes "forget" that there's a world outside the Anglosphere. Some people have the temerity to speak foreign languages! And some of those languages have accents on their letters!! Even worse, some don't use English letters at all!!!

A decade ago, I was miffed that GitHub only supported some ASCII characters in its project names. There's no technical reason why your repo can't be called "ഹലോ വേൾഡ്".

Similarly, I'm frustrated that Mastodon (the largest ActivityPub service) doesn't allow Unicode usernames and has resisted efforts to change.

So I built a small ActivityPub server which publishes content from an Actor called @你好@i18n.viii.fi - it is only a demo account, but it works!

Some ActivityPub clients report that they are able to follow it and receive messages from it. Others - like Mastodon - simply can't see anything from it. Take a look at the replies on Mastodon to see which services work. You can also see some of its posts on the Fediverse.

What Does The Fox Spec Say?


The ActivityPub specification says:

Building an international base of users is important in a federated network.
Internationalization


I can't find anything in the specifications which limits what languages a username can be written in. But there are a few clues scattered about.

The user's @ name is defined by preferredUsername which is:

A short username which may be used to refer to the actor, with no uniqueness guarantees.
4.1 Actor objects


There's nothing in there about what scripts it can contain. However, later on, the spec says:

Properties containing natural language values, such as name, preferredUsername, or summary, make use of natural language support defined in ActivityStreams.
4. Actors


So it is expected that a preferred username could be written in multiple scripts. Which implies that the default need not be limited to A-Z0-9.

The ActivityStreams specification talks about language mapping.

Finally, the ActivityPub specification has some examples on non-Latin text in names.

So, I think that it is acceptable for usernames to be written in a variety of non-Latin scripts.

But What About...?


There are usually a few objections to "Unicode Everywhere" zealots like me. I'd like to forestall any arguments.

What about homograph attacks?


Well, what about them? ASCII has plenty of similar looking characters. I doubt most people would notice when a capital i is replaced by a lower L - and vice-versa. Similarly the kerning issue of an r and n looking like an m is well known. Are mixed language homographs more dangerous? I don't think so.

What if people make names that can't be typed?


Well, what if they do? Maybe not being found by people who can't type your language is a feature, not a bug. But, anyway, clients can let users search for other people, or copy and paste their names.

What about weird "Zalgo" text?


It is up to a client to decide how they want to render text input. The "problems" of strange Unicode combinations are well known. This is not a hard computer-science problem.

What about bi-directional text?


The spec makes clear this is allowed.

Do people even want a username in their own script?


I have no evidence for this. But I bet you'd get pretty frustrated if you had to switch keyboard just to type your own name, wouldn't you? In any case, why can't I have a username of @😉

What's Next?


If you build ActivityPub software, give some thought to the billions of people who don't have names which easily fit into ASCII.

If your software can see @你好@i18n.viii.fi and its posts, please let me know.

https://shkspr.mobi/blog/2024/02/internationalise-the-fediverse/

#ActivityPub #fediverse #i18n #mastodon #unicode


Is GitHub Racist?
https://shkspr.mobi/blog/2013/06/is-github-racist/

One of the interesting aspects of privilege is how it lays bare our unconscious assumptions about the world. A male software developer may never consider that a user would want or need to change their name. Thus they would design a product which ignored the millions of women changing their names after marriage.

It's very temping to see software as racist when, in reality, it's more likely to have a root cause of unconscious assumptions.

Take, for example, GitHub. You can host all of your software projects on there - as long as you speak English.

Wait? What?

Try adding a repository which contains, say, Chinese - and all those beautiful characters will be replaced with "-".
Chinese GitHub

I asked GitHub about this, and quickly got this reply.

Unfortunately, at the moment, you can only use ASCII (i.e. Windows-1252) characters in Repo names. Most things on GitHub.com support non-ASCII but because of limitations in Git, the repo name isn't one of them. Sorry about the international-unfriendliness


Interestingly, that's not quite the case. Windows-1252 contains some characters with accents - they simply aren't recognised by GitHub.

Accents Github

We don't live in a homogeneous world. US English is not the global language. Even if it was, ASCII is insufficient to the task of information interchange.

ASCII was invented in 1972 - 40 years later and our brand new shiny kit is hamstrung by the needs of the telegraph industry! It's like that wonderful urban legend about the Space Shuttle being constrained by the size of a horse's arse.

Obviously, GitHub isn't racist. Either they or the originators of Git have assumed that their local dialect is sufficient for a service which aims to be universally acceptable. All the more strange given that Linus Torvalds, the creator of Git, is Finnish and - one presumes - knows about ääkköset (the "extra" letters in the Finnish alphabet).

At this stage in the maturity of the software industry, we should consider the practice of not supporting Unicode as outmoded and dangerous as assuming every year can be represented by a two digit number.

There's a world outside our narrow viewpoint and, if we want to do business with that world, we need to speak their language.

https://shkspr.mobi/blog/2013/06/is-github-racist/

#accents #chinese #github #racism #usability



What is We Distribute, exactly? 🤔

We Distribute is a CC-licensed open media project. It serves as a people-focused tech publication, with the goal of informing and educating people about three things:

1. Decentralized Communications
2. User empowerment
3. The future of the Internet

Most of what we do involves reporting on the day-to-day developments of the #Fediverse. In fact, our articles are ActivityPub-enabled, and integrate directly into the network.

However, the Social Web / Decentralized Social movement involves far more efforts and technologies that we think are also worth reporting on: #Matrix, #XMPP, #Bluesky, #Nostr, #SecureScuttlebutt, and #Solid all bring interesting pieces to the puzzle.

Our ultimate goal is to showcase the ongoing efforts to change the shape and form of the Internet itself, at a grassroots level. Join us on this exciting journey. #WeDistribute


#ILoveFreeSoftware, you love #FreeSoftware. Let's get that down. Most of the time you don't even notice that you're using a device running a :linux: #Linux kernel, :gnu: #GNUtils or services like :apache: #ApacheWebserver, :matrix: #Matrix etc. as they just work and don't get in your way; don't bother you reading ancient 📜 #EULA; don't track you ...

But have you ever said thank you to all the :linus: contributors supporting the projects and sustaining #SoftwareFreedom?! If not, then today's your lucky day. :awesome:

Create a sharepic via @fsfe's https://sharepic.fsfe.org/#ilovefs tool and use the #ILoveFS hashtag to show your appreciation. Additionally, spend some time looking up the #Fediverse handle of your favorite projects and mentioned them.

Happy I 🧡 Free Software Day!


#BlueSky bude mít nejspíše bridge do #Fediverse.
https://snarfed.org/2024-02-12_52106


I think everyone needs to be aware of this: https://fed.brid.gy/r/https://snarfed.org/2024-02-12_52106 and think about whether and how they want their #fediverse accounts to interact with #Bluesky.

Admins should probably discuss with their communities whether or not they want their instances opted-in by default. I think it's unfortunate that he built it to be opt-out rather than opt-in, but Ryan does, at least, seem open to working toward mutually agreeable solutions.


Krásné pondělní #dobréRáno přátelé #fediverse
Sice mám volno, ale jelikož dokončuji první část melouchu tak to bude volno pracovní. Naštěstí to vychází, maximálně na dva dny a hotovo. No a to znamená, že budu objednávat nové PC #jupííí :drake_like: :leftsharkdance:


@abu Und entfolgen und dann wieder folgen auch nicht. Tja, solche Dinge hatte ich hier auch bei Sharkey... Die Avatare sind offenbar eine grosse Herausforderung im #Fediverse - auch in Bezug Speicherplatz... @helpers @powo01 @heluecht @zwovierzwo


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.

Map of a part of London. Some parts are highlighted.

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}});

Map of London with several bits highlighted.

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.

;nw%5B%22name%22%5D%5B%21%22highway%22%5D%5B%21%22railway%22%5D%5B%21%22waterway%22%5D%5B%21%22power%22%5D(around:100,51.5202,-0.1040);out%20center%20qt%2025;]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'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 'Imagine'."        }    ],    "location": {        "name": "John Lennon'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


With inspiration from @jcrabapple let's do a quick poll...

DO YOU LIKE CHOCOLATE?

Please BOOST for maximum exposure to the #Fediverse

Comment below and let's discuss what you like or don't like.

#Poll #Polls #POTD #Question #Questions #QOTD #Chocolate #AllThingsTech

  • Yes! Love me some chocolate! (92%, 39 votes)
  • No! That stuff is eww! (2%, 1 vote)
  • Other -> Comment below and let's discuss! (4%, 2 votes)
42 voters. Poll end: 2 weeks ago


Good morning and happy Saturday to all of you here in the #Fediverse

Tell me about your #MorningMoments such as what you hope to accomplish today, what you've already accomplished today or just a funny story of sorts!

I'm not sure what today holds to be honest. Might stay home and relax, might get out of the house for a bit with the wife. We'll figure that out shortly.

#GoodMorning #HappySaturday #AI #Art


Hey #Fediverse! @Seirdy has a 'forever' article: A look at search engines with their own indexes

One thing this article should remind you all about: there are three dominant #search indexes - Google, Bing, and Yandex. And Yandex is dominant outside of English.

But there are real options, and many of them are open source, especially for outside the commercial internet. (I am partial to the MarginaliaSearch project.)

#dev #internet


@raroun Nein, nicht abstrus, sonderen dem Zweck angepasste Plattform auswählen.
#Friendica ist Micro- und Macroblogging
#Pixelfed ist fürs Teilen von Bildern.

Dea ist eben das #Fediverse. Es gibt nicht die ein und alle Plattform für ein und alles. Sondern es gibt verschiedene Dienste - sie sind alle über #ActivityPub verbunden.

@cantences @tux @helpers


Indonesian interest in social web or #fediverse seems practically nonexistent. Not aware of any more Mastodon instances left running, the Pleroma instance will shut down in April unless someone is willing to take over, and apparently misskey.id is the only one remaining, according to @redseraphim, and maybe some private or personal instances.

From: @t1
https://pleroma.id/objects/af8dffe2-b967-4d4f-a2a5-563225996f39


Have you heard the terms "Fediverse" or "Fedi" and wondered what they are?

I've done a little article that tries to explain what the Fediverse is, and how Mastodon is a part of it:

➡️ https://fedi.tips/what-is-mastodon-what-is-the-fediverse

TL:DR - The Fediverse is a network of thousands of independent social media servers that communicate seamlessly using a common standard. Even totally different kinds of Fediverse server allow users to follow each other.

#FediTips #Fediverse


Why do you like Mastodon (or any open source Fediverse app of your choosing) the most? (You can choose multiple choices)

Boosts appreciated for reach.

#Fediverse #Mastodon #SocialWeb #SocialMedia

  • It's free (43%, 381 votes)
  • No ads (71%, 633 votes)
  • No commercial algorithms (79%, 700 votes)
  • It has many apps (20%, 181 votes)
  • Features towards healthier social media (like content warnings) (53%, 473 votes)
  • Most features in general (15%, 137 votes)
  • Not owned by a single company and cannot be bought (79%, 706 votes)
  • You own your data (49%, 434 votes)
  • You can choose your privacy level even per-post (44%, 390 votes)
  • Something else (10%, 97 votes)
886 voters. Poll end: 2 weeks ago


Krásné nedělní #dobréRáno přátelé #fediverse
Není zde někdo, kdo je schopný sestavit pro mě PC? Na Alze konfigurátor PC je, ale možná někdo poradí lepší sestavu. Přemýšlel jsem o PC postaveném na https://www.alza.cz/intel-core-i7-14700k-d7950854.htm
Hry hrát nehraju a ani hrát nebudu, možná i stačí procesor https://www.alza.cz/intel-core-i5-14500-d8574507.htm


We’ve been floored by everyone’s support for Project Tapestry! Three of the pledge tiers on Kickstarter are already sold out, but there are still several to choose from with rewards ranging from wallpapers to stickers, pins, and even a free year of Wallaroo. At this rate, we’re going to need to come up with some more stretch goals soon! https://www.kickstarter.com/projects/iconfactory/project-tapestry

#ProjectTapestry #Fediverse #RSS #iOSDev


I donated to @thunderbird #freetheinbox . Join me to support communication privacy. #thunderbird does not have Mastodon Share link on their donation page. #Fediverse


Krásné páteční #dobréRáno přátelé #fediverse
Já teď budu mít počítám tři pracovní víkendy v ČR. Nechce se no, ale potřebuji nový PC, tak se to zrovna hodí.
:leftsharkdance: https://invidious.cz/watch?v=DLlJjbyzkqo


@damtux @erAck @italovignoli

Already had some conversation in the past with #LibreOffice via #Fediverse.

I miss real versions numbers, that are useful on technical level.

That's why i asked, if there is somewhere one... hidden under the hood... ;-)

Advertising should maybe be separated from engineering... :-)

But i don't wanted to start a heavy or intense discussion... :-)


Online media can be overwhelming. It's fragmented between countless services, websites, social networks, and apps.

You need an app that weaves together an overview of nearly everything that’s happening across all the different services you follow.

That’s our vision for Project Tapestry, the new Kickstarter we're launching today.

https://www.kickstarter.com/projects/iconfactory/project-tapestry

#ProjectTapestry #Fediverse #iOSDev