As communicated a few months ago I'll be shutting down the following #services:

• relay.iliketoast.net which is the default relay for the #Diaspora server software. This will happen at the end of July or soon after that time.
• iliketoast.net Diaspora pod. This will happen at the end of August, or soon after that time. Please export your data.

Oh hello #ActivityPub network from #Socialhome \o/

Finally flipped the switch! ActivityPub support is very alpha still but far enough that dogfooding is becoming the only efficient way forward.

Plus it's my birthday, so let this be a present to myself, after so much work to make this little project of mine multi-protocol, joining #Friendica and #Hubzilla in having the largest reach in the #Fediverse ;)

The account @jaywink@diaspodon.fr will not get new posts at some point in the future after a few announcements to followers - follow me here! Thanks @{https://diaspodon.fr/@dada} for offering me a home while building my AP support <3

boom6

This site is pure awesome: https://regex101.com/

Regexp testing, validation and on-the-fly editor. Makes regexp actually not painful.

Socialhome 0.9.0 released

Long overdue, this release brings a few long awaited features and privacy related improvements. A total of 105 commits went into this release by two authors, changing 175 files (4476 insertions, 1958 deletions).

This release makes #Socialhome and #GDPR friends. Users can now delete and export their data, and admins can publish terms and privacy documents.

Other main features include support for limited content, notifications on mentions, admin improvements, tag search and the new local content stream. See below highlights for more details.

Highlights

• Limited content is now supported 🙈 💪

Limited content can now be created using the web create form. Note, API does not currently allow creating limited content (except replies to limited content). Once create form is ported to the API, things should be refactored there, right now had no bandwidth to ensure both work.

Limited content is shown in the stream with a lock symbol. The create shows some extra fields for limited content. These include “recipients” and “include following”. Recipients is a comma separated list of target profile handles the limited content will be sent to. Include following will populate recipients (on save) with all the profiles that one follows. Later on we will add contact lists for better targeting.

Limited content visibilities can be edited. If someone is removed from the target recipients, a retraction will be sent to try and delete the content remotely from the target recipient.

Currently recipients must already be known to the server, in the future a remote search will be done if the profile is not known. Any known remote profile can be targeted - it is up to the receiving server to decide whether to accept it or not. For local profiles, those of visibility SELF (ie hidden) cannot be targeted.

There is also a new stream “Limited” available. It shows all limited content visible to you.

• Add “Local” stream which contains only content from users registered on the same server.

• Mentions are now parsed out of incoming remote content and locally created content.

Currently the only syntax supported is the #Diaspora mentions syntax, ie @Name. Currently Socialhome users can create mentions by using the syntax manually. UI layer will be added later to choose people using the standard @ syntax to trigger search.

• Searching for hashtags is now possible using the global search

• Admins can now add Terms of Service and Privacy Policy documents to the site. Default templates are provided in the admin. These can be published as is or modified to suit the site.

• Users can export their data from the account settings. In addition to user and profile data, this export contains a list of profiles followed, content (including shares and replies) and a zip file of image uploads. An email notification will be sent to the user once the export is ready for download from the account page.

• Add possibility to delete user account. Deletion is permanent and will delete all created content including uploaded images. Delete request for profile and related content will be sent to remote servers.

• Admin pages are now linked to from the new navbar cogs dropdown menu. New admin pages have been added for content and profiles.

• Many fixes to stabilize the resource usage of streams precaching.

See the full changelog here.

What's next?

Limited content initial support was one of the goals of this release, and that has now been done. One of the other most wished for features has been the possibility to follow tags. This will most likely be included very soon for the next release.

The one major feature that has been postponed for a long time is #ActivityPub support. To finally move this forward, it is likely that no other large features will be worked on for the next release other than following tags and adding ActivityPub support to the federation layer.

Source code hosting

This release will most likely be the last release done exclusively through #GitHub. Migration will soon happen to a #Gitlab instance. While development will happen through Gitlab, there will be mirroring to the current GitHub repository, so that contributing through that will also be possible.

What is Socialhome?

Socialhome is best described as a #federated personal profile with social networking functionality. Users can create rich content using #Markdown. All content can be pinned to the user profile and all content will federate to contacts in the federated social web. Currently federation happens using the Diaspora protocol. Federating using existing protocols means Socialhome users can interact with tens of thousands of other users.

Please check the official site for more information about features. Naturally, the official site is a Socialhome profile itself.

Official site: https://socialhome.network.

Contribute

Want to work on a #Django and #Vue.js powered social network server? Join in the fun! We have easy to follow development environment setup documentation and a friendly chat room for questions.

• Documentation
• Chat room info

#changelog #news #socialnetwork #thefederation #selfhosting

Testing mentions towards Socialhome - hey @[Jason Robinson 🐍🍻](/people/da323072-e566-4b6e-a8b6-b2bda0c6ace4)

Faces of the Federation — Jason Robinson of Socialhome

Jason Robinson was a long-term volunteer dev to the Diaspora project who made several important code contributions before deciding to roll his own federated platform. An avid Pythonista, Jason has specializes in Django development, and continues to tinker with decentralized communication.

https://medium.com/we-distribute/faces-of-the-federation-jason-robinson-of-socialhome-7f6aa0b77915

A cool interview with @[Jason Robinson](/u/jaywink)!

#socialhome #diaspora #federation

Socialhome version 0.5.0 released

Approximately one month since the previous release, #Socialhome 0.5.0 is out with 102 changed files, 2870 insertions and 999 deletions by 2 contributors.

For users there are only a few features added in this release, most of the work being internal refactoring and work in preparation for future features.

Please see the full changelog here.

New features

A few notes on feature highlights.

Shares in streams

Shares are now pulled up to the "Followed" stream. What this basically means is that when a person you follow shares something authored by a person you don't follow, the post will be pulled up in your stream by the share action.

Generally, you should only see a single post once. If you follow the author whose content was shared, that content has already been in your stream, and thus a share will not repeat it. Note however that since stream pre-calculation is a new thing, it is possible that content seen in the stream before this feature was added will pop up in a new share once more.

There are still some things to do for shares, these are being tracked in this issue.

Stream precaching

Related to "shares in streams", there was a lot of refactoring work to create the new base for how all streams function. This includes unifying lots of code and rewriting it so that in addition to pulling content out of the database, we can "precalculate" streams. This is done to ensure streams load super fast even if the calculations on what content the stream has are heavy.

The only stream that is currently precached is the "Followed" stream. Precaching means it will load as fast as the public stream even though we now include shares by non-followed users and include them only once - which would be a heavy calculation to do without precaching. The real benefit will come when custom user defined streams are available.

How would you like to configure the content in your stream?

GIF uploads

Yes, we love GIF's <3

Links in content

All links in content (whether textual, markdown or HTML) are now treated equally. They will all be used as candidates for OEmbed/OpenGraph fetches and all will be processed to add a target="_blank" to the link, forcing it to open in another tab/window.

Stream URL changes

All stream urls now live under /streams/, so for example followed stream is /streams/followed/. The old url's should still work until they are needed for something else.

Features coming up

Vue.js streams

Christophe Henry has been hard at work rewriting the current Django template + #jQuery based streams in #VueJS. The status of that work can be tracked here. We're hoping to replace the current stream frontend with the Vue streams within the coming months. This will drop a lot of legacy code and speed up development of new features, and will also mean our #API is fully complete for the stream features.

ActivityPub protocol support

This is still something we want to do as soon as some of the basic features are first implemented. Currently it looks like having it before the end of the year is slightly optimistic, but federating with for example #Mastodon using #ActivityPub will be a strong priority to get early next year.

Docker images

There has been some work on #Docker images to run a Socialhome instance. Will post more info as they are ready.

What is Socialhome?

Socialhome is best described as a #federated personal profile with social networking functionality. Users can create rich content using Markdown. All content can be pinned to the user profile and all content will federate to contacts in the federated social web. Currently #federation happens using the #Diaspora protocol. Federating using existing protocols means Socialhome users can interact with tens of thousands of other users.

Please check the official site for more information about features. Naturally, the official site is a Socialhome profile itself.

Official site: https://socialhome.network.

Contribute

Want to work on a #Django and Vue.js powered social network server? Join in the fun! We have easy to follow development environment setup documentation and a friendly chat room for questions.

• Documentation
• Chat room info

#changelog #news #socialnetwork #thefederation #selfhosting

Starting to unfollow people from this account, following instead from my #Socialhome account jaywink@jasonrobinson.me .. please if you want to see my posts, follow that account instead. I have not been posting from this account for a while.

Socialhome doesn't support private posts yet, so if you want to hit me up with those, please mention account.

Btw, for those on iliketoast.net. The pod will keep running until a migration process has been in place for some time, maybe even longer. I will update it to 0.7.0.0 in the coming days, apologies for taking such a long time.

https://twitter.com/SuperJoeMunday/status/905281591789879296

The Incredible Growth of #Python - #StackOverflow Blog

This #data is just awesome. Python is literally on fire, in a good way! In the "high-income" countries, on Stack Overflow, which is pretty much the de-facto for #programming knowledge, Python has overtaken not just #Java, but #JavaScript too, in terms of visits to questions. Before anyone says "wait that isn't a measurement of absolute popularity!". Nothing is, but this is a very strong metric to me, among the many that indicate Python is #trending trending and trending.

Good time to be a Python #developer!

Some quotes from the article:

June 2017 was the first month that Python was the most visited tag on Stack Overflow within high-income nations. This included being the most visited tag within the US and the UK, and in the top 2 in almost all other high income nations (next to either Java or JavaScript). This is especially impressive because in 2012, it was less visited than any of the other 5 languages, and has grown by 2.5-fold in that time.

With a 27% year-over year-growth rate, Python stands alone as a tag that is both large and growing rapidly; the next-largest tag that shows similar growth is R. We see that traffic to most other large tags has stayed pretty steady within high-income countries, with visits to Android, iOS, and PHP decreasing slightly.

Outside of high-income countries Python is still the fastest growing major programming language; it simply started at a lower level and the growth began two years later (in 2014 rather than 2012). In fact, the year-over-year growth rate of Python in non-high-income countries is slightly higher than it is in high-income countries.

https://stackoverflow.blog/2017/09/06/incredible-growth-python/

#FOSDEM 2018 - Call for participation

https://fosdem.org/2018/news/2017-09-03-call-for-participation/

#opensource

Socialhome is best described as a federated personal profile with social networking functionality. Users can create rich content using Markdown and even HTML/JS/CSS (if set as trusted user). All content can be pinned to the user profile and all content will federate to contacts in the federated social web. Currently federation happens using the Diaspora protocol with future plans to include at least ActivityPub as well. Federating using existing protocols means Socialhome users can interact with tens of thousands of other users.

-> https://github.com/jaywink/socialhome
-> https://socialhome.network

#python #diaspora #federation #open-source #free-software #foss [Jason Robinson](/u/jaywink)

#Socialhome v0.4.0 released

The focus of work lately has been implementing missing features for proper daily usage. One of these is allowing users to share content created by other people. This is now partially possible. Remote shares are now processed and users are able to create shares, but shares are not yet themselves taken into account when creating a stream. Will write another post related to the status with shares and how they will function.

Check out the release here: https://github.com/jaywink/socialhome/releases/tag/v0.4.0

Try it!

Registrations are open at https://socialhome.network . Please be aware some features are still missing, but otherwise the software is very stable. Let us know what you think if you decide to try it!

Participate

Are you a #Django, #Python or #VueJS coder? Want to build a social network? Check out the contribution guide and get in touch!

Changelog

Update notes

This release contains long running migrations. Please allow up to 10 minutes for the migrations to run, depending on your database size.

Added

• Allow user to change profile picture. (#151)

  Profile menu now has an extra option "Change picture". This allows uploading a new picture and optionally setting focus point for cropping a picture that is not square shape.

• Federate local profiles to remote followers on save. (#168)

• Process remote profiles entities on receive.

  Remote profiles were so far only created on first encounter. Now we also process incoming Profile entities from the federation layer.

• When following a remote profile, federate profile to them at the same time.

• It is now possible to expose statistics from a Socialhome node. This includes counts for users (total, 30 day, 6 month), local content and local replies. These will be exposed via the NodeInfo documents that for example the-federation.info node list consumes.

  By default statistics is off. Admins can switch the counts on by setting environment variable SOCIALHOME_STATISTICS=True and restarting Socialhome.

• Add user API token view. Allows retrieving an API token for usage in clients and tools. Allows also regenerating the token if it has been lost or exposed.

• Added bookmarklet to easily share external pages. The bookmarklet can be bookmarked from the 'Create' page. (#138)

  Sharing with the bookmarklet will copy the page url, title and optionally selected text into the create content text area. The bookmarklet is compatible with Diaspora, so for example the Firefox sharing service will work.

• Support receiving 'Share' entities. Show amount of shares on content. (#206)

• Show replies to shares on the original shared content. (#206)

• Add share endpoint to Content API. This enables creating and removing shares via the API. (#206)

• Allow sharing content. Clicking the share counter icon exposes a 'Share' button which when clicked will create a share. (#206)

• Allow unsharing content. Clicking the share counter icon exposes an 'Unshare' button (assuming the user has shared the content) which when clicked will remove the share. (#206)

• Federate local shares to remote nodes. (#206)

• There is now a 'My content' stream link in the navbar 'Streams' dropdown. This goes to your own profile all content stream.

• Add user preference for the new stream refactoring. If enabled, all streams that have a new version in progress will be rendered with the new frontend code based on Vue.js. (#202)

  Warning! The new frontent code doesn't have all the features of the current on yet.

• Content API has three new read only fields available:

  • local, boolean whether the content is local or remote.
  • reply_count, count of replies (including replies on shares)
  • shares_count, count of shares

• Make email notifications nicer by using HTML templates in addition to the plain text version. (#206)

  In addition to reply and follow notifications, send also when own content is shared.

Changed

• Breaking change. Content API results now return visibility as a string ('public', 'limited', 'site' or 'self'), not an integer.

Fixed

• There was no notification sent out when a local user followed a local user. This has now been fixed.

Removed

• Breaking change. Removed Content, Profile and Users API LIST routes. For now these are seen as not required for building a client and allow unnecessarily easy data mining.

• Removed content modal. Clicking timestamp in grid now directly loads the content detail view. (#162)

  Loading the content in a modal was an early experiment and didn't end out very usable.

• Removed reply button from replies. Technically, threaded replies are possible but the UI implementation is not done. Replying to a reply will be back once UI and federation layer will handle threaded replies properly.

#thefederation #federation

Anyone in #Helsinki / #Espoo / #Vantaa region interested in buying some old #breakbeat / #dnb #vinyl? Need to clear some room. All in fair to good condition (played in clubs).

Count of items:
- Breakbeat 61
- Drum'n'bass 56
- House/hiphop/other 10

Selling in bulk only, not single items. Make me an offer!

Disturbed - Just Stop

https://youtube.com/watch?v=NDic-BmaQkQ

<3

#Python overtakes #Java on (SO) popularity , fast gaining on #JavaScript

https://twitter.com/pycharm/status/902254848334319617

#Django #PyCharm #IDE #fundraising

Sigh, huge #UX problem with share replies on #Socialhome.. Damn you #diaspora protocol.. 😑

Currently it's like this:

The first reply is on the original content. The rest of the replies are on the reshare I made with my diaspora account.

I'm really not sure how to go with this. Separate reply "sections" by share with replies might be the only way.. Then provide a "reply" button for each share "section"... It's kind of annoying, but otherwise the replies are not guaranteed to ever go to the right place in diaspora protocol network. Which would be even more annoying.

#devdiary

[Fr] Hier, j'ai expliqué un partie de mon métier à ma môman avec Socialhome. Oh, coucou [Jason Robinson](/u/jaywink)
[En] Yesterday, me explained my profession to my mommy with Socialhome. Oh, hi [Jason Robinson](/people/da323072-e566-4b6e-a8b6-b2bda0c6ace4)

#mommy #love #myWork