Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)K
Posts
63
Comments
91
Joined
3 yr. ago

All of this user's content is licensed under CC BY 4.0

  • Hm, I have trouble trusting any information on that site for a number of reasons:

    1. They don't seem to grasp the concept of a federated service, and how that plays a role with "Matrix". As stated on this page, under "Riot/Element":
      1. There have been no code audit and an independent security analysis, and hence we must take Element’s word. No one can mark his own homework.
      2. Matrix has had at least one embarrassing security breach, indicating that their infrastructure security is lacking.

    They seem to be referring to "Matrix", and "Element" interchangeably which doesn't make any logical sense as "Matrix" describes the underlying federation protocol, and "Element" one of many clients that exist. This line of thinking can also be seen in the comparison table; the column title is "Element/Riot", and yet much of the data contained in the table is referring to things related to the protocol.

    1. Furthermore, it should also be noted that the quote in point #1 is complete misinformation, and blatantly false (it should also be noted that this information is repeated elswhere, including the comparison table). Firstly,

      There have been no code audit and an independent security analysis, and hence we must take Element’s word. No one can mark his own homework.

    Ignoring that they say "Element", and, instead, assuming that they intended to say "Matrix", from what I can see, there are at least two independent audits that have been done -- their respective information can be found on the blog posts here, and here. and secondly,

    Matrix has had at least one embarrassing security breach, indicating that their infrastructure security is lacking.

    Ignoring the fact that this statement makes no logical sense since "Matrix" is a protocol, and therefore the idea of a "security" breach does not even apply, I'm going to instead assume that they are referring to the home-server "matrix.org". The security breach I'm assuming that they are referring to is described in the blog post here:

    TL;DR: An attacker gained access to the servers hosting Matrix.org. The intruder had access to the production databases, potentially giving them access to unencrypted message data, password hashes and access tokens.

    I'm not entirely sure what the author was insinuating, since this is just something that affected the matrix.org homeserver and no one else, and has absolutely nothing to do with the security of the protocol on the whole. The only important thing with this is whether or not the retrived unencrypted data (ignoring the messages) has any affect of compromising the security of the user -- this author, unfortunately, makes no effort to explore this idea, and just moves on.

    There are plenty of other discontinuties that can be picked apart from this person's site, but these were the most immediately glaring.

  • Of course, few things in life are truly free -- presumably, such a service would be run by donations, and the community.

  • While I do agree that these features are very useful, and interesting, they are unfortunately not the type of service that I am looking for. I encourage you to check out AllTrails, so that you can see an example of what I mean.

  • I’d be concerned if All Trails started taking all that data and charging for access.

    I share the very same concern.

  • Ah, my apologies, I wasn't specific enough in my intent for the post. I am looking for something akin to AllTrails -- you search for a trail, and the site provides you with all of the relevent information: descriptions, pictures, waypoints, information about trail dangers, maps (that's where OpenStreetMap would come in), time to complete the trail, distance, elevation gain, hiking season, etc.

    EDIT: I have now updated the post so that it is more accurate in its intent.

  • Based artist name.

  • FYI, you can edit post titles directly. You don't need to put an "edit" in the description.

  • How come Lemmy randomly shows these super old posts, every now and then?

  • Is Connect open source? I can't find a repo for it.

  • Why ban natural grass? Would putting people on a water meter not accomplish the same thing? Being on a water meter would, theoretically, reduce waste, but at the same time allows one to maintain some of their liberty.

  • Done!

  • I worry that these sorts of things would end up turning the site into a popularity contest (or, well, more of a popularity contest than these sorts of sites already are. That being said, I'm quite proud of Lemmy, currently, as it appears to be resisting that). Also I'm not entirely sure how things like payed comment awards would work with everything being federated.

  • ie oldest postes && least liked First

    This would pretty much automatically throw out all troubleshooting posts. These sorts of posts, very often, don't receive many likes, as that is not their purpose. On top of that, there has been many a time that I have been saved by finding some ancient forum post that solved my problem.

  • It would put the more popular instances under enormous stress, if they had to serve every single subscriber from any other instance.

    From what I understand, media (images, videos, etc.) is not cached. Does that not mean that, in the worst case where every post contained an image, the instance would be serving every subscriber, anyways?

  • The data in that graph doesn't show what your title is inferring. For one, the y-axis is relative, and not absolute. Secondly, your data range is set to the past week so this says nothing about how this method of searching is trending over any useful period of time.

  • I don't really understand this reasoning. Some server would still need to receive those requests at some point. Would it not be better if those requests were distributed, rather than pounded onto one server? If you have a server caching all the content for its users, then all of its users are sending all of those requests for content to that one single server. If users fetched content from their source servers, then the load would be distributed. The only real difference that I can think of is that the speed of post retreival. Even then, though, that could be flawed, as perhaps the source server is faster than one's host server.

  • For your reference, please see the updated post. I ran a S.M.A.R.T test, and the drive is indeed borked.

    Thank you very much for all of the extra information!

  • I ran a S.M.A.R.T short test, and, yeah, the hard drive is quickly dying:

     
        
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: FAILED!
    Drive failure expected in less than 24 hours. SAVE ALL DATA.
    Failed Attributes:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x002f   001   001   051    Pre-fail  Always   FAILING_NOW 1473
    
      
  • Lemmy.world Support @lemmy.world

    Consider creating a separate dedicated donation portal for lemmy.world donations.

  • Arch Linux @lemmy.ml

    Would the Arch Linux forums ever switch to Discourse?

  • Jellyfin: The Free Software Media System @lemmy.ml

    Some shows are not recognized. Can I force/override Jellyfin to make it identify them properly?