Skip to main content

Search

Items tagged with: Diaspora


 
Bei #Friendica bekommt man sogar sämtliche Kommentare seiner Kontakte samt der entsprechenden Posts und der weiteren Kommentare angezeigt. Und es besteht eine Verbindung zu #Mastodon. Beides finde ich sehr gut.
Aber neben @Frank Dapor #podmin ist @Josh endlich mal jemand auf #Diaspora, von dem ich mir alle Posts von Friendica aus ansehen kann. Diaspora oder die meisten seiner Konten scheinen da zu blockieren.


 
Bild/Foto
#diaspora #joindiaspora #amigos #friends

After 8 months I have returned to diaspora, I hope to meet again all the friends I used to have in joindiaspora


 
Bild/Foto
#diaspora #joindiaspora #amigos #friends

After 8 months I have returned to diaspora, I hope to meet again all the friends I used to have in joindiaspora


 
#pod #podmin #diaspora #hetzner #vserver #server #inflation #strom

und schon wieder wird der Betrieb von Diaspora* teurer :(
Sehr geehrte(r) Frank,

seit Ende letzten Jahres haben sich die Bezugskosten für Strom drastisch erhöht. Diese globale Entwicklung ist in vielen Bereichen des täglichen Lebens bereits spürbar. Da sich in absehbarer Zeit keine Stabilisierung der Energiepreise abzeichnet, sehen wir uns leider gezwungen, die Preise zahlreicher Produkte um ca. 10 % anzuheben. Die Strom-/Klimapauschale für Colocation muss leider noch deutlich stärker angehoben werden.

Die Preisanpassung erfolgt zum 1. September 2022 für Neubestellungen. Sämtliche neue Preise für die aktuell angebotenen Produkte finden Sie ab dem 1. September 2022 auf unserer Website unter https://www.hetzner.com. Bei Produkten, die vor dem 1. September 2022 bestellt und bereit gestellt werden, berechnen wir erst ab dem 1. Januar 2023 den neuen Preis.

Kunden mit Bestandsprodukten profitieren ebenfalls bis zum 31. Dezember 2022 vom bisherigen Preis.

Um Ihnen größtmögliche Transparenz und Planungssicherheit zu geben, haben wir uns dazu entschlossen, über die Preisanpassungen für Bestandsprodukte bereits heute in dieser Nachricht zu informieren. Wir werden zu Beginn des 4. Quartals mit detaillierten Informationen auf Sie zukommen.

Wir sind überzeugt, dass wir Ihnen trotz der Preisanpassung unsere Produkte nach wie vor zu einem fairen Preis-Leistungs-Verhältnis anbieten können.

Falls Sie Ihren Vertrag dennoch nicht fortführen möchten, können Sie ihn innerhalb der regulären Kündigungsfrist über die entsprechende Administrationsoberfläche beenden.

Wir hoffen Sie können unsere Entscheidung nachvollziehen und bitten um Ihr Verständnis für diese Maßnahme.

Bei Rückfragen stehen wir Ihnen gerne zur Verfügung. Antworten auf häufig gestellte Fragen finden Sie unter https://docs.hetzner.com/de/general/others/price-adjustment oder wenden Sie sich an unseren Kundensupport. Verwenden Sie dazu bitte das Kontaktformular in Ihrer Administrationsoberfläche im Menüpunkt “Support”.

Mit freundlichen Grüßen

Hetzner Online


 
Hey podmins!

Please note that diaspora* is currently not compatible with Ubuntu 22.04, aka Jammy. Canonical decided to ship OpenSSL version 3 to everyone, and unfortunately, Ruby 2.7 is incompatible with OpenSSL 3. While there are some potential workarounds for that, we're currently unable to offer any help or support. So for now, please set up new pods using Ubuntu 20.04, and please do not upgrade your existing pods.

The next major release of diaspora* will support Ruby 3, and as soon as that is released (please do not ask for a timeline - we don't have one :)), you can upgrade your pods.

If you're already running a production pod on 22.04, and you somehow managed to get it running... please tell us how. We'd really like to know in case we get more support requests!

Thanks y'all.

#diaspora #podmin #podmins #ubuntu #jammy


 
Hey podmins!

Please note that diaspora* is currently not compatible with Ubuntu 22.04, aka Jammy. Canonical decided to ship OpenSSL version 3 to everyone, and unfortunately, Ruby 2.7 is incompatible with OpenSSL 3. While there are some potential workarounds for that, we're currently unable to offer any help or support. So for now, please set up new pods using Ubuntu 20.04, and please do not upgrade your existing pods.

The next major release of diaspora* will support Ruby 3, and as soon as that is released (please do not ask for a timeline - we don't have one :)), you can upgrade your pods.

If you're already running a production pod on 22.04, and you somehow managed to get it running... please tell us how. We'd really like to know in case we get more support requests!

Thanks y'all.

#diaspora #podmin #podmins #ubuntu #jammy


 
#podmin #diaspora #update

pod.dapor.net is now running on 0.7.18.0


Notes:

diaspora* version 0.7.18.0 released!
As announced, a new minor release is now released. Over the past three months, we have managed to collect 113 commits made by 3 contributors for this minor release.

A huge thanks to all the contributors from diaspora's amazing community! If you want to help make diaspora even better, please check out our getting started guide. Please see the changelog for a complete list of changes made in this release.

Notable Changes
We updated the recommended Ruby version to 2.7. If you followed our installation guides, run rvm install 2.7 to install it!
We updated to bundler 2 and rails 6.1.
Switched to sassc-rails which makes assets:precompile a lot faster.
HTML notification emails now contain the correctly formatted posts and comments.
Updating
For podmins, update instructions are available as usual in the wiki. For those of you who have been testing the release candidate, run git checkout master before the update to get back to the stable release branch.

If you are a user not running your own pod, there is nothing you need to do!


 
#Hallo ihr #alle!

Neu bin ich hier, aber nicht gänzlich neu auf #Diaspora. #neuhier

Dieser Account ist die Fortsetzung von @Amina, wo es je nach Geschmack auch schon interessante Dinge zu sehen gibt.

Ich bin eine #Frau, was ja an sich nix besonderes wäre, wenn mein Körper nicht männlich wäre. Also bin ich eine #transfrau

Momentan ist das hier (als Fortsetzung der alten Amina) mehr oder weiger themenbezogen, da alles, was mit #queer zu tun hat (denkt euch die entsprechenden Hashtags dazu), ein schwarzes Loch ist, das alle anderen Interessen aufsaugt. Das ist aber nicht Programm, sondern momentan einfach so.

So, jetzt werde ich unterbrochen... schnell ab der Post und bis später!


 
#podmin #diaspora #update

Die neueste diaspora*-Version ist v0.7.17.0, dein Pod verwendet v0.7.17.0.


 
Hallo an alle #neuhier 👋

Schön, dass ihr hier in die #Fediverse gefunden habt. Kommt rein und fühlt euch wohl.
Der unten genannte Link erklärt kurz die Fediverse, deren Dienste und Benutzung. Die dortigen Infos sind wirklich hilfreich am Anfang.

Hier vorab schon einige Tipps um den Einstieg oder die Orientierung in die Fediverse zu erleichtern:
- Die Fediverse besteht nicht nur aus Mastodon (siehe Link unten)
- Aus Gründen der Dezentralität nicht (nur) die großen und bekannten Instanzen benutzen
- Ein "Hallo bin neu hier" Beitrag mit dem Hashtag #neuhier wäre schön in dem man auch etwas über sich schreibt
- Das Ausfüllen seines Profils/Bio mit interessanten Infos über einen wie z.B. Interessen erleichtert das finden und folgen von neuen Kontakten ungemein

Hier nun der versprochene Link:

#Fediverse #Friendica #Misskey #Pleroma #Diaspora #Mastodon #Twitter #Facebook #Instagram #HowTo


 
Hallo an alle #neuhier 👋

Schön, dass ihr hier in die #Fediverse gefunden habt. Kommt rein und fühlt euch wohl.
Der unten genannte Link erklärt kurz die Fediverse, deren Dienste und Benutzung. Die dortigen Infos sind wirklich hilfreich am Anfang.

Hier vorab schon einige Tipps um den Einstieg oder die Orientierung in die Fediverse zu erleichtern:
- Die Fediverse besteht nicht nur aus Mastodon (siehe Link unten)
- Aus Gründen der Dezentralität nicht (nur) die großen und bekannten Instanzen benutzen
- Ein "Hallo bin neu hier" Beitrag mit dem Hashtag #neuhier wäre schön in dem man auch etwas über sich schreibt
- Das Ausfüllen seines Profils/Bio mit interessanten Infos über einen wie z.B. Interessen erleichtert das finden und folgen von neuen Kontakten ungemein

Hier nun der versprochene Link:

#Fediverse #Friendica #Misskey #Pleroma #Diaspora #Mastodon #Twitter #Facebook #Instagram #HowTo


 

Kein „Walled Garden“… aber trotzdem mit Jägerzaun


https://pepecyb.hu/2022/03/15/kein-walled-garden-aber-trotzdem-mit-jaegerzaun/

#Hubzilla #Diaspora #Fediverse
Kein „Walled Garden“…
aber trotzdem mit Jägerzaun


 

Kein „Walled Garden“… aber trotzdem mit Jägerzaun


https://pepecyb.hu/2022/03/15/kein-walled-garden-aber-trotzdem-mit-jaegerzaun/

#Hubzilla #Diaspora #Fediverse
Kein „Walled Garden“…
aber trotzdem mit Jägerzaun


 

How to Refer to Diaspora* Profiles Using Links

... and Otherwise --- Many Ways, Many Traps


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.

Three Recommended References


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:I recommend NOT using the "/people/" form of link as it is almost always useless to viewers.I explain this below.

Clickable profile reference:

@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.

How to enter


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 . 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: @[url=https://diaspora.permutationsofchaos.com/u/drldr]Lee Rothstein[/url]

Code Block
@[url=https://diaspora.permutationsofchaos.com/u/drldr]Lee Rothstein[/url]

Raw full username reference

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.

How to enter


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

User home-pod URL reference:

https://diaspora.permutationsofchaos.com/u/drldr
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.

How to enter


As a standard URL. Angle braces (<>) remove ambiguity for referencing a URL, though they are not strictly necessary here.
Lee Rothstein's profile page:  <[url=https://diaspora.permutationsofchaos.com/u/drldr>]https://diaspora.permutationsofchaos.com/u/drldr>[/url]

Renders as:
Lee Rothstein's profile page: https://diaspora.permutationsofchaos.com/u/drldr
----.

Generally do NOT use the /people/GUID/ reference


I 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/ reference

https://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.

How to enter


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:
<[url=https://diaspora.glasswings.com/people/3eefd570b6d001395a191eac510f7330>]https://diaspora.glasswings.com/people/3eefd570b6d001395a191eac510f7330>[/url]

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.

Bonus tip: Public Extended Bio visibility


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


 

Joindiaspora Shutdown is in ONE (1) Days


Joindiaspora will cease to be a active Diaspora pod on March 4, 2022.

If you’re waiting for a rescue or sitting on the fence, DO NOT WAIT.

Your options are reduced with any further delay.

What you should do NOW:
  • Create an archive of any data you wish to preserve from your Profile Settings page.
  • Find a new home on another Diaspora* or Fediverse instance NOW
  • Share your new location with your followers.
Do not expect miracles or a continuation, the Joindiaspora pod will be shut down SOON.

See also:

#SIGNALFLARE


I have moved from @Doc Edward Morbius (moved to Glasswings) (dredmorbius@joindiaspora.com) to @Doc Edward Morbius (dredmorbius@diaspora.glasswings.com).
#Joindiaspora #JoindiasporaCom #Diaspora #DiasporaMigration #Migration #Diaspora #Help #Tips #DataArchves #Archives #Plexodus


 

Joindiaspora Shutdown is in ONE (1) Days


Joindiaspora will cease to be a active Diaspora pod on March 4, 2022.

If you’re waiting for a rescue or sitting on the fence, DO NOT WAIT.

Your options are reduced with any further delay.

What you should do NOW:
  • Create an archive of any data you wish to preserve from your Profile Settings page.
  • Find a new home on another Diaspora* or Fediverse instance NOW
  • Share your new location with your followers.
Do not expect miracles or a continuation, the Joindiaspora pod will be shut down SOON.

See also:

#SIGNALFLARE


I have moved from @Doc Edward Morbius (moved to Glasswings) (dredmorbius@joindiaspora.com) to @Doc Edward Morbius (dredmorbius@diaspora.glasswings.com).
#Joindiaspora #JoindiasporaCom #Diaspora #DiasporaMigration #Migration #Diaspora #Help #Tips #DataArchves #Archives #Plexodus


 
I notice that some pods work more efficiently than others ?
Is this to do with the servers/technology used ?

#Diaspora
#Pluspora
#CheckIn
Not #newhere but trying another pod due to the closing of Pluspora.


 
I notice that some pods work more efficiently than others ?
Is this to do with the servers/technology used ?

#Diaspora
#Pluspora
#CheckIn
Not #newhere but trying another pod due to the closing of Pluspora.


 

Diaspora* Migration & Data Archival: Finding your First Remote-Pod Followers


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.
  • pod.orkz followed on 25 December 2013, but is now defunct.
  • pod.geraspora.de followed on 18 January 2014 and remains active.
  • diasp.eu followed on 31 March, 2014 and remains active.
  • diasp.de followed on 6 May, 2014, and remains active.
  • diaspora-fr.org followed on 22 July, 2014 and remains active
  • spyurk.am followed on 11 August, 2014 and remains active.
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


 

Finding your First Remote-Pod Followers


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.
  • pod.orkz followed on 25 December 2013, but is now defunct.
  • pod.geraspora.de followed on 18 January 2014 and remains active.
  • diasp.eu followed on 31 March, 2014 and remains active.
  • diasp.de followed on 6 May, 2014, and remains active.
  • diaspora-fr.org followed on 22 July, 2014 and remains active
  • spyurk.am followed on 11 August, 2014 and remains active.
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


 

Diaspora* Data Migration and Archival Lessons Learned


(So far)

This is a summary of my discoveries and learning over the past two months or so concerning Diaspora* data archives and references as well as JSON and tools for manipulating it, specifically jq.

It is a condensation of conversation mostly at my earlier Data Migration Tips & Questions (2022-1-10) thread, though also scattered elsewhere. I strongly recommend you review that thread and address general questions there.

Discussion here should focus on the specific information provided, any additions or corrections, and questions on how to access/use specific tools. E.g., how to get #jq running on Microsoft Windows, which I don't have specific experience with.

Archival Philosophy


I'm neither a maximalist nor minimalist when it comes to content archival. What I believe is that people should be offered the tools and choices they need to achieve their desired goal. Where preservation is preferred and causes minimal harm, it's often desirable. Not everything needs to be preserved, but too it isn't necessary to burn down every library one encounters as one journeys through life.

In particular, I'm seeking to preserve access for myself and others to previous conversations and discussions, and to content that's been shared and linked elsewhere. Several of my own posts have been submissions to Hacker News and other sites, for example, and archival at, say, the Internet Archive or Archive Today will preserve at least some access.

This viewpoint seems not to be shared by key members of the Diaspora* dev team and some pod administrators. As such, I'll note that their own actions and views reduce choice and agency amongst members of the Diaspora* community. The attitude is particularly incongruous given Diaspora*'s innate reliance on federation and content propagation according to the original specified intent of the content's authors and creators. This is hardly the first time Diaspora* devs have put their own concerns far above those of members of the Diaspora* community.

Information here is provided for those who seek to preserve content from their own profiles on Diaspora* servers likely to go offline, in the interest of maximising options and achieving desired goals. If this isn't your concern or goal, you may safely ignore what follows.

Prerequisites


The discussion here largely addresses working with a downloaded copy of Diaspora* profile data in JSON format.

It presumes you have jq installed on your system, and have a Bash or equivalent command-line / scripting environment. Most modern computers can offer jq though you will have to install it: natively on Linux, any of the BSDs, MacOS (via Homebrew), Windows (via Cygwin or WSL), and Android (via Termux). iOS is the only mass-market exception, and even there you might get lucky using iSH.

Create your archive by visiting your Pod's /user/edit page and requesting EXPORT DATA at the bottom of that page.

If you have issues doing so, please contact your Pod admin or other support contact(s). Known problems for some Joindiaspora members in creating archives are being worked on.
## Diaspora* post URLs can be reconstructed from the post GUID

The Diaspora* data extract does not include a canonical URL, but you can create one easily:

Post URL = /posts/

So for the GUID 64cc4c1076e5013a7342005056264835

We can tack on:
  • protocol: https://
  • host_name: pluspora.com Substitute your intended Pod's hostname here.
  • the string literal /posts/
to arrive at:

https://pluspora.com/posts/64cc4c1076e5013a7342005056264835

... which is the URL for a post by @Rhysy (rhysy@pluspora.com) in which I'd initially witten the comment this post is based on, at that post's Pluspora Pod origin.

Given that Pluspora is slated to go offline a few weeks from now, Future Readers may wish to refer to an archived copy here:
https://archive.ph/Y8mar

Once you have the URL, you can start doing interesting things with it.

Links based on other Pod URLs can be created


Using our previous example, links for the post on, e.g., diasp.org, diaspora.glasswings.com, diasp.eu, etc., can be generated by substituting for host_name:Simply having a URL on a pod does not ensure that the content will be propagated. A member of that pod must subscribe to the post first. In many cases this occurs through followers, though occasionally it does not.

You can trigger federation by specifically mentioning a user at that instance and having them request the page.
I'm not sure of when specifically federation occurs --- when the notification is generated, when the notification is viewed, or when the post itself is viewed. I've experienced such unfederated posts (404s) often as I've updated, federated, and archived my own earlier content from Joindiaspora to Glasswings. If federation occurs at some time after initial publication and comments the post URL and content should resolve, but comments made prior to that federation will not propagate.

(Pinging a profile you control on another pod is of course an excellent way to federate posts to that pod.)

Once a post is federated to a set of hosts it will be reachable at those hosts. If it has not yet been federated, you'll receive a "404" page, usually stating "These are not the kittens you're looking for. Move along." on Diaspora* instances.

(I'm not aware of other ways to trigger federation, if anyone knows of methods, please advise in comments.)

Note that comments shown on a post will vary by Pod, when and how it was Federated, and any blocks or networking issues between other Pods from which comments have been made. Not all instances necessarily show the same content, inconsistencies do occur.

Links to archival tools can be created by prepending their URLs to the appropriate link

Those will either show existing archives if they exist or provide links to submit the post if they do not.

Note that the Internet Archive does not include comments, though Archive.Today does, see: https://archive.is/almMw vs. [url=https://web.archive.org/web/20220224213824/https://pluspora.com/posts/64cc4c1076e5013a7342005056264835]https://web.archive.org/web/20220224213824/https://pluspora.com/posts/64cc4c1076e5013a7342005056264835[/url]

To include later comments, additional archival requests will have to be submitted.

My Archive-Index script does all of the above


See My current jq project: create a Diaspora post-abstracter.

https://diaspora.glasswings.com/posts/ed03bc1063a0013a2ccc448a5b29e257

That still has a few rough edges, but works to create an archive index which can be edited down to size. There's a fair bit of "scaffolding" in the direct output.

Note that the OLD and NEW hosts in the script specify Joindiaspora and Glasswings specifically. You'll want to adapt these to YOUR OWN old and newPod hostnames.

The script produces output which (after editing out superflous elements) looks like this in raw form:
## 2012

### May


**Hey everyone, I'm #NewHere. I'm interested in #debian and #linux, among other things. Thanks for the invite, Atanas Entchev!**

> Yet another G+ refuge. ...

<[url=https://diaspora.glasswings.com/posts/cc046b1e71fb043d>]https://diaspora.glasswings.com/posts/cc046b1e71fb043d>[/url] 
[Original]([url=https://joindiaspora.com/posts/cc046b1e71fb043d]https://joindiaspora.com/posts/cc046b1e71fb043d[/url]) :: [Wayback Machine]([url=https://web.archive.org/]https://web.archive.org/[/url]*/[url=https://joindiaspora.com/posts/cc046b1e71fb043d]https://joindiaspora.com/posts/cc046b1e71fb043d[/url]) :: [Archive.Today]([url=https://archive.is/https://joindiaspora.com/posts/cc046b1e71fb043d]https://archive.is/https://joindiaspora.com/posts/cc046b1e71fb043d[/url]) 

(2012-05-17 20:33)

----


**Does anyone have the #opscodechef wiki book as an ePub?  Only available formats are online/web, or PDF (which sucks).  I'm becoming a rapid fan of the #epub format having found a good reader for Android and others for Debian/Ubuntu.**

> Related:  strategies for syncing libraries across Android and desktop/laptop devices. ...

<[url=https://diaspora.glasswings.com/posts/e76c078ba0544ad9>]https://diaspora.glasswings.com/posts/e76c078ba0544ad9>[/url] 
[Original]([url=https://joindiaspora.com/posts/e76c078ba0544ad9]https://joindiaspora.com/posts/e76c078ba0544ad9[/url]) :: [Wayback Machine]([url=https://web.archive.org/]https://web.archive.org/[/url]*/[url=https://joindiaspora.com/posts/e76c078ba0544ad9]https://joindiaspora.com/posts/e76c078ba0544ad9[/url]) :: [Archive.Today]([url=https://archive.is/https://joindiaspora.com/posts/e76c078ba0544ad9]https://archive.is/https://joindiaspora.com/posts/e76c078ba0544ad9[/url]) 

(2012-05-17 21:29)
----

Which renders as:

2012

May


Hey everyone, I'm #NewHere. I'm interested in #debian and #linux, among other things. Thanks for the invite, Atanas Entchev!
Yet another G+ refuge. ...

https://diaspora.glasswings.com/posts/cc046b1e71fb043d
Original :: [url=https://web.archive.org/*/https://joindiaspora.com/posts/cc046b1e71fb043d]Wayback Machine[/url] :: [url=https://archive.is/https://joindiaspora.com/posts/cc046b1e71fb043d]Archive.Today[/url]

(2012-05-17 20:33)


Does anyone have the #opscodechef wiki book as an ePub? Only available formats are online/web, or PDF (which sucks). I'm becoming a rapid fan of the #epub format having found a good reader for Android and others for Debian/Ubuntu.
Related: strategies for syncing libraries across Android and desktop/laptop devices. ...

https://diaspora.glasswings.com/posts/e76c078ba0544ad9
Original :: [url=https://web.archive.org/*/https://joindiaspora.com/posts/e76c078ba0544ad9]Wayback Machine[/url] :: [url=https://archive.is/https://joindiaspora.com/posts/e76c078ba0544ad9]Archive.Today[/url]

(2012-05-17 21:29)


I've been posting those in fragmenents by year as private posts to myself to facilitate both federation and archival of the content. In chunks as Diaspora* has a 2^16^ / 65,536 byte per-post size limit. It's a slow slog but I've only one more year (2021) to manually process at this point, with post counts numbering up to 535 per year.

The Internet Archive Wayback Machine (at Archive.org) accepts scripted archival requests


If you submit a URL in the form of https://web.archive.org/save/<URL>, the Wayback Machine will attempt to archive that URL.

This can be scripted for an unattended backup request if you can generate the set of URLs you want to save.

Using our previous example, the URL would be:

[url=https://web.archive.org/save/https://pluspora.com/posts/64cc4c1076e5013a7342005056264835]https://web.archive.org/save/https://pluspora.com/posts/64cc4c1076e5013a7342005056264835[/url]

Clicking that link will generate an archive request.

(IA limit how frequently such a request will be processed.)

Joindiaspora podmins discourage this practice. Among the more reasonable concerns raised is system load.

I suggest that if you do automate archival requests, as I have done, you set a rate-limit or sleep timer on your script. A request every few seconds should be viable. As a Bash "one-liner" reading from the file DIASPORA_EXTRACT.json.gz (change to match your own archive file), which logs progress to the timestamped file run-log with a YYYYMMDD-hms format, e.g., run-log.20220224-222158:
time zcat DIASPORA_EXTRACT.json.gz |
    jq -r '.user .posts[] | "[url=https://joindiaspora.com/posts/]https://joindiaspora.com/posts/[/url]\(.entity_data .guid )"' |
    xargs -P4 -n1 -t -r ~/bin/archive-url |
    tee run-log.$(date +%Y%m%d-%H%M%S)

archive-url is a Bash shell script:
\#!/bin/bash

url=${1}

echo -e "Archiving ${url} ... "
lynx -dump -nolist -width=1024 "[url=https://web.archive.org/save/$]https://web.archive.org/save/$[/url]{url}"  |
    sed -ne '/[Ss]aving page now/,/^$/{/./s/^[  ]*//p;}' |
    grep 'Saving page now'

sleep 4

Note that this waits 4 seconds between requests (sleep 4), which limits itself to a maximum of 900 requests per hour. There is NO error detection and you should confirm that posts you think you archived actually are archived. (We can discuss methods for this in comments, I'm still working on how to achieve this.)

The script could be improved to only process public posts, something I need to look into. Submitting private posts won't result in their archival, but it's additional time and load.

There is no automated submission mechanism for Archive.Today of which I'm aware.

Appending .json to the end of a Diaspora* URL provides the raw JSON data for that post:


https://joindiaspora.com/posts/64cc4c1076e5013a7342005056264835.json

That can be further manipulated with tools, e.g., to extract original post or comment Markdown text, or other information. Using jq is useful for this as described in other posts under the #jq hashtag generally.

Notably:

As always: This is my best understanding


There are likely errors and omissions. Much of the behaviour and structure described is inferred. Corrections and additions are welcomed.

#DiasporaMigration #Migration #Diaspora #Help #Tips #JoindiasporaCom #jq #json #DataArchves #Archives


 

Useful Diaspora* jq recipes: Extract the last (or other specified) comment(s) on a post


if you want to re-write the most recent comment on a thread, and retrieve the original Markdown, you can fetch the post using its GUID URL with .json appended, then run it through a simple jq recipe:
curl -s '<post_url>.json' |
   jq -r '.interactions.comments[-1].text'

Say, for example, if you realise you'd just muffed your most recent contribution to a thread and wanted to rewrite it, but don't want to have to re-tag all the Markdown from scratch.

I'm using curl as the web transport and piping output to jq on a commandline. This is supported on Linux, the BSDs, MacOS, Windows (using Cygwin or WSL), and via Termux on Android. Sorry, iOS, here's a dime, go buy a real computer.

An example referencing a specific post:
curl -s '[url=https://diaspora.glasswings.com/posts/ed03bc1063a0013a2ccc448a5b29e257.json]https://diaspora.glasswings.com/posts/ed03bc1063a0013a2ccc448a5b29e257.json[/url]' |
    jq -r '.interactions.comments[-1].text'

Note that comments are indexed from either the start (beginning with [0]) or via negative values, the last ([-1] instance), and you can provide another offset if you're trying to access a specific post some number of values from the start or end. The third comment would be [2], the fourth most recent would be [-4].

Leave the iterator unspecified to select all comments:
jq -r '.interactions.comments[].text`

As before, the -r argument outputs raw text without JSON escaping of quotes and other characters. This avoids most post-retrieval processing, e.g., a sed script to remove quoted characters and the like.

And as I've mentioned previously, jq itself is an extraordinarily useful, if occasionally opaque, command-line tool for processing and parsing JSON data. Which happens to be how Diaspora* delivers much of its content.

This post is of course based on a comment I'd made to this earlier jq thread ... as a comment. Edited and adapted, but substantially similar.

https://diaspora.glasswings.com/posts/ed03bc1063a0013a2ccc448a5b29e257

#UsefulJqRecipes #jq #json #diaspora #tips


 

Useful Diaspora* jq recipes: Finding your most-engaged peers


One question I've had on Diaspora* is who it is I'm interacting with most often.

This is an extract to a Linux / Unix pipeline which will show the most frequent users within the "others_data.relayables" data.
jq -r '.others_data.relayables[].entity_data.author' |
    sort | uniq -c | sort -k1nr | cat -n | less

For those unfamiliar with scripting: after extractng the data, I'm passing it through a set of Linux utilities. "sort | uniq" is something of an idiom for tallying frequencies.

These indicate any 'like', 'comment', or 'poll' interactions, but not reshares, best I can tell. For the record, the summary:
$  jq -r '.others_data.relayables[].entity_type' archive.json |
    sort | uniq -c | sort -k1nr | cat -n
1  16319 like
 2  7979 comment
 3    67 poll_participation

I will allow that the profile most frequently interacting ... was something of a surprise.

I feel I can share my top 20 hosts / pods:
1    15937 pluspora.com
     2     2802 diasp.org
     3     2019 diaspora.glasswings.com
     4      996 joindiaspora.com
     5      666 social.isurf.ca
     6      361 diasp.eu
     7      206 diasporing.ch
     8      104 framasphere.org
     9       99 pod.geraspora.de
    10       92 hub.libranet.de
    11       64 diaspora.psyco.fr
    12       64 diaspora.ty-penguin.org.uk
    13       64 hey.iseeamess.com
    14       48 social.c-r-t.tk
    15       44 diaspora-fr.org
    16       42 nerdpol.ch
    17       40 pod.orkz.net
    18       39 diaspora.permutationsofchaos.com
    19       31 protagio.social
    20       30 societas.online

Some expected results and a few surprises there. Note that Pluspora provides an overwhelming amount of traffic, and Joindiaspora, despite its 300k members and 10 year history ranks only 4th overall. The recently-departed social.isurf.ca hit a rather storied number and ranked 5th overall.

And as I've mentioned previously, jq itself is an extraordinarily useful, if occasionally opaque, command-line tool for processing and parsing JSON data. Which happens to be how Diaspora* delivers much of its content.

#jq #json #Diaspora #UsefulJqRecipes #tips


 

My current jq project: create a Diaspora post-abstracter


Given the lack of a search utility on Diaspora*, my evolved strategy has been to create an index or curation of posts, generally with a short summary consisting of the title, a brief summary (usually the first paragraph), the date, and the URL.

I'd like to group these by time segment, say, by month, quarter, or year (probably quarter/year).

And as I'm writing this, I'm thinking that it might be handy to indicate some measure of interactions --- comments, reshares, likes, etc.

My tools for developing this would be my Diaspora* profile data extract, and jq, the JSON query tool.

It's possible to do some basic extraction and conversion pretty easily. Going from there to a more polished output is ... more complicated.
A typical original post might look like this, (excluding the subscribed_pods_uris array):
{
  "entity_type": "status_message",
  "entity_data": {
    "author": "dredmorbius@joindiaspora.com",
    "guid": "cc046b1e71fb043d",
    "created_at": "2012-05-17T19:33:50Z",
    "public": true,
    "text": "Hey everyone, I'm #NewHere. I'm interested in #debian and #linux, among other things. Thanks for the invite, Atanas Entchev!\r\n\r\nYet another G+ refuge.",
    "photos": []
  }
}

Key points here are:
  • entity_type: Values "status_message" or "reshare".
  • author: This is the user_id of the author, yours truly (in this case in my DiasporaCom incarnation).
  • guid: Can be used to construct a URL in the form of https://<hostname>/posts/<guid>
  • created_at: The original posting date, in UTC ("Zulu" time).
  • public: Status, values true, false. Also apparently missing in a significant number of posts.
  • text: The post text itself.
A reshare looks like:
{
  "entity_type": "reshare",
  "entity_data": {
    "author": "dredmorbius@joindiaspora.com",
    "guid": "5bfac2041ff20567",
    "created_at": "2013-12-15T12:45:08Z",
    "root_author": "willhill@joindiaspora.com",
    "root_guid": "53e457fd80e73bca"
  }
}

Again, excluding the .subscribed_pods_uris. In most cases, reshares are of less interest than direc posts.

Interestingly, I've a pretty even split between posts and reshares (52% status_message, that is, post).

My theory in creating an abstract is:
  • Automation is good.
  • It's easier to peel stuff off an automatically-created abstract than to add bits back in manually.
  • The compilation should contain only public posts and exclude reshares.
Issues:
  • It's relatively easy to create a basic extract:
jq '.user.posts[].entity_data | .author, .guid, .created_at, text

Adding in selection and formatting logic gets ... more complicated.

Among other factors, jq is a very quirky language.

Desired Output Format


I would like to produce output which renders something like this for any given posts:
Diaspora Tips: Pods, Hashtags & Following
For the many Google Plus refugees showing up on Diaspora and Pluspora, some pointers: ...
https://diaspora.glasswings.com/posts/a53ac360ae53013611b60218b786018b (2018-10-10 00:45)
What if any options are there for running Federated social networking tools on or through #OpenWRT or related router systems on a single-user or household basis?
I'm trying to coordinate and gather information for #googleplus (and other) users looking to migrate to Fediverse platforms, and I'm aware that OpenWRT, #Turris (I have a #TurrisOmnia), and several other router platforms can run services, mostly #NextCloud that I'm aware. ...
https://diaspora.glasswings.com/posts/91f54380af58013612800218b786018b (2018-10-11 07:52)
The original posts can of course be viewed at the URLs shown.

What this is doing is:
  • Extracting the first line of the post text itself.
  • Stripping all formatting from it.
  • Bolding the result by surrounding it in ** Markdown.
  • Including the second paragraph, terminating it in an elipsis ....
  • Including a generated URL, based on the GUID, and here parked on Glasswings. (I might also create links to Archive.Today and Archive.Org of the original content.)
  • Including the post date, with time in YYYY-MM-DD hh:mm resolution.
Including the month and year where those change might also be useful for creating archives.

Specific questions / challenges:

  • How to conditionally export only public posts.
  • How to conditionally export only status_message (that is, original) posts, rather than reshares.
  • How to create lagged "oldYear" and "oldMonth" variables.
  • How to conditionally output content when computed Month and Year values > oldMonth and oldYear respectively. Goal is to create ## .year and ### .month segments in output.
  • How to output up to two paragraphs, where posts may consist of fewer than two separate text lines, and lines may be separated by multiple or only single linefeeds \r\n.
  • Collect and output hashtags used in the post.
  • Include counts of comments, reshares, likes, etc. I'm not even sure this is included in the JSON output.
There might be more, but that's a good start.

And of course, if I have to invoke other tools for part of the formatting, that's an option, though an all-in-jq solution would be handy.

#jq #json #diaspora #scripting #linux


 

Diaspora Migration Tips and Questions Thread


I'm going to be posting suggestions and questions regarding migrating between and/or preserving Diaspora* profile data.

This is not a new announcements / follow thread.

Please do chip in with suggestions or corrections.

#DiasporaMigration #Migration #Diaspora #Help #Dips #JoindiasporaCom


 
Hi! Somebody here, who can share his experiences with diaspora-mobile client for android?
#android #diaspora


 
Hi! Somebody here, who can share his experiences with diaspora-mobile client for android?
#android #diaspora


 

Would you like diaspora to be better connected ...


so you can talk to more people?

#poll #survey #sondage #diaspora #fediverse #interchange


 

Would you like diaspora to be better connected ...


so you can talk to more people?

#poll #survey #sondage #diaspora #fediverse #interchange


 
#Frage zu #joindiaspora

Bei mir sind immer noch #Bilder / #Fotos verschwunden. Der #Podmin @podmin@joindiaspora.com antwortet nicht und auch über die #E-Mail Adresse (incoming+feneas-association-8-issue-@git.feneas.org) kommt auf #Anfrage keine #Antwort.
Gibt es noch eine andere #Möglichkeit mit jemandem in #Kontakt zu treten, der das #Problem lösen könnte? Weiß da jemand weiter?

#Diaspora #Bug #Code #Community #Danke


 
#Frage zu #joindiaspora

Bei mir sind immer noch #Bilder / #Fotos verschwunden. Der #Podmin @podmin@joindiaspora.com antwortet nicht und auch über die #E-Mail Adresse (incoming+feneas-association-8-issue-@git.feneas.org) kommt auf #Anfrage keine #Antwort.
Gibt es noch eine andere #Möglichkeit mit jemandem in #Kontakt zu treten, der das #Problem lösen könnte? Weiß da jemand weiter?

#Diaspora #Bug #Code #Community #Danke


 
New push to next-minor at Diaspora
  • Commit: Store signatures of AccountMigrations if the old person is local by Benjamin Neff
    That way it can be re-used when sending the AccountMigrations to other
    pods again if a message for the migrated account is received.

    fixes 7902
    closes 8309
  • Commit: Resend AccountMigration or AccountDeletion for closed recipients by Benjamin Neff
  • Commit: Update open_graph_reader gem by Thorsten Claus
    closes 8307
  • Commit: Change placeholder in translations for 8304 by Benjamin Neff
  • Commit: Change placeholder in translations for 8037 by Benjamin Neff
  • Commit: updated 82 locale files [ci skip] by Benjamin Neff
  • Commit: Change domain for poduptime by David Morley
    closes 8304
  • Commit: Remind the username in the reset password e-mail by flaburgan
    closes 8037
#diaspora push #diaspora next-minor push


 

Info | Veränderung bei meinen Friendica Account


Nach langem Abwägen habe ich beschlossen den Schwerpunkt meiner Aktivitäten im Fediverse wieder zu Diaspora zu verlagern. Das ist auf der einen Seite sehr schade, da ich in meiner Zeit hier auf Friendica einiges an tollen Leuten die Mastodon, Pleroma etc. kennengelernt habe zu denen der Kontakt nun nicht mehr ganz so gut sein wird. Auf der anderen Seite komme ich bei Diaspora was das Look & Feel und die Usabilty betrifft immer noch wesentlich besser zurecht als bei anderen Plattformen. Dazu kommt das sich der Kontakt zu meinen vielen Kontakten auf Diaspora auf technischer Sicht ziemlich verschlechtert hat seit ich zu Friendica gewechselt bin, so als wenn nicht alles was ich geschrieben habe dort ankam. Vielleicht hat die Federation auch ein wenig länger gedauert, ich weiß es nicht.

Als Notlösung lasse ich meine Beiträge auf Diaspora jetzt über den Friendica Account laufen, damit sie auch ins ActivityPub basierte Fediverse federiert werden und schaue ein, zwei mal am Tag hier bei Friendica herein. Und vielleicht schafft es ja auch Diaspora irgendwann ActivityPub zu unterstützen, die Hoffnung stirbt zuletzt.

Allen Diaspora, Friendica und Hubzilla Usern die meinen Friendica-Account in ihren Kontakten haben kann ich nur empfehlen ihn zu entfolgen und meinem Diaspora Account ravenbird@nerdpol.ch bzw. @ravenbird@nerdpol.ch zu folgen. Den da schaue ich zukünftig entsprechend sehr viel häufiger herein und reagiere somit auch schneller auf Beiträge und Kommentare.

Tags: #Info #Veränderung #Friendica #Diaspora #Fediverse #Federation #Look-and-Feel #Usability #ActivityPub #Umzug #Ravenbird #2021-10-24


 

Info | Veränderung bei meinen Friendica Account


Nach langem Abwägen habe ich beschlossen den Schwerpunkt meiner Aktivitäten im Fediverse wieder zu Diaspora zu verlagern. Das ist auf der einen Seite sehr schade, da ich in meiner Zeit hier auf Friendica einiges an tollen Leuten die Mastodon, Pleroma etc. kennengelernt habe zu denen der Kontakt nun nicht mehr ganz so gut sein wird. Auf der anderen Seite komme ich bei Diaspora was das Look & Feel und die Usabilty betrifft immer noch wesentlich besser zurecht als bei anderen Plattformen. Dazu kommt das sich der Kontakt zu meinen vielen Kontakten auf Diaspora auf technischer Sicht ziemlich verschlechtert hat seit ich zu Friendica gewechselt bin, so als wenn nicht alles was ich geschrieben habe dort ankam. Vielleicht hat die Federation auch ein wenig länger gedauert, ich weiß es nicht.

Als Notlösung lasse ich meine Beiträge auf Diaspora jetzt über den Friendica Account laufen, damit sie auch ins ActivityPub basierte Fediverse federiert werden und schaue ein, zwei mal am Tag hier bei Friendica herein. Und vielleicht schafft es ja auch Diaspora irgendwann ActivityPub zu unterstützen, die Hoffnung stirbt zuletzt.

Allen Diaspora, Friendica und Hubzilla Usern die meinen Friendica-Account in ihren Kontakten haben kann ich nur empfehlen ihn zu entfolgen und meinem Diaspora Account ravenbird@nerdpol.ch bzw. @ravenbird@nerdpol.ch zu folgen. Den da schaue ich zukünftig entsprechend sehr viel häufiger herein und reagiere somit auch schneller auf Beiträge und Kommentare.

Tags: #Info #Veränderung #Friendica #Diaspora #Fediverse #Federation #Look-and-Feel #Usability #ActivityPub #Umzug #Ravenbird #2021-10-24


 

Info | Veränderung bei meinen Friendica Account


Nach langem Abwägen habe ich beschlossen den Schwerpunkt meiner Aktivitäten im Fediverse wieder zu Diaspora zu verlagern. Das ist auf der einen Seite sehr schade, da ich in meiner Zeit hier auf Friendica einiges an tollen Leuten die Mastodon, Pleroma etc. kennengelernt habe zu denen der Kontakt nun nicht mehr ganz so gut sein wird. Auf der anderen Seite komme ich bei Diaspora was das Look & Feel und die Usabilty betrifft immer noch wesentlich besser zurecht als bei anderen Plattformen. Dazu kommt das sich der Kontakt zu meinen vielen Kontakten auf Diaspora auf technischer Sicht ziemlich verschlechtert hat seit ich zu Friendica gewechselt bin, so als wenn nicht alles was ich geschrieben habe dort ankam. Vielleicht hat die Federation auch ein wenig länger gedauert, ich weiß es nicht.

Als Notlösung lasse ich meine Beiträge auf Diaspora jetzt über den Friendica Account laufen, damit sie auch ins ActivityPub basierte Fediverse federiert werden und schaue ein, zwei mal am Tag hier bei Friendica herein. Und vielleicht schafft es ja auch Diaspora irgendwann ActivityPub zu unterstützen, die Hoffnung stirbt zuletzt.

Allen Diaspora, Friendica und Hubzilla Usern die meinen Friendica-Account in ihren Kontakten haben kann ich nur empfehlen ihn zu entfolgen und meinem Diaspora Account ravenbird@nerdpol.ch bzw. @ravenbird@nerdpol.ch zu folgen. Den da schaue ich zukünftig entsprechend sehr viel häufiger herein und reagiere somit auch schneller auf Beiträge und Kommentare.

Tags: #Info #Veränderung #Friendica #Diaspora #Fediverse #Federation #Look-and-Feel #Usability #ActivityPub #Umzug #Ravenbird #2021-10-24


 

Info | Veränderung bei meinen Friendica Account


Nach langem Abwägen habe ich beschlossen den Schwerpunkt meiner Aktivitäten im Fediverse wieder zu Diaspora zu verlagern. Das ist auf der einen Seite sehr schade, da ich in meiner Zeit hier auf Friendica einiges an tollen Leuten die Mastodon, Pleroma etc. kennengelernt habe zu denen der Kontakt nun nicht mehr ganz so gut sein wird. Auf der anderen Seite komme ich bei Diaspora was das Look & Feel und die Usabilty betrifft immer noch wesentlich besser zurecht als bei anderen Plattformen. Dazu kommt das sich der Kontakt zu meinen vielen Kontakten auf Diaspora auf technischer Sicht ziemlich verschlechtert hat seit ich zu Friendica gewechselt bin, so als wenn nicht alles was ich geschrieben habe dort ankam. Vielleicht hat die Federation auch ein wenig länger gedauert, ich weiß es nicht.

Als Notlösung lasse ich meine Beiträge auf Diaspora jetzt über den Friendica Account laufen, damit sie auch ins ActivityPub basierte Fediverse federiert werden und schaue ein, zwei mal am Tag hier bei Friendica herein. Und vielleicht schafft es ja auch Diaspora irgendwann ActivityPub zu unterstützen, die Hoffnung stirbt zuletzt.

Allen Diaspora, Friendica und Hubzilla Usern die meinen Friendica-Account in ihren Kontakten haben kann ich nur empfehlen ihn zu entfolgen und meinem Diaspora Account ravenbird@nerdpol.ch bzw. @ravenbird@nerdpol.ch zu folgen. Den da schaue ich zukünftig entsprechend sehr viel häufiger herein und reagiere somit auch schneller auf Beiträge und Kommentare.

Tags: #Info #Veränderung #Friendica #Diaspora #Fediverse #Federation #Look-and-Feel #Usability #ActivityPub #Umzug #Ravenbird #2021-10-24


 
My tests with #diaspora import #migration are running well.
If you want (or need to) move from your pod, I have good news. At least on my development machine I now can import migration files (the zipped json, you can download from your settings menu) as well as the zipped #photos file.

Don't hold your breath, but in the next days I will deploy an early test available for everyone to #societas.

@Fla has a nice new registration formula in the makes that will lead you from new registrations to the migration page. (Still need to adapt this)


 
My tests with #diaspora import #migration are running well.
If you want (or need to) move from your pod, I have good news. At least on my development machine I now can import migration files (the zipped json, you can download from your settings menu) as well as the zipped #photos file.

Don't hold your breath, but in the next days I will deploy an early test available for everyone to #societas.

@Fla has a nice new registration formula in the makes that will lead you from new registrations to the migration page. (Still need to adapt this)


 
#Hallo ihr #alle!

Neu bin ich hier, aber nicht gänzlich neu auf #Diaspora. #neuhier

Dieser Account ist die Fortsetzung von @Amina, wo es je nach Geschmack auch schon interessante Dinge zu sehen gibt.

Ich bin eine #Frau, was ja an sich nix besonderes wäre, wenn mein Körper nicht männlich wäre. Also bin ich eine #transfrau

Momentan ist das hier (als Fortsetzung der alten Amina) mehr oder weiger themenbezogen, da alles, was mit #queer zu tun hat (denkt euch die entsprechenden Hashtags dazu), ein schwarzes Loch ist, das alle anderen Interessen aufsaugt. Das ist aber nicht Programm, sondern momentan einfach so.

So, jetzt werde ich unterbrochen... schnell ab der Post und bis später!


 
Bild/Foto
#pod #podmin #cloud #server #hosting #diaspora

Wie lange ich bei den Preisanpassungen meine Server noch bei Hetzner / oder überhaupt betreiben kann ist mehr als fraglich


 
@Andrew Pam @Joseph Teller and other #podmins

Spam Accounts:
shop_hiddle@sysad.org
fashion_hiddle@iviv.hu
hiddle_quanaonam@sow.social

#spam #diaspora


 
@Andrew Pam @Joseph Teller and other #podmins

Spam Accounts:
shop_hiddle@sysad.org
fashion_hiddle@iviv.hu
hiddle_quanaonam@sow.social

#spam #diaspora


 
So, as @Thorsten Claus motivated me again to contribute to #diaspora, here I am. And here is my TODO list...
- Review all the open pull requests and see which ones can be integrated
- Answer the support on #Framasphere
- Upgrade #framasphere to 0.7.15.0, I still didn't do that
- Update Ubuntu on #diaspora-fr
- Fix some trivial bugs to put myself back in diaspora code
- Draw some mockups of the UI for pod migration and post them on discourse
- Actually implement the mockups with HTML
- See with Thorsten how we make them live
- Start thinking about the next major release, in case they are long term things to do
- Post about what I'm doing to show people that diaspora* isn't dead \o/

#diaspora-dev


 
So, as @Thorsten Claus motivated me again to contribute to #diaspora, here I am. And here is my TODO list...
- Review all the open pull requests and see which ones can be integrated
- Answer the support on #Framasphere
- Upgrade #framasphere to 0.7.15.0, I still didn't do that
- Update Ubuntu on #diaspora-fr
- Fix some trivial bugs to put myself back in diaspora code
- Draw some mockups of the UI for pod migration and post them on discourse
- Actually implement the mockups with HTML
- See with Thorsten how we make them live
- Start thinking about the next major release, in case they are long term things to do
- Post about what I'm doing to show people that diaspora* isn't dead \o/

#diaspora-dev


 
Ich beobachte immer gerne und regelmäßig den Hashtag #neuhier, weil ich es so toll finde, dass man hier so nett begrüßt wird und wie hilfsbereit alle sind. Leider wird das aber immer weniger.
Du meinst es gibt weniger Beiträge mit #neuhier oder meinste es wird weniger Hilfsbereitschaft präsentiert?
Früher haben sich mehr angemeldet. Dabei fällt doch #Facebook immer mehr in Ungnade und da müsste #Diaspora doch mehr Zulauf haben? Also woran liegt es? Ist Diaspora zu unbekannt oder geht die Post inzwischen viel eher bei #Mastodon ab?
Ja ich denke, Mastodon ist einfach viel populärer. Ich benutze es parallel, weil ich in beiden Systemen seine Vorzüge sehe. Auf diaspora* kann man viel besser längere und fruchtbare Diskussionen führen, in denen man vor allem auch mal was ausformulieren kannn (dieser Beitrag hat JETZT schon 824 Zeichen). Auf Mastodon erreicht man vielleicht ein größeres Publikum und hat gefühlt auch mehr "Zufallskontakte" als auf diaspora*.
Es gibt doch gerade im deutschsprachigen Raum viele engagierte Podmins oder sind diese Pods alle ausgelastet und nehmen keine neuen Nutzerinnen mehr auf?
Gibt es 'fjeden, aber tatsächlich nicht so viele. Wenn ich auf https://podupti.me/ mal filtere:
  • diaspora (halbwegs aktuelle Version nix älter als 0.7.10)
  • Registrierungen offen
  • mindestens 1 Monat existent
  • Deutschland
komme ich auf 14 Pods (und noch einer in der Schweiz). Also es ist jetzt nicht direkt eine Armee an Podmins, die dahinter steht. Für den Alltag ist das kein Problem, praktisch ist ja egal wo sich mein Pod befindet, solange ich eine gemeinsame Sprache mit dem Podmin teile. Aber für deine Idee…
Ich habe überlegt ob man mal statt Cryptopartys Onboarding-Partys für Diaspora machen müsste.
…aber für deine Idee der Onboarding-Parties sind 14 Podmins halt nicht soooo viel, wenn man die da "mit im Boot" haben will. Vielleicht lohnt es sich aber zu recherchieren, wo diese 14 Leute wohnen, wenn man mal so 'ne Onboarding-Party macht und jemand von denen wohnt in der Nähe kann man die eine Person vielleicht als Expertin dabei haben.
Is' aber alles eher ein Thema für nach der Pandemie oder?

Ich habe zumindest im Rahmen des #chaoscommunicationcongress hier und da schonmal jemandem einen diaspora*-Account übergeholfen, es ist halt ganz cool wenn man als interessiere Person jemanden hat dem oder der man Löcher in den Bauch fragen kann und der oder die dann auch genug Ahnung hat um das meiste davon zu beantworten (wie funktioniert das mit der Föderation? wer kann mein Profil sehen? wie viele Leute erreicht man so? Was bedeutet 'Aspekte'?…)
Schade wäre doch wenn dezentrale freie Netzwerke schon wieder total “out” sind im Mainstream …
Ich glaube dezentrale Netzwerke erleben einen Hype wie noch nie. Jahre lang dümpelte status.net / identi.ca / GNUsocial in einem Schattendasein vor sich hin, genutzt von ein paar Hardcore-Nerds, aber oft irgendwie parallel zu Twitter.
Diaspora* hat da meiner Meinung nach eine Tür aufgestoßen, aber der "Durchbruch" (erm naja *räusper* #wissensschon) kam halt mit #ActivityPub und Mastodon, denn dort tummeln sich neben Computer-Nerds (die über die Jahre auch einfach mehr geworden sind, Computer sind halt kein Nieschenthema mehr) auch genug politische Aktivistinnen, Künstler, Institutionen, Politikerinnen (naja nicht sooo viele XD) und so fort.
Kurzum: Mastodon bzw. das Fediverse um ActivityPub scheint der aktuelle Sieger im "Kampf" um dezentrale soziale Netzwerke zu sein. Ich benutze diaspora* trotzdem sehr gerne, weil hier andere Leute sind, weil man hier auch eher mal privater kommuniziert (auf Mastodon ist eher alles öffentlich) und und und. Also wie gesagt, ich sehe Vorzüge und Probleme mit beiden Netzwerken bzw. Softwaren.


 

diaspora* version 0.7.15.0 released!


We're happy to announce that a new minor release is now available. Over the past ten months, we have managed to collect 63 commits made by 10 contributors for this minor release.

A huge thanks to all the contributors from diaspora*'s amazing community! If you want to help make diaspora* even better, please check out our getting started guide. Please see the changelog for a complete list of changes made in this release.

Notable Changes

  • Support and recommend TOML as configuration format
  • Removed support for defunct Uni Heidelberg OSM tile server, Mapbox is now required if you want to show maps
  • Update mimemagic dependency that prevented new installations and updates

Updating


For podmins, update instructions are available as usual in the wiki. For those of you who have been testing the release candidate, run git fetch; git checkout main before the update to get back to the stable release branch.

#diaspora #announcement #release #07150


 

diaspora* version 0.7.15.0 released!


We're happy to announce that a new minor release is now available. Over the past ten months, we have managed to collect 63 commits made by 10 contributors for this minor release.

A huge thanks to all the contributors from diaspora*'s amazing community! If you want to help make diaspora* even better, please check out our getting started guide. Please see the changelog for a complete list of changes made in this release.

Notable Changes

  • Support and recommend TOML as configuration format
  • Removed support for defunct Uni Heidelberg OSM tile server, Mapbox is now required if you want to show maps
  • Update mimemagic dependency that prevented new installations and updates

Updating


For podmins, update instructions are available as usual in the wiki. For those of you who have been testing the release candidate, run git fetch; git checkout main before the update to get back to the stable release branch.

#diaspora #announcement #release #07150


 

Ahoi ihr Surferinnen und Surfer auf Diaspora wir müssen mal reden über unser Netzwerk hier...


Ich beobachte immer gerne und regelmäßig den Hashtag #neuhier, weil ich es so toll finde, dass man hier so nett begrüßt wird und wie hilfsbereit alle sind. Leider wird das aber immer weniger. Früher haben sich mehr angemeldet. Dabei fällt doch #Facebook immer mehr in Ungnade und da müsste #Diaspora doch mehr Zulauf haben? Also woran liegt es? Ist Diaspora zu unbekannt oder geht die Post inzwischen viel eher bei #Mastodon ab? Es gibt doch gerade im deutschsprachigen Raum viele engagierte Podmins oder sind diese Pods alle ausgelastet und nehmen keine neuen Nutzerinnen mehr auf? Ich habe überlegt ob man mal statt Cryptopartys Onboarding-Partys für Diaspora machen müsste. Schade wäre doch wenn dezentrale freie Netzwerke schon wieder total "out" sind im Mainstream ...