taaz

joined 1 year ago
[–] taaz@biglemmowski.win 126 points 8 months ago (28 children)

Welcome to federation, where basically every instance is a proxy to all others.

Btw you are also free to block any instance yourself.

[–] taaz@biglemmowski.win 33 points 8 months ago (2 children)

Uuids are part of the gpt (table) on the disk.

[–] taaz@biglemmowski.win 12 points 8 months ago

Relm4 is an idiomatic GUI library inspired by Elm and based on gtk4-rs.

[–] taaz@biglemmowski.win 0 points 8 months ago

There is also FX which can do this too, additionally you can browse/download/upload files to/from the phone locally from PC through browser (the app opens up a web server).

[–] taaz@biglemmowski.win 15 points 8 months ago* (last edited 8 months ago) (1 children)

I think your idea is not necessarily wrong but it would be hard to get right, especially without making the entry into fediverse too painful for new (non-tech) people, I think that is still the number one pain point.

I have been thinking about moderation and spammers on fediverse lately too, these are some rough ideas I had:

  • Ability to set stricter/different rate-limits for new accounts - users older less then X can do only A actions per N seconds [1] (with better explained rate-limit message on the frontend side)
  • Some ability to not "fully" federate with too fresh instances (as a solution to note [1])
  • Abuse reputation from modlog/modlog sharing/modlog distribution (not really federation) - this one is tricky, the theory is that if you get many moderation actions taken against you your "goodwill reputation" lowers (nothing to do with upvotes) and some instances could preemptively ban you/take mod action, either through automated means or (better) the mods of other instances would have some kind of (easy) access to this information so that they can employ it in their decision.
    This has mostly nothing to do with bot spammers but instead with recurring problem makers/bad faith users etc.
    Though this whole thing would require some kinds of trust chains between instances, not easy development-wise (this whole idea could range from built-in algorithms taking in information like instance age, user count, user age and so on, to some kind of manual instance trust grading by admins).

~

All this together, I wouldn't be surprised if, in the future, there will eventually be some kinds of strata of instances, the free wild west with federate-to-any and the more closed in bubbles of instances (requiring some kind of entry process for other new instances).


[1] This does not solve the other problem with federation currently being block-list based instead of allow-list based (for good reasons).
One could write a few scripts/programs to simulate a federating instance and have tons of bots ready to go. While this exact scenario is probably not usual because most instances will defed. the domain the moment they detect bigger amount of spam, it could still be dangerous for the stability of servers - though I couldn't confirm if the lemmy federation api has any kind of limits, can't really imagine how that would be implemented if the federation traffic spikes a lot.

(Also in theory one could have a shit-ton of domains and subdomains prepared and just send tons spam from these ? Unless there are some limits already, afaik the only way to protect from this would be to switch to allow-list based federation.)

Lot of assumptions here so tell me if I am wrong!
Edit: Also sorry for kind of piggy-backing on your post OP, wanted to get this ideas out here finally

[–] taaz@biglemmowski.win 15 points 8 months ago* (last edited 8 months ago) (1 children)

The base game is already pretty packed, at least it was for me last time I played and it was 10/10 experience as they say.

Why does the headline seems to say new paid DLC is a problem? Considering this is the second one and there has been a shitton of bugfixes and QoL patches (and will be as the article itself says).

"Klei Entertainment Is Working On New DLCs For Oxygen Not Included, Alongside QoL Fixes" FTFY pcgamesn

[–] taaz@biglemmowski.win 2 points 8 months ago* (last edited 8 months ago)

There is a simple trick, as a basic user, do not ever run your (gnome) file explorer as root and if a permission error (requiring "escalation") pops up you shoud double check what you are doing.

I think most graphical file mangers also keep most of the weird/important/system folders away from user and you have to directly navigate to them.

[–] taaz@biglemmowski.win 17 points 8 months ago

In this case, yes anything under /run should not be considered as normal files.

[–] taaz@biglemmowski.win 43 points 8 months ago (3 children)

https://serverfault.com/questions/24523/meaning-of-directories-on-unix-and-unix-like-systems

  • /bin - Binaries.
  • /boot - Files required for booting.
  • /dev - Device files.
  • /etc - Et cetera. The name is inherited from the earliest Unixes, which is when it became the spot to put config-files.
  • /home - Where home directories are kept.
  • /lib - Where code libraries are kept.
  • /media - A more modern directory, but where removable media gets mounted.
  • /mnt - Where temporary file-systems are mounted.
  • /opt - Where optional add-on software is installed. This is discrete from /usr/local/ for reasons I'll get to later.
  • /run - Where runtime variable data is kept.
  • /sbin - Where super-binaries are stored. These usually only work with root.
  • /srv - Stands for "serve". This directory is intended for static files that are served out. /srv/http would be for static websites, /srv/ftp for an FTP server.
  • /tmp - Where temporary files may be stored.
  • /usr - Another directory inherited from the Unixes of old, it stands for "UNIX System Resources". It does not stand for "user" (see the Debian Wiki). This directory should be sharable between hosts, and can be NFS mounted to multiple hosts safely. It can be mounted read-only safely.
  • /var - Another directory inherited from the Unixes of old, it stands for "variable". This is where system data that varies may be stored. Such things as spool and cache directories may be located here. If a program needs to write to the local file-system and isn't serving that data to someone directly, it'll go here.
[–] taaz@biglemmowski.win 23 points 8 months ago (6 children)

We’ve consolidated all our code into a single repository – just clone ente-io/ente on GitHub, and you will have at your disposal a state of the art, end-to-end encrypted, full stack (mobile/web/desktop clients, the server, and a CLI to boot) alternative to Google Photos and Apple Photos.

[–] taaz@biglemmowski.win 24 points 8 months ago* (last edited 8 months ago)

I have recently bought the P14s Gen 4 and except for some WiFi issues it has been pretty smooth sailing (definitely a loot better then the last notebook I had with nvidia dgpu).

[–] taaz@biglemmowski.win 7 points 8 months ago

Getting into MAM is easy tho and you can branch from there, there are people sharing invites to others.

view more: ‹ prev next ›