As it's going to be closed: I'll delete my account on pluspora one of the next days.
Within the Fediverse I can now be found at
https://venera.social/profile/hck
.
(see this post for details: https://pluspora.com/posts/f09b32d07568013a3ddf005056264835 / https://nerdpol.ch/posts/10755682)
(see this post for details: https://pluspora.com/posts/f09b32d07568013a3ddf005056264835 / https://nerdpol.ch/posts/10755682)
Final post here and I want to say a heartfelt thank you for the Pluspora team team that saved us when G-Plus was taken away. You did so much for us and I’m sad to leave. :(
Please find me at Diasp.org from now on.
♥ ♥ ♥ ♥ ♥ to you all
📷 Mauro Savoca from Pexels
#Pluspora #G-Plus #MauroSavoca #Farewell #LastPost #ThankYou
(see this post for details: https://pluspora.com/posts/f09b32d07568013a3ddf005056264835 / https://nerdpol.ch/posts/10755682)
Diaspora* being what it is, there are four principle ways to refer to a specific profile. Three are useful, though each in different ways, the fourth ... usually is not.
With many people switching pods either in the recent past or near future, understanding the differences, and their pros and cons, is helpful. This is also useful in referring to troll, sockpuppet, and spam profiles, for people tracking and sharing those. Unfortunately, there's accumulated software and system cruft,, unexpected behaviours, and resulting confusion over this.
I'm discussing alternatives, pros, cons, results, and methods here.
TL;DR: I recommend in generaly using all three of these references for maximum clarity and utility. I'm picking on @Lee Rothstein here as I'm adapting this post from a comment I'd just made on their own migration announcement:
drldr@diaspora.permutationsofchaos.comI recommend NOT using the "/people/" form of link as it is almost always useless to viewers.
/people/GUID` reference: https://diaspora.permutationsofchaos.com/people/e85721a07a29013ab1b60242ac120002I explain this below.
@Lee Rothstein
Pro: Logged-in Diaspora* and Fediverse members can directly click on or hover over the link to add to / edit Aspects. Clicking on the link takes members directly to their Pod's instance of the profile's page.
Con: The profile's Pod is not directly viewable. Especially where people are changing Pods it is difficult to tell which Pod is being referenced. There are also problems with sock-puppet or spoof profiles impersonating others. Non-member / general public viewers are usually directed to a login/registration page. The actual username / handle name may not be apparent.
Because Diaspora* interprets and modifies even escaped and code-block versions of profile-link references, I cannot show the actual markup directly, but split it in two parts.
The general form is @name@pod-url. For any extant user, ... that reference even in backticks or a code block will be interpreted and the entered code won't be presented when a post is viewed. The transformation is also present when extracting source markup from a post's JSON link, requiring profile references to be edited when resubmitting / re-editing posts using this method.
Instead I approximate by leaving off the initial @ character, as here. Include the initial @ to create the actual link.
{drldr@diaspora.permutationsofchaos.com}
The intended rendering is achieved by including the above plus an added initial @:
@Lee Rothstein
That can be clicked on directly, a hover-card will appear, and your profile can be followed from there, or your profile's page opened directly.
If I do include the initial @, even within a code block or backtics, Diaspora* expands the user name as well, after submission (so you won't catch this in preview), even in a raw-code block, as here. Again, what was entered was @ followed immediately by `{drldr@diaspora.permutationsofchaos.com}:
Backticks: @Lee Rothstein
Code Block
@Lee Rothstein
drldr@diaspora.permutationsofchaos.com
Pro: This shows the username and pod unambiguously. It's possible to tell what Pod is being referenced. The string can be entered into Diaspora*'s Search box to find the associated profile. (Diaspora* seems to really like hiding Pod context...)
Con: The reference isn't a link and cannot be interacted with and won't directly bring up the user's profile.
Input the full user-handle reference leaving off the initial @ and surrounding curly braces ({}), inside backticks (`):
Lee Rothstein's raw profile: `drldr@diaspora.permutationsofchaos.com`
Renders:
Lee Rothstein's raw profile:
drldr@diaspora.permutationsofchaos.com
Pro: Universal access for all Diaspora* AND non-DIapsora* viewers. Provides a clickable link to bring up member's Pod homepage. Will show content even if the user, Pod, or individual posts are locally blocked. Can be viewed by the general public and non-Diaspora* members, or when not logged in to a Diaspora* Pod. Unambiguously shows the Pod the profile belongs to.
Con: The link isn't interactable except to members of the profile's own home Pod. Many members won't be able to use this page to add or remove the profile from Aspects, to Ignore or Unignore the profile, or to interact (Like, Comment, Share) posts and content.
As a standard URL. Angle braces (<>) remove ambiguity for referencing a URL, though they are not strictly necessary here.
Lee Rothstein's profile page: <https://diaspora.permutationsofchaos.com/u/drldr>
Renders as:
Lee Rothstein's profile page: https://diaspora.permutationsofchaos.com/u/drldr
----.
/people/GUID/ referenceI see this used often, and it is the link format generally presented internally on Diaspora* for profile references. In most cases it will redirect the reader to a login/registration page rather than the profile in question. This tends not to be useful or the intended result.
/people/GUID/ referencehttps://diaspora.permutationsofchaos.com/people/e85721a07a29013ab1b60242ac120002
I'll note that Lee's profile does seem to appear for me, proving that Diaspora*'s inconsistancies are inconsistently inconsistent. This is not usually the case and is not reliable behavour. An alternate profile shows, at least as of now, the more typical result, a login/registration page on Glasswings:
https://diaspora.glasswings.com/people/3eefd570b6d001395a191eac510f7330
Pro: The URL is easy to find for the submitter. This is the link that's generally shown when referring to a profile within Diaspora* Unfortunately it is useless to virtually everyone in the world.
Con: The link is typically useless to anyone not on the same Pod as you, and especially the general public. Most will be redirected to a login/registration page, which is probably not your intent.
This is usually the link given when seeing a profile reference on Diaspora* As noted, Lee's profile seems to work for me, though @tom grzyb's does not, so I'll use tom's to illustrate the more-typical behaviour. I believe the hexadecimal string is the profile's own GUID (globally unique identifier), so I'm calling this the "/people/<GUID/' method.
Selecting the URL from that reference I get:
<https://diaspora.glasswings.com/people/3eefd570b6d001395a191eac510f7330>
Rendered:
https://diaspora.glasswings.com/people/3eefd570b6d001395a191eac510f7330
Opening that link in an incognito browser session, where I'm logged out, I see the Glasswings login/registration page. This is ... not especially useful, and isn't my intended result.
Oddly, in the case of Lee's profile, I do see his profile page. I'm not sure why this is.
The /people/ version is ... highly unreliable and usually does not work in my experience.
Among information presented on a user's profile page may be an extended biography. This is not visible to the general public by default. In general I recommend you do provide information here, even if pseudonymous (as I have), especially when migrating between Pods. Of course if you have specific reasons not to do this, then don't.
**To make the extended biography information publicly visible, change the setting here: /profile/edit (Diaspora* Pods only, other Fedeiverse software may use different references).
For "Visibility of your extended profile" select "Public" to enable non-logged-in readers to be able to see your extended bio description, then save your profile settings by pressing the "Update Profile" button at the bottom of the page.
And if you've recently moved from another pod and want others to know your previous identity, this is a good place to leave tracks on your NEW profile. If you're planning to move pods in the future, you can also leave a reference here on your OLD profile.
See my own profile bios here as examples:
#Diaspora #Tips #DiasporaDev #Pluspora #Joindiaspora #Bio #Migration
Prima Framasphere, ora anche #JoinDiaspora ha chiuso, #Pluspora sta per chiudere...
Potrebbe essere la fine di #Diaspora 🙁 e un brutto colpo per l'idea di un #Fediverso plurale
* https://blacklight.tumblr.com/post/651320527722610688
* https://linuxnews.de/2022/03/social-network-diaspora-verliert-2-pods/
* https://pluspora.com/posts/f09b32d07568013a3ddf005056264835
ahoi zusammen, ich bin #NeuHier. war erst bei #pluspora, dann #tchncs, jetz versuch ich hier meine zelte aufzuschlagen... ich interessiere mich für #affinity, #dtp, #hägar, #linux, #musik, #scifi, #startrek und #starwars.danke für die einladung,@Welcome Diasporg!
auf dass ich hier länger bleiben kann/darf... :)
Say, for the sake of argument, that you've^†^ spent a few weeks trying to ensure that a set of URLs were archived at the Internet Archive's Wayback Machine, and you're aware that not all of those URLs were in fact archived, but you^†^ aren't sure just which ones were or were not.
The question might occur to you^†^, "Is there some way of testing whether or not a particular URL has or has not been successfully archived? Preferably in an automated manner?"
And the answer to that question would be YES!!! Yes there is!!!
What you^†^ are looking for are the Internet Archive Wayback Machine APIs, and specifically:
Wayback Availability JSON API
This simple API for Wayback is a test to see if a given url is archived and currenlty accessible in the Wayback Machine. This API is useful for providing a 404 or other error handler which checks Wayback to see if it has an archived copy ready to display.
Quoting from the Archive:
The API can be used as follows:
http://archive.org/wayback/available?url=example.com
which might return:
{
"archived_snapshots": {
"closest": {
"available": true,
"url": "http://web.archive.org/web/20130919044612/http://example.com/",
"timestamp": "20130919044612",
"status": "200"
}
}
}
if the url is available. When available, the url is the link to the archived snapshot in the Wayback Machine At this time, archived_snapshots just returns a single closest snapshot, but additional snapshots may be added in the future.
If the url is not available (not archived or currently not accessible), the response will be:
{"archived_snapshots":{}}
https://archive.org/help/wayback_api.php
It's also possible to query for a specific timestamp, though not AFAICT for saves within a date range.
You^†^ are now running that check on a set of 1300 or so URLs you'd^†^ hoped to have saved in the past two months or so.
See Also: Data Migration Tips and Questions.
Notes:
†: And my "you" I of course me "me".
#DataMigration #InternetArchive #APIs #Joindiaspora #JoindiasporaCom #Pluspora #Archival
TL;DR: I'd posted something both confusing and based on utter misunderstanding and confusion over Diaspora* post IDs (GUIDs) a couple of hours ago.
I suspect my conclusions are actually correct, though the example was simply wrong.
With the shutdown of Joindiaspora as a full-service Diaspora* instance, I'd thought a post made from a profile on a different Pod had originated from Joindiaspora. It hadn't, and several conclusions are wrong.
I'd also messed up the GUID references in the original and federated examples.
If you don't know what this is referring to, ignore the commotion. If you did see the earlier, now-deleted post, or worse, re-shared it (I've commented noting my error to those posts that I could find), my apologies.
I do think that there are some quirks in federation when a pod goes offline. I'll need to find better examples. (I do have numerous of these in my own post archives, so stay tuned.)
I will note that Diaspora* federation is weird and has interesting edge cases.
#Diaspora #Joindiaspora #Pluspora #Federation #Tips #ThatTimeIWasWrong
The Joindiaspora Pod is back online following maintenance in "limited-service mode". It is NOT a full-fledged Diaspora* instance any longer.
The screenshots I'm including here show the accessible portions of the site other than my direct messages (which appear as they did previously). Front page, Notifications, and Profile menu. Notifications are visible, and I'm curious as to whether or not @Doc Edward Morbius (moved to Glasswings) will see this mention...
Also featured is the delightful magenta colour theme I'd chosen to provide a visual cue to myself that I was on Joindiaspora rather than Glasswings over the past few weeks.
It is not possible to read or create comments on the site.
It is possible to view private communications / direct messages.
The front page now notes:
As such, all features are disabled, including the ability to post new content. However, you still can:
- Export your data, and initiate the account migration as soon it's done.
- Send and receive private messages.
- Delete your account.
- Manage your profile and account details.
I've tested to see if posts can be retrieved via JSON, and that appears not to be the case. My own first post to the site being:
https://joindiaspora.com/posts/cc046b1e71fb043d.json
Via curl -I I see an HTTP 301 (permanently moved) response.
A critical question in salvaging content is determining what content was federated, and where. This determines which of your posts were federated and whether all comments can be found at a given pod.
To do this, you can look to see what remote profile(s) and pod(s) followed you earliest. If that pod remains active, there's a good chance your full content and comments are probably fully represented there, after that initial follow date.
In my own case, I created my Joindiaspora profile and first posted in May, 2013.
My first non-Joindiaspora follow was from diasp.org on 15 December 2013. That pod remains active. It is most likely that full dicussions will exist there for posts made after that date.
To determine what remote pod(s) followed you earliest, go to your EARLIEST Notifications "Started Sharing", and look to see what pod the profile comes from (you'll have to hover over the username / avatar to do so. Scroll to the bottom of the page and click on the highest page number there for your earliest followers.
Note that broken avatar images almost always indicate dead pods. You can safely skip those.
Confirm that the pod itself is still online by loading its URL directly, e.g., https://diasp.org/ TLS/SSL security errors and non-resolution tend to be A Bad Sign.
It's possible that you were unfollowed by all profiles on a given pod, in which case your posts may not appear in full there. You'll need to verify this individually. The more followers you have on a given pod, the more likely your content is federated there.
I'm going to update my Archive-Index script to generate links for early-federating pods based on this information.
Also note that the following-date-by-pod information seems ... hard to extract if not impossible from your data extract. (I've yet to look into this.)
Another implication of this is that loss of large, long-lived pods has a knock-on effect across the entire Diaspora* network as history is wiped out. Mitigations against this would be very useful.
For more information or questions, see Diaspora Migration Tips and Questions Thread
https://diaspora.glasswings.com/posts/e0b4d980545c013a0103448a5b29e257
#DiasporaMigration #Migration #Diaspora #Help #Tips #JoindiasporaCom #Pluspora #PlusporaCom
This is my OLD and OBSOLETE profile on #pluspora, handle: @bonobo@pluspora.com
OLD and Dead and already smells funny:
https://pluspora.com/people/e5e09510aded013646c5005056268def
Still smelling funny 😝 but new and shiny is THIS account here: @bonobo@nerdpol.ch from which I’m posting, and hey, every post is FREE 😆 Costs only your time, and maybe your sanity, so better remove me from your aspects 👺
Well, now, it looks like the Outsourced Math server is down. BOY am I glad both JoinDiaspora and Pluspora are still up & running. If this becomes a frequent problem I might have to migrate pods yet again.
#newhere #signalflare #Pluspora #JoinDiaspora #refugee
#joindiaspora #pluspora #refugees #nota404mn #podmin
Hello there. If you need a place to go if you are losing your pod, I would recommend going to this site: https://diaspora.fediverse.observer/list
My favorite sites on there are:
@Daniel Doubet (backup) @danieldoubet (backup)
Note to plusporans - please download your image data!
Go to your Profile Settings here and scroll down to the bottom:
https://pluspora.com/user/edit
Then choose the Download Photos option. It'll take a few minutes to prepare, and then you can download the zip.
I'm working on a simple system which will then let you view and search your old profile here:
https://socialhome.network/p/f1ae2bb3-59c4-40cb-9784-5a01a6e5d6e6/
You do NOT need a SocialHome account to search for users (including yourself) and tags. This will be a working, searchable archive of all your posts and comments.
But each of us needs to preserve our own image data first for it to work. It only takes minutes to download the image data!
(Downloading the profile data may or may not work at all. I posted a lot of stuff, so I don't think my profile data export will ever succeed. It's like Google+ export woes all over again. But my 2000+ images downloaded in minutes!)
For the #GPlusRefugees out there:
♲ Filip H.F. "FiXato" Slagter - 2022-02-27 22:05:55 GMT
#SignalFlare: A reminder to follow me elsewhere if you want to stay in touch, as #JoinDiaspora will be going offline at the start of March:
You can follow me on:
- #Mastodon:@fixato@toot.cathttps://toot.cat/@FiXato
- #Friendica:@fixato@libranet.de@Fixato . https://libranet.de/profile/fixato/
- Overview of other profiles (which needs updating..): https://contact.fixato.org/
- My #Gemini blog: gemini://fixato.org
#GPlus #GooglePlus #PlusPora #CheckIn #PlusPoraRefugee #PlusPoraRefugees #GooglePlusRefugee #GPlusRefugee #GPlusRefugees #FiXato #Plexodus #JoinDiaspora
