pod.dou.bet

Search

Items tagged with: diaspora

insporation* iOS Beta App for Diaspora is here


Today I am proud to announce that the #insporation* project started by @Jonne Haß now has a beta #iOS app.

insporation* is a #Flutter based #diaspora client. Based von upcoming diaspora 0.8 API.
Get the beta on your iPhone or iPad. iOS v12.4 or higher up to the newest 14 is supported.

Remember: insporation* needs latest v0.8 of Diaspora. This is still unreleased but ready to test. - If you pod already has the ‚eight‘, ask you podmin to update to latest commit. If your pod still runs on a lower version, maybe your podmin likes to test the next major.

We love to hear from you. Test the app, give feedback, about performance, design and usability. Use the Beta-Feedback provided inside the TestFlight-App, give us GitHub-Issues or simply a direkt mail.

Get the iOS client by the official apple testflight app. Just open this link and follow the simple instructions
TestFlight Link

Image/photo

Git sources to contribute or for issues is here:
insporationon github
 

insporation* iOS Beta App for Diaspora is here


Today I am proud to announce that the #insporation* project started by @Jonne Haß now has a beta #iOS app.

insporation* is a #Flutter based #diaspora client. Based von upcoming diaspora 0.8 API.
Get the beta on your iPhone or iPad. iOS v12.4 or higher up to the newest 14 is supported.

Remember: insporation* needs latest v0.8 of Diaspora. This is still unreleased but ready to test. - If you pod already has the ‚eight‘, ask you podmin to update to latest commit. If your pod still runs on a lower version, maybe your podmin likes to test the next major.

We love to hear from you. Test the app, give feedback, about performance, design and usability. Use the Beta-Feedback provided inside the TestFlight-App, give us GitHub-Issues or simply a direkt mail.

Get the iOS client by the official apple testflight app. Just open this link and follow the simple instructions
TestFlight Link

Image/photo

Git sources to contribute or for issues is here:
insporationon github
 
Hey #diaspora #devs -- what does this error mean?

Failed discovery for user@example.com: ActiveRecord::RecordInvalid: Validation failed: Guid has already been taken

Thanks
 

Pod Update Announcement


Today, lot's of changes/updates occurred on the back-end server.
  • Nodejs to v12.15 from v10.19
  • Diaspora to v0.7.13.0 from v0.7.12.0
  • Peertube to v2.1.0 from v2.0.0
  • Gitea to v1.11.0+1-gc95d9603e from v1.11.0+rc2-19-ge48b460a0
  • YOURLS to v1.7.6 from v1.7.4
If you run into any problems, please let me know ASAP.

Tag cloud:
#nota404mn #node #nodejs #diaspora #peertube #gitea #updates #yourls
 
fixes an issue where missing image link fields caused an exception. Please update.

#pod feeder #pod feeder v2 #feeds #rss #atom #diaspora
 

Diaspora Maintenance


I have lots of updates to install on the server so I am going to take it down for a backup. Will take approximately 1.5 hours to complete starting now!

#diaspora #server #maintenance #nota404mn
 

Diaspora Maintenance


I have lots of updates to install on the server so I am going to take it down for a backup. Will take approximately 1.5 hours to complete starting now!

#diaspora #server #maintenance #nota404mn
 

Nota.404.Mn Announcement


Starting today, I have made a few changes to this diaspora pod that may or may not affect you. The only ssl protocol that I have enabled is TLSv1.2 (because of a snafu, TLSv1.3 is no longer available), the ssl cipher suites available are: EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH, and protocols h2 and http/1.1 are available. #nota404mn #diaspora #security #admin
 
2018-01-31

A #Desirable #Diaspora #Feature

#TagList


A screen that shows what #tags are in use in a given #pod,
and the count of the times it has been used.

A bonus would be to see the same,
within a date-range (so that you can see what is popular,
say, over the last 60 days).

Made necessary by current inability to see what tags are in use;
or which are most popular.

The former results in tag-waste; confusion; and inaccuracy.

e.g.

For Amateur Radio, is it?

Right now, it's up to each person to wildass-guess.


Other Diaspora Nits (~alt link~)
 

Are you willing to contribute some money to help diaspora*s development?





Hey awesome diaspora* community! Today I'm asking you a very special question. At the moment, the development speed of the diaspora* project is quite slow. It looks like this is not only because not many people are interested in contributing to diaspora*, but also because the volunteers who compose the core team don't have enough time to do the review work needed, adding more delays to everything.

The core team is doing all lot of background work. They maintain all the official services: the website, the HQ pod, our Discourse and the wiki. They do the sysadmin job of installing and keeping those services up to date, but they also are the moderators who fight spam. They answer many questions and help developers, podmins, and users. They do the release management and push out new versions of diaspora*. But most important of all, they are the ones doing the final reviews, the very important task of checking the code submitted by other contributors, helping them improve the code, and then integrate it inside diaspora* for everyone.

This is a lot of work, and even if it is less visible than new features, this work is critical because if it is not done, the project is stuck.

We unfortunately reached a point where the limited time of the core team as volunteers slows down the diaspora* development. Two very important features, the accounts migration and the API, are waiting for a review for several weeks while the core team currently is busy with all the tasks listed above, as well as other tasks like the creation of a new official website. To go forward, the diaspora* project needs someone from the core team to be dedicating more time to these diaspora* background jobs at least a couple of hours per month more.

So, to the important question...

If a diaspora* core team member would set up a Patreon or something similar that allows them to fund more time to do the maintenance and review work, would you contribute to that fund?

A big warning here: This is not about paying someone to be able to decide what they will be working on. There is BountySource if you want to support the development of specific features with money. This is about allowing someone to have some dedicated time to work on the maintenance tasks of the diaspora* project, mainly reviews. This core developer will be the one who will choose how they will spend their time, most of the time. But as the core team members are the ones who are the most aware of what's going on with the project, I think we can trust them to do the best choices to improve diaspora* development speed.

So, would you give a few bucks monthly? I would totally do!

#diaspora #diaspora-dev #contribute #donate
 

Word of Caution for Apache2 and diaspora* Admins


I'd hate to think that I am the only one experiencing this. DO NOT USE APACHE2 v2.4.41 without disabling TLS1.3 and diaspora together, or your connections will timeout!
On Apache2 v2.4.38, if I curl -v [url=https://nota.404.mn]https://nota.404.mn[/url] I get this:
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):

Once you upgrade to v2.4.41, and do the same command:
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Unknown (8):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Client hello (1):
* TLSv1.3 (OUT), TLS Unknown, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=nota.404.mn
*  start date: Sep  2 15:44:07 2019 GMT
*  expire date: Dec  1 15:44:07 2019 GMT
*  subjectAltName: host "nota.404.mn" matched cert's "nota.404.mn"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
* Using Stream ID: 1 (easy handle 0x55df26b776b0)
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
> GET / HTTP/2
> Host: nota.404.mn
> User-Agent: curl/7.58.0
> Accept: */*
> 
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):

Tag cloud


#apache #apache2 #diaspora #update #ondrej #ppa #tls13 #tlsv13 #tlsv1.3 #podmin #server #ubuntu
 

#peer-to-peer #websites


#Zeronet

#IPFS

So -- watching the above tech evolve, I am wondering;
how do distributed / federated websites handle singular complex back-end databases that are used to serve the site up?

Unlike #diaspora pods -- where unique instances of #databases share parts of the overall data; I am asking how you take 1 given #dynamically updated database-served site; and share that data through Many distributed peer-to-peer #nodes of the same #website.
  • Does data have to federate along like Diaspora (where federation issues illustrate missing posts, lagging posts, large gaps in post streams, etc)? I mean, I can deal with that for ditzy social media "stuff" -- but for real life customer data?
  • If the backend data is distributed, how is it secured? I see the #blockchain approach used by zeronet -- but I also watch all of the #bitcoin/#ethereum #hacked #exchanges as well -- something that will become even more prevalent as #cryptocurrency (and other reasons to #hack blockchain tech) takes hold. I can't expose customers to that; where the data is then sitting in 100 other user's computers.
  • How about large #videos, that get served up?
    Do copies of the videos get #distributed everywhere as well, as I assume they do?
    (and what is the long term bandwidth issues to the peer-to-peer net when that takes off?)
Anyone here actually setting up peer-to-peer sites that are more than straight js/css/html with data that really needs to be protected ... beyond d* pods, that is?

Image/photo

#thanks
#programming
#website
#data
 
So I need ideas to help recover data from a mechanical drive that failed Saturday.

Data on the drive


Approximately 2750 Gigabytes of music, videos, and photos

Content Story


This is a really low blow. The drive housed 10 years worth of personal videos converted from VHS tapes and music I’ve collected and converted over the years.

Signs and Symptoms


There were no warnings: in the middle of a movie I was watching, the drive suddenly became unavailable. I walk into my office and I hear a procession of a series of two clicks. The drive appears to be and is no longer mountable.

HELP


At this point, I haven’t come to terms with my decision that none of this data is backed up anywhere and would be a monumental loss personally and I only have myself to blame; having said that, I’m looking for any tips, tricks or resources to help minimize the damage.

Thank you in advance. #data #datarecovery #loss #death #seagate #diaspora #nota404mn
 
I haven't done one of these in a while, but since we have so many new people I thought I'd cast a wide net. These are the tags I follow. Whether you're #newhere or #oldhere if we share an interest let me know!

#activism #aesoprock #agot #asoiaf #astronomy #australia #automation #battlestargalactica #beer #bernie #berniesanders #bostonterrier #btv #burlington #cider #cloud #collabora #comics #computing #containers #cosmology #cubesats #danger5 #darkcaracal #debian #deepdream #deepspacenine #deviantart #diaspora #dieantwoord #diy #django #docker #dogs #drugs #ds9 #el-p #encryption #español #faithnomore #fedora #floridaman #fnm #foss #freedom #freedombox #freesoftware #gameofthrones #geek #gibberfish #gnupg #google #gpg #grillz #grrm #hackathon #hailmarymallon #hbo #headytopper #hema #hiphop #holdfast #hplovecraft #hzsogood #interplanetary #jiujitsu #jpl #kempo #kenpo #killermike #kurzgesagt #letsencrypt #libre #linux #lovecraft #martialarts #mastodon #microbrew #microbrews #mikepatton #mindlessselfindulgence #minecraft #minetest #minio #mixedmartialarts #mma #mongodb #nasa #netflix #netherlands #netneutrality #newengland #newhere #nextcloud #nonprofit #npr #onlyoffice #openpgp #opensource #openstack #owncloud #pancrypticon #perl #pgp #physics #pineapplefund #pipod #pitbull #pitbulls #pod feeder #podmin #potus #privacy #programming #python #rap #raspberrypi #raspberrypi2 #raspberrypi3 #raspbian #redhat #retropie #roleplaying #rpgs #rtj #rtj2 #rtj3 #runthejewels #sadtrombone #scaleway #schadenfreude #sci-fi #science #scifi #scotus #searx #security #sifrp #smbc #space #stanleythoughts #startgate #startrek #strangerthings #surveillance #sysadmin #sysadmins #tails #tech #technology #techsoup #thecoup #themartian #theymightbegiants #thugnotes #tmbg #tor #trump #trumpspoilers #ubuntu #universityofvermont #unix #usa #uvm #vermont #vmware #vt #webcomic #webrtc #websockets #weirdal #weirdalyankovic #westeros #winteriscoming #xkcd #xmpp #zfs
#newhere #oldhere #activism #aesoprock #agot #asoiaf #astronomy #australia #automation #battlestargalactica #beer #bernie #berniesanders #bostonterrier #btv #burlington #cider #cloud #collabora #comics #computing #containers #cosmology #cubesats #danger5 #darkcaracal #debian #deepdream #deepspacenine #deviantart #diaspora #dieantwoord #diy #django #docker #dogs #drugs #ds9 #el-p #encryption #espaΓ±ol #faithnomore #fedora #floridaman #fnm #foss #freedom #freedombox #freesoftware #gameofthrones #geek #gibberfish #gnupg #google #gpg #grillz #grrm #hackathon #hailmarymallon #hbo #headytopper #hema #hiphop #holdfast #hplovecraft #hzsogood #interplanetary #jiujitsu #jpl #kempo #kenpo #killermike #kurzgesagt #letsencrypt #libre #linux #lovecraft #martialarts #mastodon #microbrew #microbrews #mikepatton #mindlessselfindulgence #minecraft #minetest #minio #mixedmartialarts #mma #mongodb #nasa #netflix #netherlands #netneutrality #newengland #nextcloud #nonprofit #npr #onlyoffice #openpgp #opensource #openstack #owncloud #pancrypticon #perl #pgp #physics #pineapplefund #pipod #pitbull #pitbulls #pod feeder #podmin #potus #privacy #programming #python #rap #raspberrypi #raspberrypi2 #raspberrypi3 #raspbian #redhat #retropie #roleplaying #rpgs #rtj #rtj2 #rtj3 #runthejewels #sadtrombone #scaleway #schadenfreude #sci-fi #science #scifi #scotus #searx #security #sifrp #smbc #space #stanleythoughts #startgate #startrek #strangerthings #surveillance #sysadmin #sysadmins #tails #tech #technology #techsoup #thecoup #themartian #theymightbegiants #thugnotes #tmbg #tor #trump #trumpspoilers #ubuntu #universityofvermont #unix #usa #uvm #vermont #vmware #vt #webcomic #webrtc #websockets #weirdal #weirdalyankovic #westeros #winteriscoming #xkcd #xmpp #zfs
 
I've decided to package pod_feeder_v2 to make it easier to install and use. You can now run pip install pod-feeder-v2 instead of downloading the source from git, and it will be available as numbered releases from this point forward.

Importantly, the scripts in the root of the git repo are symlinked to maintain backward compatibility, but should be considered deprecated and will be removed in a future release. Please see the README for details on how to switch to using the new package.

#pod feeder #pod feeder v2 #diaspora #rss #python #pip #pypi
 
I've decided to package pod_feeder_v2 to make it easier to install and use. You can now run pip install pod-feeder-v2 instead of downloading the source from git, and it will be available as numbered releases from this point forward.

Importantly, the scripts in the root of the git repo are symlinked to maintain backward compatibility, but should be considered deprecated and will be removed in a future release. Please see the README for details on how to switch to using the new package.

#pod feeder #pod feeder v2 #diaspora #rss #python #pip #pypi
 
I've been compiling Plume for 2.5 hours from source.... man that is a long time to just set up. In hind sight, setting up diaspora was simple in comparison!
#plume #activitypub #diaspora #compile #rust
 

The poddery story





poddery.com ( #poddery stands for Pod Dery ) was started around 2010 (domain name was registered on 2010 December 07) by Joe Bivins. To place this in history of #diaspora,
1. The famous lecture "Freedom in The could" by Eben Moglen, was delivered on 2010 Feb 05.
1. This speech inspired 4 students of New York University’s Courant Institute (Illia Zhitomirskiy, Daniel Greppi, @Maxwell Salzberg and Raphael Sofaer) to launch a crowd funding campaign to replace #facebook on 2010 April 24.
1. The first developer preview was released on 2010 September 15 and first consumer alpha version was released on 2010 November 23. The first tag on the github repo dates 2010 December 2.

As you can see from these dates, poddery.com is one of the earliest diaspora pods. Possibly, third pod after joindiaspora.com and diasp.org (if you know another pod started before poddery.com, let me know in comments). When we organized our second Mini #Debian Conference in Pune in 2011, we opened an account in poddery.com (@Mini DebConf India) and its first post was on 2011 June 23.

We posted many photos of the events on this account and when we heard Joe Bivins was planning to close this pod on 2013 June 30, we did not want to lose these posts. We offered to take over the maintenance and launched Save Poddery Campaign in June 2013. We got around 50% of the target amount and with around 66% discount by KnightSwarm, we took over maintenance of poddery.com. We are running this service for about 6 years now. In between we added #xmpp service and last year #matrix.

You can follow the history of this service via @SavePoddery Campaign ** and @poddery.com updates accounts.

We are running our 3rd crowd funding campaign now. Thanks to everyone who contributed, money as well as time and effort to run the service.

Contribute to this campaign at https://fund.poddery.com


#savepoddery #fundpoddery #privacy #FreeSoftware #OpenSource #FOSS
 

The poddery story





poddery.com ( #poddery stands for Pod Dery ) was started around 2010 (domain name was registered on 2010 December 07) by Joe Bivins. To place this in history of #diaspora,
1. The famous lecture "Freedom in The could" by Eben Moglen, was delivered on 2010 Feb 05.
1. This speech inspired 4 students of New York University’s Courant Institute (Illia Zhitomirskiy, Daniel Greppi, @Maxwell Salzberg and Raphael Sofaer) to launch a crowd funding campaign to replace #facebook on 2010 April 24.
1. The first developer preview was released on 2010 September 15 and first consumer alpha version was released on 2010 November 23. The first tag on the github repo dates 2010 December 2.

As you can see from these dates, poddery.com is one of the earliest diaspora pods. Possibly, third pod after joindiaspora.com and diasp.org (if you know another pod started before poddery.com, let me know in comments). When we organized our second Mini #Debian Conference in Pune in 2011, we opened an account in poddery.com (@Mini DebConf India) and its first post was on 2011 June 23.

We posted many photos of the events on this account and when we heard Joe Bivins was planning to close this pod on 2013 June 30, we did not want to lose these posts. We offered to take over the maintenance and launched Save Poddery Campaign in June 2013. We got around 50% of the target amount and with around 66% discount by KnightSwarm, we took over maintenance of poddery.com. We are running this service for about 6 years now. In between we added #xmpp service and last year #matrix.

You can follow the history of this service via @SavePoddery Campaign ** and @poddery.com updates accounts.

We are running our 3rd crowd funding campaign now. Thanks to everyone who contributed, money as well as time and effort to run the service.

Contribute to this campaign at https://fund.poddery.com


#savepoddery #fundpoddery #privacy #FreeSoftware #OpenSource #FOSS
 
Image/photo
Thanks to @BADy , we have now a progress bar for https://fund.poddery.com campaign. And we have raised about 34% of the target with 48 more days to go. Lets know if you would like to help with promoting the campaign. If you know ruby/rails we need help with adding this directly to our diaspora instance.

#savepoddery #fundpoddery #poddery #diaspora #matrix #xmpp
 
Image/photo
Thanks to @BADy , we have now a progress bar for https://fund.poddery.com campaign. And we have raised about 34% of the target with 48 more days to go. Lets know if you would like to help with promoting the campaign. If you know ruby/rails we need help with adding this directly to our diaspora instance.

#savepoddery #fundpoddery #poddery #diaspora #matrix #xmpp
 
#diaspora #totp #twofactor #authentication

Opinion


I enabled Two-factor authentication just to see how it worked and it does do what it needs to do... however, it is incredibly annoying that as soon as I close the browser window, I have to re-log in and also get another TOTP code. So, disabling this for now.
 
Hola amigos y enemigos,

Diaspora has a design problem. Podmins can block users on their own pods, but there's no mechanism for blocking the content of users of other pods from ending up on their own. For example, a podmin cab block a racist troll from their pod, but they can't block that racist troll's public posts from another pod appearing on their own. Also, users who are banned from any given pod can just create a new account on a different pod and continue to plague the network.

I know that adding a feature to block external users to the diaspora codebase is unlikely to happen quickly, if at all. There may even be philosophical objections to "breaking" federation like this. So, for those who want this feature now, I started tinkering with a workaround solution: a small proxy server that sits between D* and its front-end web server which discards incoming posts from users on a blacklist. All a podmin need do is add the user's diaspora ID to their list, and henceforth none of that user's posts or comments will make it on to their pod. All that will be necessary to run it is to change a single port number in the web server configuration.

If you'd like to have a look, or maybe try it out for yourself, the project is hosted here. However, in its current state it should be considered highly experimental.

Before I conclude, I'd like to anticipate a couple of responses and address them:

First, it may be pointed out that you can accomplish the same effect by corrupting the user's public key on the local database. This is correct, but that might be both difficult and intimidating for inexperienced podmins. Also, it's not easily reversible. I think this solution is much more podmin-friendly.

Second, what ever happened to, like, free speech, man? I know some people will be strongly against the very idea of this on principal. To that, I say we must agree to disagree. D* already has mechanisms for podmins to silence and ban users, this is just expanding the scope. That, and it's totally voluntary.

Third, yes, this is a specific targeted attempt to de-platform Nazis. I don't apologize for that. I guess it would work just as well for paedophiles too. I'm not going to lose any sleep.

PS - I apologize to all of the Friendicans, SocialHomers, Hubzilloids, et al for the Diaspora-centric language in this post. Don't take it personally. Unless you're a Nazi. Then fuck you.

#diaspora #federation #podmins #censorship #abuse #trolling #racism #nazis #proxy #dreipfeil
 
#pod diaspora.u4u.org will be shutdown by the end of august (31.08.2019)

All data will be deleted!

Please backup your data and move to another #pod !!!!

#diaspora #podmin #shutdown #closed
 
#pod diaspora.u4u.org will be shutdown by the end of august (31.08.2019)

All data will be deleted!

Please backup your data and move to another #pod !!!!

#diaspora #podmin #shutdown #closed
 
#Podmins, I've included the scripts I've used to remediate fake accounts on our pod in the diaspora-scripts repo.

The first script, find-fakes.py will search the diaspora database for users that have no content and only a single log-in and write out the user ids to a file. You may specify --interval <days> to omit newly-created accounts.

The second script, purge-accounts.py will read in the list of user ids and either close (delete) or lock (disable) the accounts in bulk.

If you have no idea what this is all about, see this post.

#diaspora #spam #fakeaccounts
 
I've decided to re-write pod_feeder from the ground up in python3. The original perl version works (mostly), but it's kind of a mess, and there are some outstanding issues that would be annoying to fix.

If you'd like to follow along, here is the repo. If you have any feature requests, get them in now!

#pod feeder #diaspora #rss #python
 
I've decided to re-write pod_feeder from the ground up in python3. The original perl version works (mostly), but it's kind of a mess, and there are some outstanding issues that would be annoying to fix.

If you'd like to follow along, here is the repo. If you have any feature requests, get them in now!

#pod feeder #diaspora #rss #python
 
#Hello #People!
when the developers of diaspora will put a "do not like" button?
Perhaps diaspora must continue the capitalist thinking of facebook, by which they trap people from positive emotions... Like, like and more like ..

BUTTON DISLIKE!! FREE DISLIKE!!


P.D.: like if you like I do not like! hehe..

#diaspora #internet #developers #freesoftware #programing #php #freedom #social #red #
 

diaspora\* version 0.7.7.0 released!


As scheduled, a new minor release is now released. Over the past six weeks, we have managed to collect 30 commits made by 5 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


* As Facebook shut down their APIs to post into peoples timelines, the Facebook integration is now removed.
* Preliminary for the diaspora:// URI scheme has been added by supporting web+diaspora:// calls. More on this in a future release!

Updating


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.
Next minor freeze (0.7.8.0): 2018-11-18
Next release (0.7.8.0): 2018-11-25

diaspora\* Rapid Release: ICS feed, HTML version.
#diaspora #announcement #release #0770
 

diaspora\* version 0.7.7.0 released!


As scheduled, a new minor release is now released. Over the past six weeks, we have managed to collect 30 commits made by 5 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


* As Facebook shut down their APIs to post into peoples timelines, the Facebook integration is now removed.
* Preliminary for the diaspora:// URI scheme has been added by supporting web+diaspora:// calls. More on this in a future release!

Updating


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.
Next minor freeze (0.7.8.0): 2018-11-18
Next release (0.7.8.0): 2018-11-25

diaspora\* Rapid Release: ICS feed, HTML version.
#diaspora #announcement #release #0770
 
Later posts Earlier posts