[-] scsi@lemm.ee 3 points 2 weeks ago

This is unfortunately a choice the Nautilus (GNOME) folks have taken; in other file managers (Thunar for XFCE, Caja for MATE, etc.) the ability to use custom actions are a first class citizen. Within Nautilus, the nautilus-actions project was superseded by the filemanager-actions project which was then archived: https://gitlab.gnome.org/Archive/filemanager-actions - a custom GNOME action might be something like gio open /path/to/terminal.desktop %d (where %d is the directory from Nautilus)

There are 3rd party attempts to recreate what was stripped out of/abandoned in Nautilus such as this one: https://github.com/bassmanitram/actions-for-nautilus

[-] scsi@lemm.ee 8 points 2 weeks ago

Went down the rabbit hole for you while drinking some tea listening to the rain - it looks like in the future there is a new app/proposal for FreeDesktop to use xdg-terminal-exec as the new/default way and it's hard coded into the GNOME "gio" code over here (ctrl+f search xdg-terminal-exec): https://gitlab.gnome.org/GNOME/glib/-/blob/main/gio/gdesktopappinfo.c

That said, it looks like the nautilus-open-terminal Nautilus extension is shipped as part of gnome-terminal so it's hard coded to run that terminal not using the above code. Instead, you'd need to leverage a different extension called nautilus-open-any-terminal for now until the landscape changes: https://github.com/Stunkymonkey/nautilus-open-any-terminal

(disclaimer: not using GNOME/Nautilus or Fedora, theorycraft from me)

[-] scsi@lemm.ee 9 points 1 month ago

In addition to the other comments which more directly address your question, DNS has been / can be used to exfiltrate data from "secure" networks. Search "dns data exfiltration" in your favourite search engine and you'll get several high quality articles. Typical mitigations might be to limit which DNS servers your network can contact, restrict packet sizes to the bare minimum which valid use would have and so forth.

[-] scsi@lemm.ee 5 points 1 month ago

I'm familiar with the news about the brick - in the past I've had this problem (I think it was a bricked... pixel 2?) and faced similar power off issues. Keep trying what you're trying but in various ways - I vaguely recall that I had to press volume up first and then hold power or something like that (meaning pressing them both at once or power first didn't work). One of the various combos you're trying is supposed to be the one that forces it off after ~30secs of holding but a fuzzy memory reminds me it was real finicky to actually get working. Worst case scenario, just let the battery die. :(

[-] scsi@lemm.ee 1 points 1 month ago

To your multiple IMAP concept, I have been using isync / mbsync (name change, package isync in Debian) for years running via cron script to pull email from one domain at one provider and push it to a subfolder of another domain at another provider. You have to be aware of one specific gotcha but it's otherwise been working all by itself forever without issues. Take note of the PipeLineDepth 1 for IMAP service providers which throttle your speed, I have to use it on the destination side provider config.

[-] scsi@lemm.ee 1 points 1 month ago

Two tips having worked in the corporate world (strict controls):

  • Create a basic non-spam web page for it that has something that doesn't look like SEO garbage or whatever. Nothing more than "hey this is a personal domain of the flatbield family" is fine, maybe a link to something (links enhance rep - put a picture of your dog up or link to a wikipedia article or something) and let it rest for at least 30 days. The 3rd party filtering services used by corporate players severely limit, block or distrust a domain newer than 30 days (or longer, depending). Set up a SSL cert on it for another +1 to it's rep value, HTTPS is looked at by these services and ensure the CA record is in your DNS for that SSL issuer.

  • Ensure you use the Providers' setup for DKIM, SPF and so forth (many like Fastmail have a DNS-check wizard to get you all set up) as many modern providers will instantly downvote you if anything is missing or wrong with these controls (I've heard GMail and O365 particularly). In 2024 these are a must-have, not a nice-to-have, for getting your email received by anyone and everyone.

If you chose a domain at a TLD which has/had been used by the bad buys (dot-xyz, info, zip, etc.) you may wish to reconsider - there are TLDs which are wholescale blocked or downvoted in rep based on this (by the same services used above). Ensure someone working at a bank (strict egress controls for their employees) can visit your domain as a good litmus test as to it's validity for use in email reputation.

A company such as Fastmail spends a lot of time ensuring their IP address space for sending and receiving mail is clean - getting spammers off their service, getting IP rep cleaned off blacklists and so forth. So your task is to focus on the same thing for your domain - if someone had previously owned the name they could have gotten it on blacklists long ago, a handy way to check old history is looking it up at web.archive.org for captured snapshots (and I've walked away from domain names because of this once I discovered previous content I didn't like).

[-] scsi@lemm.ee 8 points 1 month ago* (last edited 1 month ago)

Fastmail has one feature many others lack (which is hard to research unless you want/need it and have go down the rabbit hole) - scope limited login tokens for specific uses. Specifically, you can set up one for "read only IMAP" (to archive emails using scripts etc.), "SMTP only" (to send emails from scripts like backup reports etc.) and so forth. Many, if not most, other providers either don't have it, or if they do it's very limited like one token only with no scope control. $0.02 hth

[-] scsi@lemm.ee 1 points 2 months ago

Might I recommend https://liberapay.com/ ? As a user, I can donate with PayPal and they minimize vendor fees by collecting up front from me and performing recurring donations to you (lemm.ee) and it allows me to retain personal privacy if so desired (per the other reply). Here is the core Lemmy developer using the platform for example: https://liberapay.com/dessalines/ | https://liberapay.com/Lemmy/

[-] scsi@lemm.ee 1 points 3 months ago

On my Subscribed view on lemm.ee sorted by Hot which very recently upgraded lemmy-ui to 0.19.4 (your lemmy.sdf.org instance has not upgraded yet, just checked), of 14x news items/links which should have thumbnails - 8x of them are broken/missing, just over 50%.

[-] scsi@lemm.ee 2 points 3 months ago

It's possible what you are seeing is more visible than before due to issue #2433 which is:

When images are broken, a blank space is all that is shown. A fallback image for broken images would make this more apparent.

With the 0.19.4 update I notice it a lot more now and see a lot from apnews.com causing this, on my Subscribed view with news@lemmy.world and world@lemmy.world (and others) this morning I count:

Sites that are fine: www.cnbc.com, www.nbcnews.com, www.bbc.com, www.cbsnews.com, newrepublic.com and a bunch of fediverse instances and other "not mainstream" sites from around the internet. it would appear that whatever has changed in code is interacting badly with certain mainstream news sites and the ability to get a thumbnail - I browsed the lemmy-ui commits and a metric ton of 3rd party dependencies were updated, gave up looking for the cause.

[-] scsi@lemm.ee 5 points 3 months ago

Refer to the cryptsetup-luksChangeKey man page --key-file options, you cannot change the password directly on a commandline; you either (a) type it interactively, (b) put it in a keyfile, or (c) accept input from STDIN with the standard use of - on the end (e.g. echo "mypass" | cryptsetup luksChangeKey /dev/sda - )

[-] scsi@lemm.ee 2 points 3 months ago

It is a disagreement between two entities (one large, one small) as to the use of EDNS, an extension to basic DNS, and is briefly outlined in Wikipedia. Using any other resolver, such as Quad9, instead of Cloudflare for your local DNS works as expected. https://en.wikipedia.org/wiki/EDNS_Client_Subnet#Controversy_over_lack_of_support

view more: ‹ prev next ›

scsi

joined 5 months ago