Notices tagged with github, page 18

Just discovered via this page https://github.com/ForkAwesome/Fork-Awesome/network/dependents that #ForkAwesome is powering 34 projects on #Github.

Now I think I'm going to sweat next time we release an update.

We've also passed the 2M hit per month on the CDN. An that's crazy.

Hmm, remind me again why centralizing git hosting was a good idea?

Even though I personally don't use it for anything anymore, still can't access numerous others' projects today.

#github #decentralize

https://mastodon.club/media/JIJOMtm3GiVgNpuKuFo

@selfagency
also directly blocked got
- a thread that started to engage about how and if to connect to others that take action againt companies involved with ICE

I mean it's your repo and you can do what you want with it. I just didn't understood why to limit the strategy to only leaving #github, and pushing anything that wants to expand down

hi @selfagency
you are the one behind the #github repo against ICE and calling to leave github, right?
thank you, then!
here just a feedback about what I didn't liked:
- I'm only a user that used github to write bug reports or such. When tryn to add myself to the list I made something wrong. An admin of the repo took this as an offensive and blocked me
also:
thread I started about:
- how github could be used as a plattform to protest and raise awarness befor leaving got directly closed

@cedricbonhomme
I understand that. I guess what I ment is not 'switch now', but more like 'you can start now a process that leads towards switching'

If you depend on others to be able to switch, starting a discourse about the links between #github, #microsoft and #ICE would be an example of how that process could start.
(so it also kinda started already :-p)
@phildini

@cedricbonhomme
but also keep in mind to switch away from #github, better sooner then later.
see for example:
https://github.com/selfagency/microsoft-drop-ice/blob/master/README.md
@phildini

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

@Wolf480pl you're entitled to that opinion of course, and I have no opinion either way. But it is a metric people seem to value. Besides which, a federated replacement for #GitHub could build it better metrics for the quality and sustainability of dependencies

Wrote a new post on me blog:

Move your #GitHub page to #GitLab Pages | goFLOSS!
https://gofloss.wordpress.com/2018/07/04/move-your-github-page-to-gitlab-pages/

Hopefully it's helpful to someone!

If you want to work version controlled on your #LaTex or #R project without big players like #GitHub involved, then take a look at the it services at your #university. Mine has a #GitLab instance for members.

@jeroenpraat
4. not moving away from github is supporting indirect fascism.
Microsoft said they are proud to support ICE. #GitHub is one of their product that makes microsoft look like a great company, since even 'all' the opensource devs are there.
The current situation requires to take position against any major company that supports ICE.

#fuckoffmicrosoft

here's a list of devs that are going to leave:
https://github.com/selfagency/microsoft-drop-ice
@Gargron