Jonkman Microblog
  • Login
Show Navigation
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices by bes (bes@io.schiessle.org)

  1. bes (bes@io.schiessle.org)'s status on Sunday, 29-Oct-2017 01:02:44 EDT bes bes
    in reply to
    Björn Schießle deleted notice {{tag:io.schiessle.org,2017-10-29:noticeId=247561:objectType=comment}}.
    In conversation Sunday, 29-Oct-2017 01:02:44 EDT from io.schiessle.org permalink
  2. bes (bes@io.schiessle.org)'s status on Sunday, 29-Oct-2017 01:01:02 EDT bes bes
    in reply to
    Björn Schießle deleted notice {{tag:io.schiessle.org,2017-10-29:noticeId=247560:objectType=comment}}.
    In conversation Sunday, 29-Oct-2017 01:01:02 EDT from io.schiessle.org permalink
  3. bes (bes@io.schiessle.org)'s status on Friday, 27-Oct-2017 11:37:05 EDT bes bes
    in reply to
    • ☠️ Grumpy Oldman
    • Max Mehl
    • bes
    @grmpyoldman @mxmehl @bes in Deutschland kann ich noch den Linuxtag in Chemnitz empfehlen
    In conversation Friday, 27-Oct-2017 11:37:05 EDT from io.schiessle.org permalink
  4. bes (bes@io.schiessle.org)'s status on Tuesday, 24-Oct-2017 09:33:43 EDT bes bes
    in reply to
    • platano
    @platano yes, I also have a Friendica installation. I will definitely use it a some kind of "comment system" for my blog (https://soc.schiessle.org/~blog) but I'm not sure yet how much I will use the personal profile (https://soc.schiessle.org/~bjoern). But feel free to follow me and/or my blog.
    In conversation Tuesday, 24-Oct-2017 09:33:43 EDT from io.schiessle.org permalink
  5. bes (bes@io.schiessle.org)'s status on Friday, 13-Oct-2017 08:07:48 EDT bes bes
    It has been a tough decision, especially because I had many good discussions here. But I don't want to run my own server just for GNU Social any longer. The last few weeks I tried Mastodon to see if I want to join one of the existing GNU Social nodes or Mastodon. I decided to go with Mastodon. Digital social networks are just no longer as important to me as they where in the past. All important stuff I want to preserve will be published at schiessle.org and my blog. From next month on social networking will happen at https://mastodon.social/@bjoern and occasionally diasp.eu/u/bjoern. The next few weeks I will start following you from Mastodon and I hope most of you will follow me back. ;)
    In conversation Friday, 13-Oct-2017 08:07:48 EDT from io.schiessle.org permalink

    Attachments

    1. Björn Schießle - Mastodon
      from Mastodon
      Free Software developer; coordinator Germany & board member at FSFE; creating free, decentralized & open cloud technology at Nextcloud - https://schiessle.org
  6. bes (bes@io.schiessle.org)'s status on Sunday, 08-Oct-2017 07:20:06 EDT bes bes
    • Hiker
    • MMN-o ✅⃠
    • platano
    • Rob Myers
    @mmn @robmyers @platano @hikerus I think you, as the main developer should have access. Seems that most of the people in control of the homepage and the git repository have lost interest or at least the interest decreased a lot. This shouldn't slow down GNU Social development. If they don't give you root access I would consider moving GNU Social repository and Web presents to a different place. But that's of course up to you.
    In conversation Sunday, 08-Oct-2017 07:20:06 EDT from io.schiessle.org permalink
  7. bes (bes@io.schiessle.org)'s status on Saturday, 07-Oct-2017 06:19:31 EDT bes bes
    in reply to
    • GNU Social
    • Hiker
    @hikerus I wonder who is the maintainer of this site. Afaik Matt Lee gave up on it. But was it handed over to someone else in a coordinated way? !gnusocial
    In conversation Saturday, 07-Oct-2017 06:19:31 EDT from io.schiessle.org permalink
  8. bes (bes@io.schiessle.org)'s status on Wednesday, 04-Oct-2017 18:30:51 EDT bes bes
    • GNU Social
    What happened to git.gnu.io? !GNUSocial
    In conversation Wednesday, 04-Oct-2017 18:30:51 EDT from io.schiessle.org permalink
  9. bes (bes@io.schiessle.org)'s status on Tuesday, 03-Oct-2017 13:37:01 EDT bes bes
    • Politik
    Steilvorlage für den Bund, "Jamaika-Regierung" in Schleswig-Holstein setzt auf Freie Software und definiert als langfristiges Ziel "eine vollständige Ablösung" proprietärer Software. https://www.heise.de/newsticker/meldung/Schleswig-Holstein-laeutet-Abschied-von-Microsoft-ein-3849115.html #CDU #CSU #Gruene #FDP #Jamaika #FreieSoftware #OpenSource #BTW17 !politik 
    In conversation Tuesday, 03-Oct-2017 13:37:01 EDT from io.schiessle.org permalink

    Attachments

    1. Schleswig-Holstein läutet Abschied von Microsoft ein
      from heise online
      Die schleswig-holsteinische Landesregierung setzt bei der IT-Beschaffung den Kurs auf Open Source und strebt langfristig eine „vollständige Ablösung“ von Closed-Source-Software an.
  10. bes (bes@io.schiessle.org)'s status on Sunday, 01-Oct-2017 03:23:34 EDT bes bes
    • furr
    @furr hatte dir doch ein paar Unterschiede genannt. Wenn du was spezielles wissen willst musst du deine Frage konkretisieren.
    In conversation Sunday, 01-Oct-2017 03:23:34 EDT from io.schiessle.org permalink
  11. bes (bes@io.schiessle.org)'s status on Wednesday, 27-Sep-2017 13:04:22 EDT bes bes
    • furr
    @furr it is Free Software, it is integrated in desktop and mobile clients, it will be able to support HSM's for enterprise key management, it will support sharing (maybe even federated sharing), no JavaScript solution where you have to trust the server again that it gives you the right Javascript with no backdoors.
    In conversation Wednesday, 27-Sep-2017 13:04:22 EDT from io.schiessle.org permalink
  12. bes (bes@io.schiessle.org)'s status on Wednesday, 27-Sep-2017 10:52:19 EDT bes bes
    • Nextcloud
    !Nextcloud 13 will come with end-to-end encryption, read more and give early feedback: https://nextcloud.com/blog/nextcloud-introducing-native-integrated-end-to-end-encryption/
    In conversation Wednesday, 27-Sep-2017 10:52:19 EDT from io.schiessle.org permalink

    Attachments

    1. Nextcloud Introducing Native Integrated End-to-end Encryption
      from Nextcloud
      Nextcloud Introducing Native Integrated End-to-end Encryption
  13. bes (bes@io.schiessle.org)'s status on Tuesday, 26-Sep-2017 02:33:24 EDT bes bes
    Bekommen wir mit Jamaika eine bürgerrechtsfreundliche Regierung mit progressiver Netzpolitik? Die Möglichkeit besteht, drücken wir die Daumen! https://io.schiessle.org/url/54391 #CDU #CSU #Gruene #FDP #btw17
    In conversation Tuesday, 26-Sep-2017 02:33:24 EDT from io.schiessle.org permalink

    Attachments

    1. Invalid filename.
      Analyse: Digital first? Was schwarz-gelb-grün netzpolitisch bedeuten könnte
      By Ingo Dachwitz from netzpolitik.org
      Wenn die SPD nicht doch noch umkippt, ist die einzig realistische Koalition ohne Neuwahlen schwarz-gelb-grün. Wir haben analysiert, was dieses "Jamaika-Bündnis" netzpolitisch bedeuten könnte: Im besten Fall würden Liberale und Grüne ein bürgerrechtsfreundliches Korrektiv zu den Überwachungsplänen de
  14. bes (bes@io.schiessle.org)'s status on Tuesday, 26-Sep-2017 02:21:19 EDT bes bes
    • Norbert Tretkowski
    @nobse message from the future? ;) According to gajim.org 0.16.8 is the latest version.
    In conversation Tuesday, 26-Sep-2017 02:21:19 EDT from io.schiessle.org permalink
  15. bes (bes@io.schiessle.org)'s status on Friday, 22-Sep-2017 04:18:15 EDT bes bes
    • Politik
    Die Grünen atworten auf Public Money? Public Code! mit einem offenen Brief und bekunden ihre Unterstützung https://www.gruen-digital.de/2017/09/public-money-public-code-wer-es-nicht-glauben-mag-schaue-sich-die-software-zu-den-bundestagswahlen-an/ !politik #FreeSoftware #Gruene #pmpc #PublicCode
    In conversation Friday, 22-Sep-2017 04:18:15 EDT from io.schiessle.org permalink

    Attachments

    1. File without filename could not get a thumbnail source.
      Public Money? Public Code! Wer es nicht glauben mag, schaue sich die Software zu den Bundestagswahlen an...
      Public Money? Public Code! Wer es nicht glauben mag, schaue sich die Software zu den Bundestagswahlen an…
  16. bes (bes@io.schiessle.org)'s status on Saturday, 16-Sep-2017 21:20:57 EDT bes bes
    Dropbox dropped IaaS in favour of their own infrastructure. The main reasons: quality, management & control. For the same reasons you shouldn't rely on SaaS. There are better solutions out there. https://io.schiessle.org/url/53832

    #Dropbox #IaaS #SaaS #sustainability #control
    In conversation Saturday, 16-Sep-2017 21:20:57 EDT from io.schiessle.org permalink

    Attachments

    1. Why Dropbox decided to drop AWS and build its own infrastructure and network
      By <a href="/author/ron-miller/" title="Posts by Ron Miller" onclick="s_objectID='river_author';" rel="author">Ron Miller</a> from TechCrunch

      There is always a tension inside companies about whether to build or to buy, whatever the need. A few years ago Dropbox decided it was going to move the majority of its infrastructure requirements from AWS into its own data centers. As you can imagine, it took a monumental effort, but the company believed that the advantages of controlling its own destiny would be worth all of the challenges they faced to get there.

      For starters, a company like Dropbox is dealing with a huge number of customers storing an enormous amount of data. The latest numbers are 500 million users and 200,000 business customers. When they made the transition, they had to move an epic 500 petabytes — that’s five followed by 17 zeros — that had been sitting on AWS servers. (They still use AWS for some workloads.)

      The first step was building the infrastructure to replace it. We’re talking about a company that had 1500 employees, with just around a dozen on the infrastructure team. This was not a huge operation, yet what they were trying to do was build something themselves at web scale that only a small number of companies with much larger teams had tried to this point.

      That included building and equipping three US data centers. It also meant building the network backbone, the infrastructure that facilitated the connections between the US data centers and other facilities they had located throughout the world. When you open Dropbox and request a file, you want your file to download pretty much instantaneously without latency, and it was up to the team to ensure that happened, while trying to navigate between the old system and the new one.

      “What’s neat about the backbone is that it’s similar to something you might find at Google or Facebook, but we built this with a relatively small team,” Dan Williams, head of production engineering at Dropbox told TechCrunch. And that small team had to build the backbone and move all of that the content, all while keeping the service up and running.

      Ultimately though the company was willing to make this massive move because it craved control over its infrastructure. Williams admitted that when it comes to making a decision like this, there are always concessions, but in the end the trade-offs were worth it to them. “For us, it was about quality and control and management. We know there are solid third parties out there with [high] quality and performance, but we felt ours could be equal or even better because we know the system so well.”

      Williams says for Dropbox, building the network was a business decision and it has had a positive impact on the business overall. “I think it could be argued in fact that anyone who has built a decent-sized network like this has had some effect on the business in a positive way that is actually building trust for the user and getting more users to adopt the product or service based on the quality of the service” Williams explained.

      The new system has certainly had a positive impact on Dropbox’s reputation with enterprise IT too. Back in the day, Dropbox often had a bad rep with IT because of unauthorized usage inside large organizations. Today, the Dropbox Business line of products combined with this in-house infrastructure and network has created a level of trust they didn’t have before. Williams points out that they have such detailed insight into the networking operation, they can use that data as a sales driver, even though they didn’t end up charging for this change.

      “One of our core beliefs is providing a high-performance, low-expense product.” He believes that’s why they have been able to retain old customers through this transition, while also growing the user base over time.

      Whether the cost of ownership went down in real terms, the company believes it achieved its objectives by building it themselves. “While cost is always something that we consider, our goal with our network expansion was to improve performance, reliability, flexibility and control for our users — which we have succeeded in doing,” a company spokesperson told TechCrunch.

      That build versus buy decision is never an easy one, especially for a company the size of Dropbox, which had to walk the line between the two systems while it made the transition, but today it appears to have paid off in a big way for them.

  17. bes (bes@io.schiessle.org)'s status on Saturday, 16-Sep-2017 09:51:58 EDT bes bes
    • Free Software Foundation Europe
    • Rysiekúr Memesson
    @rysiek @fsfe he has a Friendica instance, but I don't know how active he uses it: friendica.3rik.cc/
    In conversation Saturday, 16-Sep-2017 09:51:58 EDT from io.schiessle.org permalink
  18. bes (bes@io.schiessle.org)'s status on Saturday, 16-Sep-2017 04:46:09 EDT bes bes
    Thanks to all the people working so hard to drive software freedom forward! Happy Software Freedom Day! #FreeSoftware #OpenSource #SFD2017 https://io.schiessle.org/attachment/53807
    In conversation Saturday, 16-Sep-2017 04:46:09 EDT from io.schiessle.org permalink
  • 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.