| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| gnu_social_on_sdf [2021/03/09 13:56] – [From Their Profile Page] hc9 | gnu_social_on_sdf [2024/09/04 07:05] (current) – es” hc9 |
|---|
| [[http://gnu.io/social|GNU social]] is a social media //platform ((GNU social might look like a simple microblogging platform, but it really is a general-purpose social networking platform for any kind of media you can imagine. Some nodes are very limited in the kinds of media they support, while others support the publication and subscription various structured data items such as bookmarks, event notifications, polls, and questions, in addition to microblogs with media attachments.))// implementing the [[http://www.w3.org/community/ostatus/|OStatus]] protocol stack. It works in much the same way as Twitter or Facebook or Google+; you may: | [[http://gnu.io/social|GNU social]] is a social media //platform ((GNU social might look like a simple microblogging platform, but it really is a general-purpose social networking platform for any kind of media you can imagine. Some nodes are very limited in the kinds of media they support, while others support the publication and subscription various structured data items such as bookmarks, event notifications, polls, and questions, in addition to microblogs with media attachments.))// implementing the [[http://www.w3.org/community/ostatus/|OStatus]] protocol stack. It works in much the same way as Twitter or Facebook or Google+; you may: |
| |
| * publish text //notices// (like Twitter's "tweets" or Facebook's "status updates"), optionally with file attachments (images, sounds, documents, and so-on); | * publish text //notices// (like Twitter's “tweets” or Facebook's “status updates”), optionally with file attachments (images, sounds, documents, and so-on); |
| * //favor// other users' notices ("like", or "+1" on other services); | * //favor// other users' notices (“like”, or “+1” on other services); |
| * //follow// ("subscribe","friend") the activity of other users, hashtags, and search terms; | * //follow// (“subscribe”,“friend”) the activity of other users, hashtags, and search terms; |
| * join groups to receive topical notices and broadcast your own notices to interested parties; | * join groups to receive topical notices and broadcast your own notices to interested parties; |
| * //repeat// ("retweet","share") others' notices so that your friends, associates, and followers will see them; | * //repeat// (“retweet”,“share”) others' notices so that your friends, associates, and followers will see them; |
| * and, of course, //comment// on notices and participate in public discourse. | * and, of course, //comment// on notices and participate in public discourse. |
| |
| GNU social differs from the most popular social media platforms in a fundamental way: rather than having all communication hosted on a single corporation's private network, GNU social is an open-source software platform running on a distributed system of [[gnu_social_on_sdf#understanding_gnu_social|federated servers]] operated by a diverse array of groups and individuals. Unlike Facebook or Google+ or Twitter, this social network has no central authority, no owner -- //anyone// can operate a server in the //Fediverse//: the service providers and users that make-up the network on which GNU social operates. | GNU social differs from the most popular social media platforms in a fundamental way: rather than having all communication hosted on a single corporation's private network, GNU social is an open-source software platform running on a distributed system of [[gnu_social_on_sdf#understanding_gnu_social|federated servers]] operated by a diverse array of groups and individuals. Unlike Facebook or Google+ or Twitter, this social network has no central authority, no owner -- //anyone// can operate a server in the //Fediverse//: the service providers and users that make-up the network on which GNU social operates. |
| |
| The SDF hosts a public GNU social //node ((//"Node"// is in vogue at the time of this writing; in the past, //"instance"// was the preferred term, and you'll still see this used by folks who've been around for a while.))// which may be reached at https://gs.sdf.org. An SDF membership is no longer required to join this node; simply direct your browser to https://gs.sdf.org/main/register to create a new account -- and bring your friends! | The SDF hosts a public GNU social //node ((//“Node”// is in vogue at the time of this writing; in the past, //“instance”// was the preferred term, and you'll still see this used by folks who've been around for a while.))// which may be reached at https://gs.sdf.org. An SDF membership is no longer required to join this node; simply direct your browser to https://gs.sdf.org/main/register to create a new account -- and bring your friends! |
| |
| This tutorial is intended to help you get started with the SDF GNU social web interface, and to a lesser extent with GNU social in general. The software version at the time of writing this is 1.2.0-beta3. | This tutorial is intended to help you get started with the SDF GNU social web interface, and to a lesser extent with GNU social in general. The software version at the time of writing this is 1.2.0-beta3. |
| ===== Setting-Up Your Account ===== | ===== Setting-Up Your Account ===== |
| |
| After logging into your account for the first time, you should click the 'SETTINGS' link at the top of the page; this will present you with a form for filling-out your profile information. It's pretty standard stuff: full name, bio, website, and so-on. Fill these things in as usual, but take note of the last two settings on the page. | After logging into your account for the first time, you should click the ‘SETTINGS’ link at the top of the page; this will present you with a form for filling-out your profile information. It's pretty standard stuff: full name, bio, website, and so-on. Fill these things in as usual, but take note of the last two settings on the page. |
| |
| ==== Subscription Policy and Private Posts ==== | ==== Subscription Policy and Private Posts ==== |
| === Favor === | === Favor === |
| |
| //Favoring// a notice is akin to "liking" or "+1'ing" a notice on other services. It adds the notice to your list of favorites, which you can access by clicking the Favorites link in the navigation pane (or by pointing your browser to ''https://gs.sdf.org/{username}/favorites'' ). This also sends a notice to the node of the notice's author to let it know that you have favored it, and when other people view the notice, they will be able to see that you favored it as well. | //Favoring// a notice is akin to “liking” or “+1'ing” a notice on other services. It adds the notice to your list of favorites, which you can access by clicking the Favorites link in the navigation pane (or by pointing your browser to ''https://gs.sdf.org/{username}/favorites'' ). This also sends a notice to the node of the notice's author to let it know that you have favored it, and when other people view the notice, they will be able to see that you favored it as well. |
| |
| === Reply === | === Reply === |
| ==== Context and Origin ==== | ==== Context and Origin ==== |
| |
| Below each post, you'll also see a hyperlink around the time that it was posted, and a link that either says '[permalink]', or something like 'from quitter.se'. These two links allow you to view the notice in context, or view the original notice. Here's why that's useful: | Below each post, you'll also see a hyperlink around the time that it was posted, and a link that either says ‘[permalink]’, or something like ‘from quitter.se’. These two links allow you to view the notice in context, or view the original notice. Here's why that's useful: |
| |
| === Viewing Notices In Context === | === Viewing Notices In Context === |
| |
| If you click on the time of the notice's posting, you'll be taken to a //Conversation// view, where you can see the conversational context in which a notice/reply was posted. This conversation is reconstructed from notices that are present in the local database (this may make more sense after reading the [[gnu_social_on_sdf#understanding_gnu_social|Understanding GNU Social]] section). Because SDF GNU social is a small node, this will sometimes produce badly fragmented conversations as only a small part of the conversation has been delivered to our node (see [[gnu_social_on_sdf#the_federation_problem|The "Federation Problem"]]). | If you click on the time of the notice's posting, you'll be taken to a //Conversation// view, where you can see the conversational context in which a notice/reply was posted. This conversation is reconstructed from notices that are present in the local database (this may make more sense after reading the [[gnu_social_on_sdf#understanding_gnu_social|Understanding GNU Social]] section). Because SDF GNU social is a small node, this will sometimes produce badly fragmented conversations as only a small part of the conversation has been delivered to our node (see [[gnu_social_on_sdf#the_federation_problem|The “Federation Problem”]]). |
| |
| === Viewing A Notice's Original === | === Viewing A Notice's Original === |
| |
| The second link, which will say '[permalink]' for notices posted by SDF users or "from some.server" for notices received from outside SDF, will take you to the unique web address for that notice. If the notice originated outside of SDF, then you will be taken to its author's server. There are a couple of reasons why you might want to do this: if the conversation view on SDF GNU social seems to be missing a lot of notices, you can go to the notice's home server and see the (hypothetically more complete) conversation view there; or, sometimes a message will be truncated as it passes from one Fediverse node to another, and you will need to view the notice on its originating node to see the entire message. This latter scenario typically won't happen on SDF, because our notice-length limit is 1000 characters, and most folks' notices are much shorter than that. | The second link, which will say ‘[permalink]’ for notices posted by SDF users or “from some.server” for notices received from outside SDF, will take you to the unique web address for that notice. If the notice originated outside of SDF, then you will be taken to its author's server. There are a couple of reasons why you might want to do this: if the conversation view on SDF GNU social seems to be missing a lot of notices, you can go to the notice's home server and see the (hypothetically more complete) conversation view there; or, sometimes a message will be truncated as it passes from one Fediverse node to another, and you will need to view the notice on its originating node to see the entire message. This latter scenario typically won't happen on SDF, because our notice-length limit is 1000 characters, and most folks' notices are much shorter than that. |
| |
| ===== Writing Notices ===== | ===== Writing Notices ===== |
| Any URLs you type in your notice will be automatically hyperlinked when you post it. | Any URLs you type in your notice will be automatically hyperlinked when you post it. |
| |
| The 'at' character (''@''), 'hash' (''#''), and 'bang' (''!'') all have special functions when they appear at the beginning of a word; let's go over those functions now: | The ‘at’ character (''@''), ‘hash’ (''#''), and ‘bang’ (''!'') all have special functions when they appear at the beginning of a word; let's go over those functions now: |
| |
| ==== Mentions (using '@') ==== | ==== Mentions (using '@') ==== |
| === User Name Collisions === | === User Name Collisions === |
| |
| In the Fediverse, two or more users on different servers can have the same nickname, and this can cause minor headaches when you're trying to mention someone. For example, there might be a user named Zorba on ''quitter.se'', and a different user named Zorba on ''micro.fragdev.com''. You might follow the Zorba on FragDev and want to mention him in a notice, so you write ''@Zorba'' in your message -- but when you post it you see that it's gone to Zorba at Quitter.se instead. Why? Because at some point your node received a notice from zorba@quitter.se and put him into the remote user database, and when the server looked in the table of user nicknames to find out who "Zorba" is, it simply took the first Zorba it came across, which happened to be the wrong one. | In the Fediverse, two or more users on different servers can have the same nickname, and this can cause minor headaches when you're trying to mention someone. For example, there might be a user named Zorba on ''quitter.se'', and a different user named Zorba on ''micro.fragdev.com''. You might follow the Zorba on FragDev and want to mention him in a notice, so you write ''@Zorba'' in your message -- but when you post it you see that it's gone to Zorba at Quitter.se instead. Why? Because at some point your node received a notice from zorba@quitter.se and put him into the remote user database, and when the server looked in the table of user nicknames to find out who “Zorba” is, it simply took the first Zorba it came across, which happened to be the wrong one. |
| |
| This won't happen with the nicknames of your fellow SDF users -- the server looks for local nicknames first, and all of the SDF users have unique names -- but it //can// happen with users on other servers. To be completely sure that your mention hits the right user, you can use their [[gnu_social_on_sdf#webfinger|webfinger address]] when mentioning them. So, in the previous example, instead of simply writing "@Zorba", you would use "@zorba@micro.fragdev.com" | This won't happen with the nicknames of your fellow SDF users -- the server looks for local nicknames first, and all of the SDF users have unique names -- but it //can// happen with users on other servers. To be completely sure that your mention hits the right user, you can use their [[gnu_social_on_sdf#webfinger|webfinger address]] when mentioning them. So, in the previous example, instead of simply writing “@Zorba”, you would use “@zorba@micro.fragdev.com” |
| |
| ==== Tags (using '#') ==== | ==== Tags (using '#') ==== |
| Ah, //hashtags//. Who isn't tired of hearing that word? | Ah, //hashtags//. Who isn't tired of hearing that word? |
| |
| They work on GNU social much the same as elsewhere: you prepend a "hash" (''#'') to a word, and the notice becomes "tagged" with that keyword so that people who are following that tag will see your notice in their Home Timeline. | They work on GNU social much the same as elsewhere: you prepend a “hash” (''#'') to a word, and the notice becomes “tagged” with that keyword so that people who are following that tag will see your notice in their Home Timeline. |
| |
| Tags in GNU social are case-insensitive, so you can write #tubers, #Tubers, #TUBERS, or #tUbErS in your notice, and they'll all be treated as #tubers. The up-side of this is that people who appreciate clarity can write multi-word hashtags in camel-case (#ThePenIsMightier) while remaining in the loop with their shift-key-averse fellows who aren't bothered by possible ambiguity in their tags (#thepenismightier). | Tags in GNU social are case-insensitive, so you can write #tubers, #Tubers, #TUBERS, or #tUbErS in your notice, and they'll all be treated as #tubers. The up-side of this is that people who appreciate clarity can write multi-word hashtags in camel-case (#ThePenIsMightier) while remaining in the loop with their shift-key-averse fellows who aren't bothered by possible ambiguity in their tags (#thepenismightier). |
| ==== Group Addressing (using '!') ==== | ==== Group Addressing (using '!') ==== |
| |
| The "bang" (''!'') is used in GNU social to address groups. | The “bang” (''!'') is used in GNU social to address groups. |
| |
| If you are a member of a group, when you type the group's name prepended with a bang in a notice (eg "!cheeseafficionados"), that notice will arrive in the timelines of all the group's members, all over the fediverse. | If you are a member of a group, when you type the group's name prepended with a bang in a notice (eg “!cheeseafficionados”), that notice will arrive in the timelines of all the group's members, all over the fediverse. |
| |
| === Group Name Collisions === | === Group Name Collisions === |
| ==== From Their Profile Page ==== | ==== From Their Profile Page ==== |
| |
| Click on a user's avatar or nickname to be taken to their profile page. Once there, look for a button that says "Subscribe" or "Remote Follow". Clicking the button will open a dialog that asks for your //account ID//. You can use the URL of your SDF GNU social profile page, which looks like this: ''https://gs.sdf.org/ //nickname//'', or you can use your webfinger ID, which looks like this: //nickname//@gs.sdf.org. | Click on a user's avatar or nickname to be taken to their profile page. Once there, look for a button that says “Subscribe” or “Remote Follow”. Clicking the button will open a dialog that asks for your //account ID//. You can use the URL of your SDF GNU social profile page, which looks like this: ''https://gs.sdf.org/ //nickname//'', or you can use your webfinger ID, which looks like this: //nickname//@gs.sdf.org. |
| |
| After you submit your ID, you will be redirected to a page asking you to confirm the follow. Once you've confirmed, you will start receiving notices from the user you've just followed in your timeline. | After you submit your ID, you will be redirected to a page asking you to confirm the follow. Once you've confirmed, you will start receiving notices from the user you've just followed in your timeline. |
| ==== From Your Profile Page ==== | ==== From Your Profile Page ==== |
| |
| If you already have another user's account ID — either a webfinger address, such as "bob@status.hoohaw.org", or a URL such as "http://status.hoohaw.org/bob" — you can begin following them by going to your profile page and clicking the "+ Remote" button underneath the "Following" section on the right-hand side of the screen. This will open a dialog asking for the account ID of the user you wish to follow. Fill in the box, submit it, confirm on the page you're redirected to, and that's it! | If you already have another user's account ID -- either a webfinger address, such as ''bob@status.hoohaw.org'', or a URL such as ''http://status.hoohaw.org/bob'' -- you can begin following them by going to your profile page and clicking the “+ Remote” button underneath the “Following” section on the right-hand side of the screen. This will open a dialog asking for the account ID of the user you wish to follow. Fill in the box, submit it, confirm on the page you're redirected to, and that's it! |
| |
| ==== Finding Users To Follow ==== | ==== Finding Users To Follow ==== |
| |
| Yes, it's all well and good to know how to follow people — but how do you find people to follow? The SDF GNU social instance is new, and there are only a handful of semi-regular users right now, so the Public timeline sometimes seems a bit dead. The Network timeline is a bit busier, and it has activity from remote users, so it's a bit better. Sometimes, though, the best place to look for interesting new people is //somewhere else//. | Yes, it's all well and good to know how to follow people -- but how do you find people to follow? The SDF GNU social instance is new, and there are only a handful of semi-regular users right now, so the Public timeline sometimes seems a bit dead. The Network timeline is a bit busier, and it has activity from remote users, so it's a bit better. Sometimes, though, the best place to look for interesting new people is //somewhere else//. |
| |
| * The [[https://gnu.io/social|GNU social website]] links to some of the largest public servers: https://gnu.io/social/try/ | * The [[https://gnu.io/social|GNU social website]] links to some of the largest public servers: https://gnu.io/social/try/ |
| Joining groups is done in much the same way as [[gnu_social_on_sdf#following_users|following users]]. You may either: | Joining groups is done in much the same way as [[gnu_social_on_sdf#following_users|following users]]. You may either: |
| |
| * visit the group's page and click the "Join" button, or | * visit the group's page and click the “Join” button, or |
| * visit your profile page and click the "+Remote" button under the GROUPS section in the right-hand pane, then enter the URL of the group's page into the dialog. | * visit your profile page and click the “+Remote” button under the GROUPS section in the right-hand pane, then enter the URL of the group's page into the dialog. |
| |
| There is an !SDF group, and it's as good as any for trying this out. The group's page is [[https://gs.sdf.org/group/sdf|"https://gs.sdf.org/group/sdf"]]. | There is an !SDF group, and it's as good as any for trying this out. The group's page is ''[[https://gs.sdf.org/group/sdf|https://gs.sdf.org/group/sdf]]''. |
| |
| ==== Finding Groups ==== | ==== Finding Groups ==== |
| |
| All of the groups hosted on SDF GNU social can easily be browsed by clicking the GROUPS link in the PUBLIC section of the navigation pane, or by directing your browser to [[https://wm.sdf.org/gs/groups|"https://wm.sdf.org/gs/groups"]]. | All of the groups hosted on SDF GNU social can easily be browsed by clicking the GROUPS link in the PUBLIC section of the navigation pane, or by directing your browser to ''[[https://wm.sdf.org/gs/groups|https://wm.sdf.org/gs/groups]]''. |
| |
| Other nodes have group directories as well, which you can usually access by visiting "{nodeURL}/groups" (ex: "https://quitter.se/groups"). Most group directory pages will have a search dialog in case you're looking for a specific topic. | Other nodes have group directories as well, which you can usually access by visiting ''{nodeURL}/groups'' (ex: ''https://quitter.se/groups''). Most group directory pages will have a search dialog in case you're looking for a specific topic. |
| |
| Hopping from site to site and browsing/searching their group directories can be a bit of a pain, though. Another resource to try is [[http://federation.skilledtests.com|Erkan Yimlaz's wiki]], which contains a user-editable list of federated groups from all over the fediverse: [[http://federation.skilledtests.com/List_of_federated_GNU_social_groups.html|"http://federation.skilledtests.com/List_of_federated_GNU_social_groups.html"]]. Finally, you could try [[http://gstools.org|GSTools]], which has a search tool for groups as well as users. | Hopping from site to site and browsing/searching their group directories can be a bit of a pain, though. Another resource to try is [[http://federation.skilledtests.com|Erkan Yimlaz's wiki]], which contains a user-editable list of federated groups from all over the fediverse: ''[[http://federation.skilledtests.com/List_of_federated_GNU_social_groups.html|http://federation.skilledtests.com/List_of_federated_GNU_social_groups.html]]''. Finally, you could try [[http://gstools.org|GSTools]], which has a search tool for groups as well as users. |
| |
| ===== Your Account ID ===== | ===== Your Account ID ===== |
| |
| There are two forms of account ID that you can put on your business card or email signature or home page or wherever else people put things like "@zippyThePinhead on Twitter!". You can either use the URL of your GNU social profile page: | There are two forms of account ID that you can put on your business card or email signature or home page or wherever else people put things like “@zippyThePinhead on Twitter!”. You can either use the URL of your GNU social profile page: |
| |
| |https://gs.sdf.org/ //nickname//| | |https://gs.sdf.org/ //nickname//| |
| Or, the GNU social server provides a [[https://webfinger.net/|WebFinger]] ID for you, which looks like an email address: | Or, the GNU social server provides a [[https://webfinger.net/|WebFinger]] ID for you, which looks like an email address: |
| |
| |//nickname// @gs.sdf.org| | |//nickname//@gs.sdf.org| |
| |
| The WebFinger ID is used in GNU social for mentioning users on other nodes. There's more information on that up in the section on [[gnu_social_on_sdf#mentions_using|mentions]]. | The WebFinger ID is used in GNU social for mentioning users on other nodes. There's more information on that up in the section on [[gnu_social_on_sdf#mentions_using|mentions]]. |
| </file> | </file> |
| |
| You'll need to replace "nickname" with your nickname, and "userIDnumber" with your user ID number on SDF GNU social. Wait, what? My user ID //number//? Yes. If you visit your profile page, in the right-hand column, under STATISTICS, you'll see that your User ID is given as a number. That's the number you need to use in your WebFinger link relations. | You'll need to replace “nickname” with your nickname, and “userIDnumber” with your user ID number on SDF GNU social. Wait, what? My user ID //number//? Yes. If you visit your profile page, in the right-hand column, under STATISTICS, you'll see that your User ID is given as a number. That's the number you need to use in your WebFinger link relations. |
| |
| ---- | ---- |
| ===== Understanding GNU social ===== | ===== Understanding GNU social ===== |
| |
| While GNU social allows you to do most of the same things you can do on other social media sites, there are some fundamental differences between the way things work on the federated OStatus network that GNU social uses ("The Fediverse") and the way they work on the closed virtual networks of, say, Facebook or Twitter. | While GNU social allows you to do most of the same things you can do on other social media sites, there are some fundamental differences between the way things work on the federated OStatus network that GNU social uses (“The Fediverse”) and the way they work on the closed virtual networks of, say, Facebook or Twitter. |
| |
| On Twitter/Facebook/Google+/&c.: | On Twitter/Facebook/Google+/&c.: |
| To some extent, each GNU social node is an island, a small Twitter or Facebook unto itself: you and the other users of SDF GNU social are visible to each other in the site directory, and the directory may be browsed or searched; when you post a public notice, everyone on SDF GNU social will see it in the Public Timeline, and all of those notices may be searched, replied to, repeated, and favored. | To some extent, each GNU social node is an island, a small Twitter or Facebook unto itself: you and the other users of SDF GNU social are visible to each other in the site directory, and the directory may be browsed or searched; when you post a public notice, everyone on SDF GNU social will see it in the Public Timeline, and all of those notices may be searched, replied to, repeated, and favored. |
| |
| But SDF GNU social is also part of a world-wide network of servers using the OStatus protocol to enable their users to follow each other, join groups, and send notices between their nodes. OStatus provides inter-node communication, but it does //not// make the Fediverse into a sort-of distributed SuperTwitter — unfortunately, I think a lot of new users expect it to. Hopefully this brief explanation of how OStatus //federation// works will help you to understand how and why GNU social behaves the way it does. | But SDF GNU social is also part of a world-wide network of servers using the OStatus protocol to enable their users to follow each other, join groups, and send notices between their nodes. OStatus provides inter-node communication, but it does //not// make the Fediverse into a sort-of distributed SuperTwitter -- unfortunately, I think a lot of new users expect it to. Hopefully this brief explanation of how OStatus //federation// works will help you to understand how and why GNU social behaves the way it does. |
| |
| ==== The Fediverse is Defined by Relationships ==== | ==== The Fediverse is Defined by Relationships ==== |
| On the federated network, user activity passes between nodes, but **only where relationships exist**. For example: | On the federated network, user activity passes between nodes, but **only where relationships exist**. For example: |
| |
| If "archibald@server01" is //following// "lucinda@server02", copies of all of Lucinda's notices will be sent to server01 and stored there so that Archibald can read them. Archibald's fellow users on server01 benefit from this as well, because having Lucinda's notices stored in server01's database means that they will come-up in searches; if they include tags that users on server01 are following, then those users will see them in their Home Timelines; and all of Lucinda's notices can be repeated, favored, and replied-to by the users of server01. | If ''archibald@server01'' is //following// ''lucinda@server02'', copies of all of Lucinda's notices will be sent to server01 and stored there so that Archibald can read them. Archibald's fellow users on server01 benefit from this as well, because having Lucinda's notices stored in server01's database means that they will come-up in searches; if they include tags that users on server01 are following, then those users will see them in their Home Timelines; and all of Lucinda's notices can be repeated, favored, and replied-to by the users of server01. |
| |
| If Archibald replies to one of Lucinda's notices, his //reply// will be sent to server02 so that Lucinda can read and interact with it (as well as everyone else at server02), **but**, if no one on server02 is //following// Archibald, none of his other notices will be sent to server02, //because there's no relationship that requires them//. Remember, just because Archibald is following Lucy, that doesn't mean she's following him back! | If Archibald replies to one of Lucinda's notices, his //reply// will be sent to server02 so that Lucinda can read and interact with it (as well as everyone else at server02), **but**, if no one on server02 is //following// Archibald, none of his other notices will be sent to server02, //because there's no relationship that requires them//. Remember, just because Archibald is following Lucy, that doesn't mean she's following him back! |
| Furthermore, because all of your activity in the Fediverse is mediated through your home node, you cannot reply-to, favor, or repeat notices that you read while visiting other nodes. They //have to have been delivered to your node// in order for you to be able to interact with them. | Furthermore, because all of your activity in the Fediverse is mediated through your home node, you cannot reply-to, favor, or repeat notices that you read while visiting other nodes. They //have to have been delivered to your node// in order for you to be able to interact with them. |
| |
| This frustrating set of limitations is increasingly referred to as "The Federation Problem". The good news is, the GNU social developers //are// trying to come-up with solutions to the federation problem. The bad news is, they're not quite there yet. | This frustrating set of limitations is increasingly referred to as “The Federation Problem”. The good news is, the GNU social developers //are// trying to come-up with solutions to the federation problem. The bad news is, they're not quite there yet. |
| |
| ==== The Best Course ==== | ==== The Best Course ==== |
| |
| - <del>[[#fn-microblog-b|<sup>↑</sup>]] GNU social might look like a simple microblogging platform, but it really is a general-purpose social networking platform for any kind of media you can imagine. Some nodes are very limited in the kinds of media they support, while others support the publication and subscription various structured data items such as bookmarks, event notifications, polls, and questions, in addition to microblogs with media attachments.</del> | - <del>[[#fn-microblog-b|<sup>↑</sup>]] GNU social might look like a simple microblogging platform, but it really is a general-purpose social networking platform for any kind of media you can imagine. Some nodes are very limited in the kinds of media they support, while others support the publication and subscription various structured data items such as bookmarks, event notifications, polls, and questions, in addition to microblogs with media attachments.</del> |
| - <del>[[#fn-node-b|<sup>↑</sup>]]//"Node"// is in vogue at the time of this writing; in the past, //"instance"// was the preferred term, and you'll still see this used by folks who've been around for a while.</del> | - <del>[[#fn-node-b|<sup>↑</sup>]]//“Node”// is in vogue at the time of this writing; in the past, //“instance”// was the preferred term, and you'll still see this used by folks who've been around for a while.</del> |
| - <del>[[#who-is-local-b|<sup>↑</sup>]]How would you notice this? If you look at the destnation of the hyperlink on a user's name, it'll point to their home server. Anything other than "https://gs.sdf.org/..." is a user from another site.</del> | - <del>[[#who-is-local-b|<sup>↑</sup>]]How would you notice this? If you look at the destnation of the hyperlink on a user's name, it'll point to their home server. Anything other than “https://gs.sdf.org/...” is a user from another site.</del> |
| |
| $Id: gnu_social.html,v 1.12 2016/01/27 10:16:31 laemeur Exp $ | $Id: gnu_social.html,v 1.12 2016/01/27 10:16:31 laemeur Exp $<sup>1</sup> [[http://sdf.org/?tutorials/gnu_social|GNU Social on SDF]] - traditional link (using [[wp>Revision_Control_System|RCS]]) |
| [[http://sdf.org/?tutorials/gnu_social|GNU Social on SDF]] - legacy link <del>$Id: gnu_social.html,v 1.13 2020/08/11 14:40:49 papa Exp $</del><sup>1</sup> | |
| |
| <sup>1</sup>Replicated from the gnu_social.html,v 1.12 2016/01/27 text. | <sup>1</sup> Replicated from the gnu_social.html,v 1.12 2016/01/27 text. |
| |
| === Notes === | === Notes === |
| |
