Jonkman Microblog
  • Login
Show Navigation
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices by Mayel - ghost account (mayel@social.coop), page 89

  1. Robert Benjamin (rbenjamin@social.coop)'s status on Thursday, 03-May-2018 13:36:46 EDT Robert Benjamin Robert Benjamin

    Hey all you Masto warriors.

    Been working on a SUPER SECRET #facebookbreakup campaign to drive dissgruntled users into the welcoming arms of the Fediverse.

    Would appreciate any feedback on the draft campaign outline and to know who might be down to participate.

    https://docs.google.com/document/d/1PA62kmK_HGj1pfIvww-TWallGXCPXuf63wYoac6Wk8o/edit?usp=sharing https://social.coop/media/57wiFvtI9ix-Brk3SGA

    In conversation Thursday, 03-May-2018 13:36:46 EDT from social.coop permalink Repeated by mayel
  2. Mayel - ghost account (mayel@social.coop)'s status on Thursday, 03-May-2018 13:34:16 EDT Mayel - ghost account Mayel - ghost account

    You can now get a new "Appetizer" private server at just €3 per month on https://cloudvault.me/

    In conversation Thursday, 03-May-2018 13:34:16 EDT from social.coop permalink
  3. Mayel - ghost account (mayel@social.coop)'s status on Thursday, 03-May-2018 13:29:15 EDT Mayel - ghost account Mayel - ghost account
    • neville park

    @nev
    Mastodon is a great example of how to use your privilege to be able to use here for you and your family and friends

    In conversation Thursday, 03-May-2018 13:29:15 EDT from social.coop permalink
  4. Karl Schultheisz (kdsch@social.coop)'s status on Thursday, 03-May-2018 08:34:47 EDT Karl Schultheisz Karl Schultheisz

    Good morning, friends.

    I'm enjoying social.coop very much.

    I've been wanting to get involved with a cooperative, and assumed I'd need to choose one in my area (the vast majority of which are in banking or agriculture, far outside of my expertise). But there seem to be opportunities for many of us right here.

    I look forward to a future where our values can be embodied more fully in our work.

    In conversation Thursday, 03-May-2018 08:34:47 EDT from social.coop permalink Repeated by mayel
  5. Mayel - ghost account (mayel@social.coop)'s status on Thursday, 03-May-2018 06:29:27 EDT Mayel - ghost account Mayel - ghost account
    in reply to
    • Internet Turtle 🏴

    @tealturtle see https://www.gnu.org/software/artanis/manual/manual.html#org8920044

    In conversation Thursday, 03-May-2018 06:29:27 EDT from social.coop permalink
  6. Mayel - ghost account (mayel@social.coop)'s status on Thursday, 03-May-2018 06:27:52 EDT Mayel - ghost account Mayel - ghost account
    • Internet Turtle 🏴

    @tealturtle I'm not very familiar with Scheme, but depending on what this is for, you may want to use a framework like http://web-artanis.com/ or just find an ODBC library for Scheme

    In conversation Thursday, 03-May-2018 06:27:52 EDT from social.coop permalink
  7. Mayel - ghost account (mayel@social.coop)'s status on Thursday, 03-May-2018 06:11:21 EDT Mayel - ghost account Mayel - ghost account
    • Internet Turtle 🏴

    @tealturtle would help if you indicate the DB server, language and framework you're using

    In conversation Thursday, 03-May-2018 06:11:21 EDT from social.coop permalink
  8. Mayel - ghost account (mayel@social.coop)'s status on Thursday, 03-May-2018 05:49:23 EDT Mayel - ghost account Mayel - ghost account

    This.

    #Docker #Containers #Virtualisation #Linux #Servers #MicroServices #Technology #Glue #Complexity

    #xkcd source: https://xkcd.com/1988/

    https://social.coop/media/u56O-ZVh5IkwHu1wUv4

    In conversation Thursday, 03-May-2018 05:49:23 EDT from social.coop permalink
  9. winmine.exe (calvin@cronk.stenoweb.net)'s status on Wednesday, 02-May-2018 08:45:07 EDT winmine.exe winmine.exe
    in reply to
    • JordiGH

    @JordiGH I think curated timelines might be a good thing, provided if:

    1. the user has control

    2. the chronological timeline is still accessible

    then people can say use/write programs that curate in the way that they wish

    In conversation Wednesday, 02-May-2018 08:45:07 EDT from cronk.stenoweb.net permalink Repeated by mayel
  10. JordiGH (jordigh@mathstodon.xyz)'s status on Wednesday, 02-May-2018 08:44:08 EDT JordiGH JordiGH
    in reply to

    In other words, we don't need a computer algorithm for our timelines; human swarms can do this job just fine.

    In conversation Wednesday, 02-May-2018 08:44:08 EDT from mathstodon.xyz permalink Repeated by mayel
  11. JordiGH (jordigh@mathstodon.xyz)'s status on Wednesday, 02-May-2018 08:42:54 EDT JordiGH JordiGH

    So you know why social networks started curating timelines? Because as soon as the network gets too big, any timeline becomes a firehose and you start missing out on stuff.

    This reminds me again of #IRC chat rooms. Those too are firehoses, and worse, you have to be online to drink from them. And I just realised,, I like this fine.

    So I'm starting to think that I should lose my #FearOfMissingOut with Masto and just enjoy the ride. The good stuff will get boosted anyway so I'll end up seeing it.

    In conversation Wednesday, 02-May-2018 08:42:54 EDT from mathstodon.xyz permalink Repeated by mayel
  12. Mayel - ghost account (mayel@social.coop)'s status on Wednesday, 02-May-2018 21:39:21 EDT Mayel - ghost account Mayel - ghost account

    Temporal autonomy is a very important freedom and I would even say human right that's worth fighting for! It has so many unexpected positive side effects.

    Such as watching a video at 4:20am on a Wednesday where Terence McKenna blows our minds talking about how "biological systems [like humans] are amplifiers of quantum mechanical indeterminancy".

    https://www.youtube.com/watch?v=DGfZQJPczmI

    https://social.coop/media/AP0j8MPY00aUtdpW-wY

    In conversation Wednesday, 02-May-2018 21:39:21 EDT from social.coop permalink
  13. Ed Summers (edsu@social.coop)'s status on Wednesday, 02-May-2018 17:55:17 EDT Ed Summers Ed Summers

    archives all the way down.

    https://web.archive.org/web/*/http://archive.is/

    In conversation Wednesday, 02-May-2018 17:55:17 EDT from social.coop permalink Repeated by mayel
  14. neville park (nev@social.coop)'s status on Wednesday, 02-May-2018 15:36:55 EDT neville park neville park
    • 🏵️ virtualice 🏵️

    Big exciting social.coop stuff: @CobaltVelvet of hosting service #Maastodon needs to share the workload, is interested in making it a cooperative/transferring responsibility to us!

    Share thoughts: https://www.loomio.org/d/jgGJ8ucA/proposal-to-take-over-a-mastodon-hosting-service-hosting-external-instances-but-also-to-enable-the-creation-of-thematic-sister-coop-instances

    There is also a planned group chat, weigh in on what time is best for you: https://www.loomio.org/p/0k8ROFnX

    If you are not a member but would be interested in joining a co-op tech team, consider getting involved! Please boost for visibility~

    In conversation Wednesday, 02-May-2018 15:36:55 EDT from social.coop permalink Repeated by mayel

    Attachments

    1. Invalid filename.
      Proposal to take over a Mastodon hosting service, hosting external instances, but also to enable the creation of thematic sister coop-instances
      from Loomio
      I've been put in touch with Alice, who runs the Mastodon hosting service https://maastodon.net (currently hosting 38 instances with 171,652 accounts, including the mothership instance https://mastodon.social) and wants to either find a way to share the workload, or transfer it to another person/group. Of course, I suggested turning it into a co-op! And here's what she replied (and said I could share here to see if we might be interested): I really like that model and can only wish MaaS becomes a coop. Financially, the service is slightly profitable, the income over the previous two months was 182€ and 293€. The current servers cost 175€/month (209€ with taxes, it could be lowered with some changes) Technically, it works okay but require constant attention (mostly for mastodon.social's traffic bursts). It has some custom software that'd I'd be happy to continue working on, in a less pressured context, and see open-source. (i can't guarantee my time without a remuneration, but i would help the migration in any case). It's all already highly automated, including billing and instance setup. Given the right resources and maintenance/scaling it doesn't require much intervention except answering support tickets. My main issue with it is that i can't healthily handle such pressure alone, i just feel more and more crushed by a thing that's visibly too heavy. I think that while Alice might not have the energy to start up a co-op from scratch, she would probably be happy to transfer it to us (we'd give her something as a payout) and become a member of social.coop instead where she could be part of the soon-to-exist Tech Ops team. It seems to me that this ties in perfectly with our bigger vision for social.coop from the beginning (creating a model for user-controlled social platforms, to then inspire/help others do the same). And now that we've reached 1000 members, the question of scaling is relevant, and I personally think horizontal scaling is preferable (for both technical and social reasons). We could use a similar model as Q&A service StackExchange for creating new communities (see http://area51.stackexchange.com/faq) which could result in sister instances like art.social.coop, science.social.coop, or even aww.social rather than sticking with one increasingly noisy and general instance. As for the external instances already hosted by Alice: https://maastodon.net/instances/ they could be a secondary source of funds for social.coop which would help remunerate the ever-more-needed Tech Ops team. Of course, we could then prod the instance admins to see about turning them into #platformcoops (or becoming sister instances of social.coop just like the hypothetical aww.social) Imagine announcing that mastodon.social is now a #platformcoop! It's no #BuyTwitter but still pretty cool :wink: Another option, in case the whole social.coop collective doesn't want to take this on, woud be to create a small worker-coop to manage maastodon.net and possibly "outsource' the hosting/maintenance of social.coop to that coop. I'm keen to hear what people think, especially those members for which this would mean extra labour (even though the beauty here is collectivisation of effort, it might be 2x more work to maintain 10 instances compared to 1, not 10x), and so will wait for some feedback before starting any polls.
  15. Mayel - ghost account (mayel@social.coop)'s status on Wednesday, 02-May-2018 16:59:18 EDT Mayel - ghost account Mayel - ghost account
    • ivan

    @bernini welcome to the fediverse!

    In conversation Wednesday, 02-May-2018 16:59:18 EDT from social.coop permalink
  16. Matt Noyes (mattnoyes@social.coop)'s status on Wednesday, 02-May-2018 13:21:44 EDT Matt Noyes Matt Noyes
    in reply to

    https://www.loomio.org/d/jgGJ8ucA/proposal-to-take-over-a-mastodon-hosting-service-hosting-external-instances-but-also-to-enable-the-creation-of-thematic-sister-coop-instances

    https://www.loomio.org/d/FLB2801O/proposal-to-offer-social-coop-as-an-unofficial-tld-domain-name-for-social-cooperatives

    Also: https://www.loomio.org/d/wTcfWtus/do-you-have-the-skills-time-interest-to-join-the-tech-ops-team-

    In conversation Wednesday, 02-May-2018 13:21:44 EDT from social.coop permalink Repeated by mayel

    Attachments

    1. Invalid filename.
      Do you have the skills+time+interest to join the Tech Ops team?
      from Loomio
      Social.coop really needs a team of sysadmins/developers/devops to better manage the instance, and then there's the possibly of expanding (see the other thread about maastodon.net) so it would be really useful to have an idea of many members we have with the skills+time+interest for this. Some of the tools we use so far: Ubuntu Linux, Alpine Linux, Docker Swarm, Mastodon (Nginx, Postgres, Ruby, NodeJS...), Mediawiki, Wordpress Please comment with details about your skills and the tools you're familiar with.
  17. Matt Noyes (mattnoyes@social.coop)'s status on Wednesday, 02-May-2018 12:51:04 EDT Matt Noyes Matt Noyes
    • Mayel - ghost account
    • Robert Benjamin

    Social.coop members -- lots of discussion on Loomio right now that is relevant to the future of Social.Coop -- please check out important proposals by @mayel and @rbenjamin

    #whosecoop? #ourcoop! #socialcoop

    In conversation Wednesday, 02-May-2018 12:51:04 EDT from social.coop permalink Repeated by mayel
  18. Dan Phiffer (dphiffer@social.coop)'s status on Wednesday, 02-May-2018 10:59:06 EDT Dan Phiffer Dan Phiffer

    MaaS: Mastodon as a Service
    https://www.loomio.org/d/jgGJ8ucA/proposal-to-take-over-a-mastodon-hosting-service-hosting-external-instances-but-also-to-enable-the-creation-of-thematic-sister-coop-instances?utm_campaign=new_discussion&utm_medium=email&utm_source=thread_mailer

    In conversation Wednesday, 02-May-2018 10:59:06 EDT from social.coop permalink Repeated by mayel

    Attachments

    1. Invalid filename.
      Proposal to take over a Mastodon hosting service, hosting external instances, but also to enable the creation of thematic sister coop-instances
      from Loomio
      I've been put in touch with Alice, who runs the Mastodon hosting service https://maastodon.net (currently hosting 38 instances with 171,652 accounts, including the mothership instance https://mastodon.social) and wants to either find a way to share the workload, or transfer it to another person/group. Of course, I suggested turning it into a co-op! And here's what she replied (and said I could share here to see if we might be interested): I really like that model and can only wish MaaS becomes a coop. Financially, the service is slightly profitable, the income over the previous two months was 182€ and 293€. The current servers cost 175€/month (209€ with taxes, it could be lowered with some changes) Technically, it works okay but require constant attention (mostly for mastodon.social's traffic bursts). It has some custom software that'd I'd be happy to continue working on, in a less pressured context, and see open-source. (i can't guarantee my time without a remuneration, but i would help the migration in any case). It's all already highly automated, including billing and instance setup. Given the right resources and maintenance/scaling it doesn't require much intervention except answering support tickets. My main issue with it is that i can't healthily handle such pressure alone, i just feel more and more crushed by a thing that's visibly too heavy. I think that while Alice might not have the energy to start up a co-op from scratch, she would probably be happy to transfer it to us (we'd give her a token payout) and become a member of social.coop instead where she could be part of the soon-to-exist Tech Ops team. It seems to me that this ties in perfectly with our bigger vision for social.coop from the beginning (creating a model for user-controlled social platforms, to then inspire/help others do the same). And now that we've reached 1000 members, the question of scaling is relevant, and I personally think horizontal scaling is preferable (for both technical and social reasons). We could use a similar model as Q&A service StackExchange for creating new communities (see http://area51.stackexchange.com/faq) which could result in sister instances like art.social.coop, science.social.coop, or even aww.social rather than sticking with one increasingly noisy and general instance. As for the external instances already hosted by Alice: https://maastodon.net/instances/ they could be a secondary source of funds for social.coop which would help remunerate the ever-more-needed Tech Ops team. Of course, we could then prod the instance admins to see about turning them into #platformcoops (or becoming sister instances of social.coop just like the hypothetical aww.social) Imagine announcing that mastodon.social is now a #platformcoop! It's no #BuyTwitter but still pretty cool :wink: Another option, in case the whole social.coop collective doesn't want to take this on, woud be to create a small worker-coop to manage maastodon.net and possibly "outsource' the hosting/maintenance of social.coop to that coop. I'm keen to hear what people think, especially those members for which this would mean extra labour (even though the beauty here is collectivisation of effort, it's might be 2x more work to maintain 10 instances compared to 1, not 10x), and so will wait for some feedback before posting starting any polls.
  19. Mayel - ghost account (mayel@social.coop)'s status on Wednesday, 02-May-2018 10:12:49 EDT Mayel - ghost account Mayel - ghost account
    • Albatroz Jeremias

    @ajeremias I blocked Google Analytics and other trackers used by the services themselves using my firewall ;)

    In conversation Wednesday, 02-May-2018 10:12:49 EDT from social.coop permalink
  20. Wu-Lee (wulee@social.coop)'s status on Monday, 23-Apr-2018 04:56:24 EDT Wu-Lee Wu-Lee

    Public Service Announcement:

    When #linking to #Mastodon posts from #Loomio (and presumably other @ -expanding websites), you need to escape the @ in the username as '@'

    In conversation Monday, 23-Apr-2018 04:56:24 EDT from social.coop permalink Repeated by mayel
  • After
  • Before
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.