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
joined 7 months ago
This ~~is~~ appears to be dark pattern marketing at play; they run a Mastodon instance which intercepts all links to the federated content and pushes you towards their for-profit site; it was actually not doing this earlier, when I visited a few links I actually got real mastodon content pages inconsistently.
Generally, if you visit anything like https://flipboard.social/@AlaskaBeacon@flipboard.com it redirects you to to flipboard.com/@AlaskaBeacon which is entirely their for-profit presence. But then it doesn't a few tries later after testing more - I watched within a minute the Texas BBQ one allow me to see the profile on flipboard.social, I reloaded and was suddenly redirected to their flipboard.com/TexasBBQ site.
It seems you might be able to load them into your own mastodon instance manually and it will work (I do see a profile page with legacy posts which hadn't federated yet, so "no posts" at this early of a test). Something like https://myserver.social/@AlaskaBeacon@flipboard.com will presumably work; I suspect though that all posts will be stubs that drive you towards flipboard.com to read the actual content, rather than a direct source (time will tell).
edit: s/is/appears to be/ to give benefit of the doubt
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/
I think I'd put this in the hard house category, could trend towards hard NRG but this really isn't my genre to know the fine details. it pushes towards some (psy)trance-like sounds as it goes on but that's the DJ adding his mojo, he brings it back towards hard house each time
edit: here's the DJ, he bills as trance https://en.wikipedia.org/wiki/Marlo_Hoogstraten
edit 2: always looking to expand my horizons, I'm going to reclassify myself and say it's hard trance in 2024 after comparing a few mixes; hard trance feels "cleaner" between the beats like this, whereas hard house has more chutzpah going on making it sound more... well, like static (no offense to the hard house lovers). It's changed over time and they really feel like they converge a lot now to my ears; two examples:
- hard house 2024: https://www.youtube.com/watch?v=_ksirtYd-lM
- hard trance 2024: https://www.youtube.com/watch?v=Pui4r2Z5uaY
I would agree, and would bring awareness of ionice into the conversation for the readers - it can help control I/O priority to your block devices in the case of write-heavy workloads, possibly compiler artifacts etc.
The Linux kernel uses the CPU default scheduler, CFS, a mode that tries to be fair to all processes at the same time - both foreground and background - for high throughput. Abstractly think "they never know what you intend to do" so it's sort of middle of the road as a default - every CPU cycle of every process gets a fair tick of work unless they've been intentionally nice'd or whatnot. People who need realtime work (classic use is for audio engineers who need near-zero latency in their hardware inputs like a MIDI sequencer, but also embedded hardware uses realtime a lot) reconfigure their system(s) to that to that need; for desktop-priority users there are ways to alter the CFS scheduler to help maintain desktop responsiveness.
Have a look to Github projects such as this one to learn how and what to tweak - not that you need to necessarily use this but it's a good point to start understanding how the mojo works and what you can do even on your own with a few sysctl tweaks to get a better desktop experience while your rust code is compiling in the background. https://github.com/igo95862/cfs-zen-tweaks (in this project you're looking at the set-cfs-zen-tweaks.sh file and what it's tweaking in /proc so you can get hints on where you research goals should lead - most of these can be set with a sysctl)
There's a lot to learn about this so I hope this gets you started down the right path on searches for more information to get the exact solution/recipe which works for you.
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%.
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:
- 3x missing from apnews.com
- 2x missing from www.theguardian.com
- 1x missing from www.aljazeera.com
- 2x "link-icon only" to www.reuters.com
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.
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 - )
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).