• 1 Post
  • 53 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle









  • Depends what you want to play it on. In my house we have:

    3 laptops 2 tablets 2 mobile phones (1 android, 1 iPhone) TV

    Not all these devices support local storage for music and it’s a pain to sync files between them. With Jellyfin the complete library is in one location with a consistent interface. It can also be made available remotely if I choose.



  • I feel this and some of the other comments in this thread are missing the point. It’s not about me and my followers. It’s about the news sources and topics that I search for or follow. They simply haven’t moved to Mastodon and where notable individuals that I follow have tried, it simply hasn’t worked out due to lack of interest. I’m not interested in the fediverse as a topic in itself, I’m interested in the topics and events I want to follow. Something happens and I can find and read and watch clips about it on Twitter. Not so Mastodon.



  • SquiffSquiff@lemmy.worldtoFediverse@lemmy.worldBluesky continues to soar
    link
    fedilink
    English
    arrow-up
    34
    arrow-down
    6
    ·
    2 months ago

    I’ve been on Mastodon for over a year and the content simply isn’t there. Several of the people that I follow on Twitter have tried moving or duplicating to Mastodon. They’ve had a fraction of the visibility and engagement from commenters that they would get on Twitter. Invariably after a few months they have essentially given up on it as a primary medium. For me the discoverability is essentially non-existent, which I don’t think is helped by the idea of it being based around instance-local communities, which have no meaning when you’re looking at something like Twitter.





  • GitLab just doesn’t compare in my view:

    To begin with, you have three different major versions to work with:

    • Self-Hosted open source
    • SAAS open source
    • Enterprise SAAS

    Each of which have different features available and limitations, but all sharing the same documentation- A recipe for confusion if ever I saw one. Some of what’s documented only applies to you the enterprise SAAS as used by GitLab themselves and not available to customers.

    Whilst theoretically, it should be possible to have a gitlab pipeline equivalent to GitHub actions, invariably these seem to metastasize In production to use includes making them tens or hundreds of thousands of lines long. Yes, I’m speaking from production experience across multiple organisations. Things that you would think were obvious and straightforward, especially coming from GitHub actions, seen difficult or impossible, example:

    I wanted to set up a GitHub action for a little Golang app: on push to any branch run tests and make a release build available, retaining artefacts for a week. On merging to main, make a release build available with artefacts retained indefinitely. Took me a couple of hours when I’d never done this before but all more or less as one would expect. I tried to do the equivalent in gitlab free SAAS and I gave up after a day and a half- testing and building was okay but it seems that you’re expected to use a third party artefact store. Yes, you could make the case that this is outside of remit, although given that the major competitor or alternative supports this, that seems a strange position. In any case though, you would expect it to be clearly documented, it isn’t or at least wasn’t 6 months ago.


  • I think you may have misunderstood your issue. 16 GB is more than is needed on / for a typical desktop Ubuntu installation. For example, here is a partial output of df -h on my Ubuntu 22.04 system- this is a server but it has a full desktop environment installed. I actually originally put 20.04 on it when that was current so it has accumulated some cruft. I also remove snaps:

    Filesystem Size Used Avail Use% Mounted on
    /dev/sda1 47G 11G 34G 25% /
    /dev/sda7 84G 26G 54G 33% /home
    /dev/sda6 88G 22G 62G 27% /var

    The thing you’re most likely running into is that whilst everyone quickly realises the advantages of putting /home on a separate partition, it’s not so obvious that /var should be on a separate partition as well. This is because /var is where all the logs and caches are stored, and if you have a runaway process that fills up /var/log, it can cause the system to crash. Experienced Linux users will have encountered situations where /var was not on a separate partition and their box broke because of logs not being cycled…

    I realise that you may be saying that you have 16GB total for 2 x installations. That is going it a bit but should be possible with some thought and care. Good luck!