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/)YU
Posts
5
Comments
98
Joined
2 yr. ago

  • i mean, the problem isn't the portal in those cases, and i think the portal is a very cool idea -- imo, the fact that these people get in the news for it is probably why they're doing it, it's just one way to get people's attention by doing outrageous stuff around a new attraction

    it's nothing new, and eventually dies off, and there are probably also many events of people being nice to each other that go unreported

    edit: also, yeah, showing body parts generally shouldn't be considered that harshly imo - of you're forcing people to look at them, they're probably not pretty, but I wouldn't call those "vulgaire" either

  • not sure about the path, you should check flatpak's docs for more accurate informations

    but i believe so, yeah

    on one had it's a shame they're not using xdg dirs, but on the other, i kinda get why -- it's neither config files, nor just data -- it's both, it's a container

  • i think those kids got a point -- app stores are easier than finding random executables on the web

    it can sometimes be a pain to find the original developper's website to get a legitimate copy of the software from, especially for non-technical users.

    the main issue with app stores is that they're often closed ecosystems, where there's only one app provider. that's not the case with flatpatk!

  • AppImages can be double clicked and executed. They are not a pain to use.

    i can understand that, but flatpaks are easier to upgrade and automatically integrated into your package manager, which (i believe) isn't as straight forward for appimages. also there's one major repo where you can find most apps (flathub) making app-hunting less daunting i feel like.
    also, once your app is installed, it's always in your system menu, so that doesn't change much in the long run

    Comfortable setup that carried over from Ubuntu LTS.

    can't you carry over flatpaks as well? you can probably copy /var/lib/flatpak or wherever they store their stuff from one system to another, or failing that, save all the app IDs you have installed, and re-install them onto your new system, backing up ~/.var to keep all your data!

  • because they require more access to the system

    afaik, you can allow more system access to flatpaks

    Ubuntu runs a virtual filesystem in order to allow its Snap Firefox to access the Dictionary that lives "outside" its sandboxing

    i believe flatpak also does that, you can specify some paths from the host to be available to the flatpak

  • my helping you

    okay, this is a personal thing, but i need the source/citation for the 3rd quote. that grammar rule has beeg bugging me for like a month, i need to know where and when this is from, and who wrote this

  • where do you live where stuff's so expensive? genuine question, because honestly, i've never seen such pricing here

    most of the stuff i get from amazon (which is, to be fair, not much and mostly non-food/perishables) has free shipping (without prime) to amazon lockers or to your house if you have a >25€ (or maybe >40€ now..?) order

    also, may be biased because i live in france, but like, a loaf of bread is at most 3€ here, even in the most remote villages, you'll likely not have for more than 1.30€ for a baguette

  • There are tons of ActivityPub implementations out there already

    but none are widely used by such a massive amount of people as threads, and especially people who don't understand/care about spec compliance or even how federation works

    honestly, i think in the best scenario, threads will create their own activitypub "fork", and most instances won't want to follow it, forcing the people who were on non-threads instances to chose between going to threads to keep in touch with their threads mutuals, or staying on non-threads instances and no longer having a reliable way of keeping in touch with those people.

    worst case would be instances following what meta does and making them the spec dictators pretty much, the spec would become closed source and all other fedi implementations would lag behind in features compared to threads, and they can at any point change the spec and break other instances.

    i think the point of defederating with threads isn't just the defederation, but is about sending a message that we don't want to play their game, we want to keep doing our things our ways. if they want to interract with the fediverse, they'll have to play by our rules, we don't want to follow theirs