０７６萌ＳＮＳ
  • Login

  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices by :blabcatverified: (jain@blob.cat), page 3

  1. :blabcatverified: (jain@blob.cat)'s status on Monday, 31-Jul-2023 21:06:45 JST :blabcatverified: :blabcatverified:
    in reply to
    • Moon
    @Moon matrix & jisti, and yes occasionally torrent, mkv is the best
    In conversation Monday, 31-Jul-2023 21:06:45 JST from blob.cat permalink
  2. :blabcatverified: (jain@blob.cat)'s status on Thursday, 20-Jul-2023 08:05:03 JST :blabcatverified: :blabcatverified:
    in reply to
    • cool_boy_mew
    @coolboymew oh.... :blobcatsweat:
    In conversation Thursday, 20-Jul-2023 08:05:03 JST from blob.cat permalink
  3. :blabcatverified: (jain@blob.cat)'s status on Wednesday, 12-Jul-2023 22:21:36 JST :blabcatverified: :blabcatverified:
    • NaiJi
    @NaiJi Dont harm cats by eating pizza!
    In conversation Wednesday, 12-Jul-2023 22:21:36 JST from blob.cat permalink
  4. :blabcatverified: (jain@blob.cat)'s status on Wednesday, 05-Jul-2023 18:59:05 JST :blabcatverified: :blabcatverified:
    • Puniko 😺 :verifiedsabakan: :verified_cool:
    :ablobcatbongo: look @puniko i found a way to stack them efficiently
    In conversation Wednesday, 05-Jul-2023 18:59:05 JST from blob.cat permalink

    Attachments


    1. https://s3.v5.yokai.cafe/blobcatfiles/212f6b799cd733c9d9120cc0f563d7b11b3912075f8955cc3c7c2976db376ce2.png
  5. :blabcatverified: (jain@blob.cat)'s status on Monday, 03-Jul-2023 05:38:57 JST :blabcatverified: :blabcatverified:
    in reply to
    • :bun: Stellar (not lewd)
    @Stellar what is it this time?
    In conversation Monday, 03-Jul-2023 05:38:57 JST from blob.cat permalink
  6. :blabcatverified: (jain@blob.cat)'s status on Wednesday, 21-Jun-2023 18:55:29 JST :blabcatverified: :blabcatverified:
    Once again I would like to make a statement about fedi instance administration. :ablobcatbongopost:

    The reason is that I increasingly get the feeling that more and more is going wrong on certain instances. Maybe that's because I sometimes don't hear everything from the outside, but i doubt that this is the case.

    There are a few issues that need to be addressed:
    - Transparency
    - Organizational structure
    - Conflict Management with Users or other Instances

    Transparency:
    It is important that things an admin does are transparent to the users of the instance. It is not the users duty to inquire, but the administrators duty to communicate. This begins with conflicts and ends with blocks.

    The publication of such data helps both users who are looking for an instance, so that they can assess the instance, and other administrators. This also helps especially when it comes to finding out communication problems between instances or you can see if the admins of an instance maintain their blocklists or dont fullfill their duties.

    One of the most used excuses here is that such information is not made public to avoid conflict and drama.
    I hardly think this argument is nonsense, especially because Admins of blocked instance will know it somewhen and have more work to figure out whats going on.
    Moreover, this does not prevent conflicts and drama at all, every admin knows how easy it is to log on to a new instance or setup a temporary one to confront the counterpart.
    In fact, this approach mostly favors the non-maintenance or incorrect maintenance of blocklists, which is to the disadvantage of their own users.

    Organizational structure:
    I will certainly not dictate to anyone how their instance should be run. However, I often notice that many instances do not announce this themselves. One's own values, rules, ways to adapt these rules, limits that are given, that all should be known. This is all information users are interested in. I think that Fediverse instances are realtively similar to associations, and exactly like this, one should deal with each other. And that brings me to the last part.

    Conflict Management with Users or other Instances:
    I've been around long enough to have experienced to be able to assess when an admin is acting out of the interest of their instance or acting out of their own interest. I have experienced this against myself or as a passive viewer on the network. Most of the time, this goes so far that people do not take the time for necessary discussions and thus again a transparency problem exists. Problems, intentional or unintentional mistakes are always there, and these should also be allowed to be discussed and one is should also allow to make mistakes but also make learnings from such situations.

    And now the controversial own opinion:
    There are not many instances which define values and stand up for them: Our decision to enforce our rules locally only is one of them. The software we use allows the user to have control over server mutes/blocks, so the administration can decline the authority to take care of those, and leave this up to the user. Something for which I stand politically strong and therefore I can take the time to care more about local rules and conflicts.

    I wish more admins and users would behave like this. But after all I can respect if other instances have different rules and behaviors. But what I don't like is when admins can't differentiate between their opinion and their responsibility and use their power to propagate their opinions.

    I hope I can inspire someone with this long text.
    In conversation Wednesday, 21-Jun-2023 18:55:29 JST from blob.cat permalink
  7. :blabcatverified: (jain@blob.cat)'s status on Sunday, 18-Jun-2023 18:23:55 JST :blabcatverified: :blabcatverified:
    Welcome to blobcat territory
    In conversation Sunday, 18-Jun-2023 18:23:55 JST from blob.cat permalink

    Attachments


    1. https://s3.v5.yokai.cafe/blobcatfiles/0087a1f92b03546ea70f7af6976ed06158a855dfb387c04945e90710890a8ad3.jpg
  8. :blabcatverified: (jain@blob.cat)'s status on Friday, 16-Jun-2023 06:29:07 JST :blabcatverified: :blabcatverified:
    in reply to
    • Moon
    @Moon yeah but instead of insisting to delete the posts, you could ask for them to be corrected... not very nice of you
    In conversation Friday, 16-Jun-2023 06:29:07 JST from blob.cat permalink
  9. :blabcatverified: (jain@blob.cat)'s status on Monday, 29-May-2023 20:26:43 JST :blabcatverified: :blabcatverified:
    Thats a wonderful video about gitlab engineers deleting the prod database unintentionally
    https://www.youtube.com/watch?v=tLdRBsuvVKc
    In conversation Monday, 29-May-2023 20:26:43 JST from blob.cat permalink

    Attachments

    1. Dev Deletes Entire Production Database, Chaos Ensues
      from Kevin Fang
      If you're tasked with deleting a database, make sure you delete the right one.Sources:https://about.gitlab.com/blog/2017/02/10/postmortem-of-database-outage-...
  10. :blabcatverified: (jain@blob.cat)'s status on Thursday, 11-May-2023 14:34:19 JST :blabcatverified: :blabcatverified:
    :comfymorning:
    In conversation Thursday, 11-May-2023 14:34:19 JST from blob.cat permalink
  11. :blabcatverified: (jain@blob.cat)'s status on Sunday, 07-May-2023 23:39:12 JST :blabcatverified: :blabcatverified:
    :comfypeek:
    In conversation Sunday, 07-May-2023 23:39:12 JST from blob.cat permalink
  12. :blabcatverified: (jain@blob.cat)'s status on Friday, 10-Mar-2023 00:17:28 JST :blabcatverified: :blabcatverified:
    in reply to
    • Puniko 😺 :verifiedsabakan: :verified_cool:
    @puniko geh was essen und entderpe dich
    In conversation Friday, 10-Mar-2023 00:17:28 JST from blob.cat permalink
  13. :blabcatverified: (jain@blob.cat)'s status on Friday, 10-Mar-2023 00:17:26 JST :blabcatverified: :blabcatverified:
    in reply to
    • Puniko 😺 :verifiedsabakan: :verified_cool:
    @puniko nein :ablobcathungry:
    In conversation Friday, 10-Mar-2023 00:17:26 JST from blob.cat permalink
  14. :blabcatverified: (jain@blob.cat)'s status on Saturday, 04-Mar-2023 08:32:26 JST :blabcatverified: :blabcatverified:
    • cool_boy_mew
    @coolboymew :blobcatgoogly:
    In conversation Saturday, 04-Mar-2023 08:32:26 JST from blob.cat permalink
  15. :blabcatverified: (jain@blob.cat)'s status on Wednesday, 01-Mar-2023 19:54:12 JST :blabcatverified: :blabcatverified:
    • Cleo🏳️‍⚧️🏳️‍🌈:AFD: :bst:
    • Puniko 😺 :verifiedsabakan: :verified_cool:
    • Hoppel (Test)
    @puniko @Hoppel @cleo lasst uns puniko entführen
    In conversation Wednesday, 01-Mar-2023 19:54:12 JST from blob.cat permalink
  16. :blabcatverified: (jain@blob.cat)'s status on Wednesday, 01-Mar-2023 19:54:10 JST :blabcatverified: :blabcatverified:
    • Cleo🏳️‍⚧️🏳️‍🌈:AFD: :bst:
    • Puniko 😺 :verifiedsabakan: :verified_cool:
    • Hoppel (Test)
    @Hoppel @puniko @cleo aber puniko möchte das ja selber, damit er nicht arbeiten muss
    In conversation Wednesday, 01-Mar-2023 19:54:10 JST from blob.cat permalink
  17. :blabcatverified: (jain@blob.cat)'s status on Wednesday, 01-Mar-2023 19:54:04 JST :blabcatverified: :blabcatverified:
    • Cleo🏳️‍⚧️🏳️‍🌈:AFD: :bst:
    • Puniko 😺 :verifiedsabakan: :verified_cool:
    • Hoppel (Test)
    @Hoppel @puniko @cleo :blobcatlaugh: :blobcatlaugh: ich weis nicht, aber ich denke der Arbeitsort ist für das nicht geeignet
    In conversation Wednesday, 01-Mar-2023 19:54:04 JST from blob.cat permalink
  18. :blabcatverified: (jain@blob.cat)'s status on Friday, 24-Feb-2023 05:44:20 JST :blabcatverified: :blabcatverified:
    in reply to
    • 
    • :ihavenomouth:
    @mint @Inginsub :blobcatshrug: Hosting Wildebeest? Maybe the concept of visibilty is beyond what you can read on fedi
    In conversation Friday, 24-Feb-2023 05:44:20 JST from blob.cat permalink
  19. :blabcatverified: (jain@blob.cat)'s status on Friday, 24-Feb-2023 05:44:19 JST :blabcatverified: :blabcatverified:
    in reply to
    • 
    • :ihavenomouth:
    • :blabcatverified:
    @mint @Inginsub let me reword it: Your assumption is wrong, you just can't see the posts
    In conversation Friday, 24-Feb-2023 05:44:19 JST from blob.cat permalink
  20. :blabcatverified: (jain@blob.cat)'s status on Friday, 24-Feb-2023 05:11:12 JST :blabcatverified: :blabcatverified:
    Since Wildebeest does reveal DMs to the public, it would be the best for Pleroma & forks instances to write a MRF to prevent sending DMs to such instances...

    Since i do not have a very deep knowledge of MRF, im not sure if MRFs do actually have enough informations about an instance to prevent sending DMs to Wildebeest...
    In conversation Friday, 24-Feb-2023 05:11:12 JST from blob.cat permalink
  • After
  • Before

User actions

    :blabcatverified:

    :blabcatverified:

    Jain, just another identifiable nameI like :blobcat: and post them regularly:blobcatsnuggle: all those :blobcat:light addiction to C8H10N4O2Alt: @Jain@fedi.absturztau.be

    Tags
    • (None)
    ActivityPub
    Remote Profile

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          8961
          Member since
          13 Jan 2023
          Notices
          65
          Daily average
          0

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          ０７６萌ＳＮＳ is a social network, courtesy of ０７６. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All ０７６萌ＳＮＳ content and data are available under the Creative Commons Attribution 3.0 license.