#attachments — Public Fediverse posts on home.social

Erik van Straten @[email protected] · 2026-04-28 · 18:40 UTC

@pascaline : I hope that I understand your issue correctly.

If an email message asks the email program (used by the recipient) to load external content (which usually happens each time the recipient opens it), typically the sender is considered to be impolite.

The reason is that the sender can observe whether, and if so when exactly, someone opens the email. Also, the IP-address of the recipient is revealed to the sender (that is, to the server hosting the external content).

This trick is commonly used by marketing companies and/or spammers.

In addition, albeit not very common, sometimes email programs have vulnerabilities that cause code execution when external malware is loaded that exploits such a vulnerability.

Finally spam filters don't like external content for multiple reasons, such as: it may be a "spammy" image, it may change over time, and it can even be something that looks like an image but actually (also) contains executable code.

OTOH, sending emails with huge attachments is not considered polite either.

Your best bet may be to include a highly compressed (relatively low quality) sample of a huge (in bytes) image, and add a link (to be manually clicked) that allows the recipient to download the full version.

#Email #Attachments #RemoteContent #MIME

#email #attachments #remotecontent #mime

trip - with Anarcho-Cougarism! @[email protected] · 2026-03-28 · 15:49 UTC

I'll take a guess on what the telegram exploit is. Mostly because people seem to be concerned and there is little information and the recommendation appears to be "Disable automatic media download" but I am worried about the mixture of severity and lack of information and at least thought to speculate based on information available and what I can see.

--

Now, please do keep in mind that I have spent like 15mins on this and have hardly done anything serious but hearing "Please do this thing to prevent an exploit but I don't have details" isn't exactly ideal. I'm also jumping to some conclusions as what is exploitable

--

1. Got notified regarding to this CVE via a friend.

* CVE for Telegram - https://bsky.app/profile/redteef.bsky.social/post/3mi3ki5tip227

The main advice appears to be disable automatic media download - My assumption is that some library related to processing media appears to have some issue.

2. pmap of my running telegram process - Saw libjxl and wondered what state it was in (Refer to media attached)

3. Looked up issues related to libjxl on github - https://github.com/libjxl/libjxl/issues/4539
and https://github.com/libjxl/libjxl/issues/4539
"ibjxl JPEG XL decoder crash due to uninitialized pointer access in malformed images" - One of the screenshots output "Illegal Instruction (Core Dump)" which is sinister, this can include the CPU attempting to execute an instruction it doesn't understand and if that segment can be manipulated, this can potentially lead to arbitrary code execution.

Which then also lead me to this: https://github.com/advisories/GHSA-76gx-97cq-65f5

---

Disclaimer: I can't say it is even about libjxl or related to the CVE mentioned in 1 but I can at least see an attack like so: (which gives weight to disabling media for telegram).

1. Attacker crafts a suitable image to manipulate the decoder, image contains data that can either manipulate the pointer and/or data that the segment it could point to (for reference, just enough data to get a shell or establish a connection to something else is enough)

2. Attacker sends the image on a platform where the user using this library can then decode it.

3. The image that is decoded will then be able to execute the payload - Attacker could gain control via this method.

---

While this may seem silly but please also do not hound or abuse the devs at libjxl. Last thing I want are people who are trying to do their best to fix the issues I have listed and do not control what telegram includes in their builds.

#telegram #cve #attachments #media #libjxl #psa

trip - with Anarcho-Cougarism! @[email protected] · 2026-03-28 · 15:49 UTC

I'll take a guess on what the telegram exploit is. Mostly because people seem to be concerned and there is little information and the recommendation appears to be "Disable automatic media download" but I am worried about the mixture of severity and lack of information and at least thought to speculate based on information available and what I can see.

--

Now, please do keep in mind that I have spent like 15mins on this and have hardly done anything serious but hearing "Please do this thing to prevent an exploit but I don't have details" isn't exactly ideal. I'm also jumping to some conclusions as what is exploitable

--

1. Got notified regarding to this CVE via a friend.

* CVE for Telegram - https://bsky.app/profile/redteef.bsky.social/post/3mi3ki5tip227

The main advice appears to be disable automatic media download - My assumption is that some library related to processing media appears to have some issue.

2. pmap of my running telegram process - Saw libjxl and wondered what state it was in (Refer to media attached)

3. Looked up issues related to libjxl on github - https://github.com/libjxl/libjxl/issues/4539
and https://github.com/libjxl/libjxl/issues/4539
"ibjxl JPEG XL decoder crash due to uninitialized pointer access in malformed images" - One of the screenshots output "Illegal Instruction (Core Dump)" which is sinister, this can include the CPU attempting to execute an instruction it doesn't understand and if that segment can be manipulated, this can potentially lead to arbitrary code execution.

Which then also lead me to this: https://github.com/advisories/GHSA-76gx-97cq-65f5

---

Disclaimer: I can't say it is even about libjxl or related to the CVE mentioned in 1 but I can at least see an attack like so: (which gives weight to disabling media for telegram).

1. Attacker crafts a suitable image to manipulate the decoder, image contains data that can either manipulate the pointer and/or data that the segment it could point to (for reference, just enough data to get a shell or establish a connection to something else is enough)

2. Attacker sends the image on a platform where the user using this library can then decode it.

3. The image that is decoded will then be able to execute the payload - Attacker could gain control via this method.

---

While this may seem silly but please also do not hound or abuse the devs at libjxl. Last thing I want are people who are trying to do their best to fix the issues I have listed and do not control what telegram includes in their builds.

#telegram #cve #attachments #media #libjxl #psa

trip - with Anarcho-Cougarism! @[email protected] · 2026-03-28 · 15:49 UTC

I'll take a guess on what the telegram exploit is. Mostly because people seem to be concerned and there is little information and the recommendation appears to be "Disable automatic media download" but I am worried about the mixture of severity and lack of information and at least thought to speculate based on information available and what I can see.

--

Now, please do keep in mind that I have spent like 15mins on this and have hardly done anything serious but hearing "Please do this thing to prevent an exploit but I don't have details" isn't exactly ideal. I'm also jumping to some conclusions as what is exploitable

--

1. Got notified regarding to this CVE via a friend.

* CVE for Telegram - https://bsky.app/profile/redteef.bsky.social/post/3mi3ki5tip227

The main advice appears to be disable automatic media download - My assumption is that some library related to processing media appears to have some issue.

2. pmap of my running telegram process - Saw libjxl and wondered what state it was in (Refer to media attached)

3. Looked up issues related to libjxl on github - https://github.com/libjxl/libjxl/issues/4539
and https://github.com/libjxl/libjxl/issues/4539
"ibjxl JPEG XL decoder crash due to uninitialized pointer access in malformed images" - One of the screenshots output "Illegal Instruction (Core Dump)" which is sinister, this can include the CPU attempting to execute an instruction it doesn't understand and if that segment can be manipulated, this can potentially lead to arbitrary code execution.

Which then also lead me to this: https://github.com/advisories/GHSA-76gx-97cq-65f5

---

Disclaimer: I can't say it is even about libjxl or related to the CVE mentioned in 1 but I can at least see an attack like so: (which gives weight to disabling media for telegram).

1. Attacker crafts a suitable image to manipulate the decoder, image contains data that can either manipulate the pointer and/or data that the segment it could point to (for reference, just enough data to get a shell or establish a connection to something else is enough)

2. Attacker sends the image on a platform where the user using this library can then decode it.

3. The image that is decoded will then be able to execute the payload - Attacker could gain control via this method.

---

While this may seem silly but please also do not hound or abuse the devs at libjxl. Last thing I want are people who are trying to do their best to fix the issues I have listed and do not control what telegram includes in their builds.

#telegram #cve #attachments #media #libjxl #psa

trip - with Anarcho-Cougarism! @[email protected] · 2026-03-28 · 15:49 UTC

I'll take a guess on what the telegram exploit is. Mostly because people seem to be concerned and there is little information and the recommendation appears to be "Disable automatic media download" but I am worried about the mixture of severity and lack of information and at least thought to speculate based on information available and what I can see.

--

Now, please do keep in mind that I have spent like 15mins on this and have hardly done anything serious but hearing "Please do this thing to prevent an exploit but I don't have details" isn't exactly ideal. I'm also jumping to some conclusions as what is exploitable

--

1. Got notified regarding to this CVE via a friend.

* CVE for Telegram - https://bsky.app/profile/redteef.bsky.social/post/3mi3ki5tip227

The main advice appears to be disable automatic media download - My assumption is that some library related to processing media appears to have some issue.

2. pmap of my running telegram process - Saw libjxl and wondered what state it was in (Refer to media attached)

3. Looked up issues related to libjxl on github - https://github.com/libjxl/libjxl/issues/4539
and https://github.com/libjxl/libjxl/issues/4539
"ibjxl JPEG XL decoder crash due to uninitialized pointer access in malformed images" - One of the screenshots output "Illegal Instruction (Core Dump)" which is sinister, this can include the CPU attempting to execute an instruction it doesn't understand and if that segment can be manipulated, this can potentially lead to arbitrary code execution.

Which then also lead me to this: https://github.com/advisories/GHSA-76gx-97cq-65f5

---

Disclaimer: I can't say it is even about libjxl or related to the CVE mentioned in 1 but I can at least see an attack like so: (which gives weight to disabling media for telegram).

1. Attacker crafts a suitable image to manipulate the decoder, image contains data that can either manipulate the pointer and/or data that the segment it could point to (for reference, just enough data to get a shell or establish a connection to something else is enough)

2. Attacker sends the image on a platform where the user using this library can then decode it.

3. The image that is decoded will then be able to execute the payload - Attacker could gain control via this method.

---

While this may seem silly but please also do not hound or abuse the devs at libjxl. Last thing I want are people who are trying to do their best to fix the issues I have listed and do not control what telegram includes in their builds.

#telegram #cve #attachments #media #libjxl #psa

#psa #libjxl #media #attachments #cve #telegram

trip - with Anarcho-Cougarism! @[email protected] · 2026-03-28 · 15:49 UTC

I'll take a guess on what the telegram exploit is. Mostly because people seem to be concerned and there is little information and the recommendation appears to be "Disable automatic media download" but I am worried about the mixture of severity and lack of information and at least thought to speculate based on information available and what I can see.

--

Now, please do keep in mind that I have spent like 15mins on this and have hardly done anything serious but hearing "Please do this thing to prevent an exploit but I don't have details" isn't exactly ideal. I'm also jumping to some conclusions as what is exploitable

--

1. Got notified regarding to this CVE via a friend.

* CVE for Telegram - https://bsky.app/profile/redteef.bsky.social/post/3mi3ki5tip227

The main advice appears to be disable automatic media download - My assumption is that some library related to processing media appears to have some issue.

2. pmap of my running telegram process - Saw libjxl and wondered what state it was in (Refer to media attached)

3. Looked up issues related to libjxl on github - https://github.com/libjxl/libjxl/issues/4539
and https://github.com/libjxl/libjxl/issues/4539
"ibjxl JPEG XL decoder crash due to uninitialized pointer access in malformed images" - One of the screenshots output "Illegal Instruction (Core Dump)" which is sinister, this can include the CPU attempting to execute an instruction it doesn't understand and if that segment can be manipulated, this can potentially lead to arbitrary code execution.

Which then also lead me to this: https://github.com/advisories/GHSA-76gx-97cq-65f5

---

Disclaimer: I can't say it is even about libjxl or related to the CVE mentioned in 1 but I can at least see an attack like so: (which gives weight to disabling media for telegram).

1. Attacker crafts a suitable image to manipulate the decoder, image contains data that can either manipulate the pointer and/or data that the segment it could point to (for reference, just enough data to get a shell or establish a connection to something else is enough)

2. Attacker sends the image on a platform where the user using this library can then decode it.

3. The image that is decoded will then be able to execute the payload - Attacker could gain control via this method.

---

While this may seem silly but please also do not hound or abuse the devs at libjxl. Last thing I want are people who are trying to do their best to fix the issues I have listed and do not control what telegram includes in their builds.

#telegram #cve #attachments #media #libjxl #psa

WPNEWS.io @[email protected] · 2026-03-04 · 21:37 UTC

Learn how to add extra information to products using a workaround of WooCommerce’s default features and the WooCommerce Product Attachment plugin.

#WordPress #Guides #WooCommerce #attachments #Dotstore #productpage
https://ift.tt/aeBDPrO

#wordpress #guides #woocommerce #attachments #dotstore #productpage

Mike McBride on M365 @[email protected] · 2026-01-22 · 02:12 UTC

Worth Reading – Carvana and the New Hyperlink Fight: “Contemporaneous” Isn’t Automatic—It’s Earned

As someone responding to an eDiscovery request, the flip side of that statement is, of course, true. Kelly goes into some detail, but for my M365 folks: if you're going to argue that the version of the document when shared is too difficult to collect, you will need to show your work. That will need to include a whole lot more than saying you don't know how to do it, or that it's difficult.

https://mikemcbride365.com/2026/01/21/worth-reading-carvana-and-the-new-hyperlink-fight-contemporaneous-isnt-automatic-its-earned/

#attachments #court #legal #sharing

Lukas Beran @[email protected] · 2025-06-09 · 06:34 UTC

𝗛𝗼𝘄 𝘁𝗼 𝗯𝗹𝗼𝗰𝗸 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗳𝗶𝗹𝗲 𝘁𝘆𝗽𝗲𝘀 𝗶𝗻 𝗲𝗺𝗮𝗶𝗹 𝗮𝘁𝘁𝗮𝗰𝗵𝗺𝗲𝗻𝘁𝘀

A very common source of infection is email. Everyone uses email and threat actors take advantage of it. Either in the form of phishing or in the form of malicious attachments.

There are very advanced protection options within Office 365. Whether it be within Exchange Online Protection, which is included in all Office 365 / Exchange Online plans, or within Safe Attachments, which is an extension within Microsoft Defender for Office 365.

But a very effective protection is the very simple blocking of unwanted file types within email attachments. You simply block what is unwanted, making it very easy and effective to block many potentially malicious files.

📺 Watch my YouTube video bellow 👇 👇
https://youtu.be/dFlD_CH5Kp8

#cswrld #videotutorial #email #attachments #filter #office365 #exchangeonline

#cswrld #videotutorial #email #attachments #filter #office365

Lukas Beran @[email protected] · 2025-06-09 · 06:34 UTC

𝗛𝗼𝘄 𝘁𝗼 𝗯𝗹𝗼𝗰𝗸 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗳𝗶𝗹𝗲 𝘁𝘆𝗽𝗲𝘀 𝗶𝗻 𝗲𝗺𝗮𝗶𝗹 𝗮𝘁𝘁𝗮𝗰𝗵𝗺𝗲𝗻𝘁𝘀

A very common source of infection is email. Everyone uses email and threat actors take advantage of it. Either in the form of phishing or in the form of malicious attachments.

There are very advanced protection options within Office 365. Whether it be within Exchange Online Protection, which is included in all Office 365 / Exchange Online plans, or within Safe Attachments, which is an extension within Microsoft Defender for Office 365.

But a very effective protection is the very simple blocking of unwanted file types within email attachments. You simply block what is unwanted, making it very easy and effective to block many potentially malicious files.

📺 Watch my YouTube video bellow 👇 👇
https://youtu.be/dFlD_CH5Kp8

#cswrld #videotutorial #email #attachments #filter #office365 #exchangeonline

#cswrld #videotutorial #email #attachments #filter #office365

Lukas Beran @[email protected] · 2025-06-09 · 06:34 UTC

𝗛𝗼𝘄 𝘁𝗼 𝗯𝗹𝗼𝗰𝗸 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗳𝗶𝗹𝗲 𝘁𝘆𝗽𝗲𝘀 𝗶𝗻 𝗲𝗺𝗮𝗶𝗹 𝗮𝘁𝘁𝗮𝗰𝗵𝗺𝗲𝗻𝘁𝘀

A very common source of infection is email. Everyone uses email and threat actors take advantage of it. Either in the form of phishing or in the form of malicious attachments.

There are very advanced protection options within Office 365. Whether it be within Exchange Online Protection, which is included in all Office 365 / Exchange Online plans, or within Safe Attachments, which is an extension within Microsoft Defender for Office 365.

But a very effective protection is the very simple blocking of unwanted file types within email attachments. You simply block what is unwanted, making it very easy and effective to block many potentially malicious files.

📺 Watch my YouTube video bellow 👇 👇
https://youtu.be/dFlD_CH5Kp8

#cswrld #videotutorial #email #attachments #filter #office365 #exchangeonline

#exchangeonline #office365 #filter #attachments #email #videotutorial

Lukas Beran @[email protected] · 2025-06-09 · 06:34 UTC

𝗛𝗼𝘄 𝘁𝗼 𝗯𝗹𝗼𝗰𝗸 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗳𝗶𝗹𝗲 𝘁𝘆𝗽𝗲𝘀 𝗶𝗻 𝗲𝗺𝗮𝗶𝗹 𝗮𝘁𝘁𝗮𝗰𝗵𝗺𝗲𝗻𝘁𝘀

A very common source of infection is email. Everyone uses email and threat actors take advantage of it. Either in the form of phishing or in the form of malicious attachments.

There are very advanced protection options within Office 365. Whether it be within Exchange Online Protection, which is included in all Office 365 / Exchange Online plans, or within Safe Attachments, which is an extension within Microsoft Defender for Office 365.

But a very effective protection is the very simple blocking of unwanted file types within email attachments. You simply block what is unwanted, making it very easy and effective to block many potentially malicious files.

📺 Watch my YouTube video bellow 👇 👇
https://youtu.be/dFlD_CH5Kp8

#cswrld #videotutorial #email #attachments #filter #office365 #exchangeonline

#cswrld #videotutorial #email #attachments #filter #office365

OpenXE ERP Project @openxe · 2022-11-21 · 09:16 UTC

Today we like to present a feature of which we are particularly proud of: The advanced #ticketsystem.

It is the central #tool to manage all #customer #email #communication.

Improvements compared to the old #xentral ticketsystem are:

- Outgoing #attachments are archived
- Unlimited number of attachments
- Comments history
- Flexible status management
- Batch processing
- Multiple recipients and CC

#erp #erpsoftware #freesoftware #agpl #gpl #xentral #crm #wawision #openxe #warenwirtschaft

#ticketsystem #tool #customer #email #communication #xentral

F0rm4t @[email protected] · 2023-05-07 · 13:56 UTC

I suggest to have a look at "Email Protection Basics" blog series:

1. Bulk Email: https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/email-protection-basics-in-microsoft-365-bulk-email/ba-p/3445337

2. Spam & Phish: https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/email-protection-basics-in-microsoft-365-spam-amp-phish/ba-p/3555712

3. Spoof and Impersonation: https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/email-protection-basics-in-microsoft-365-spoof-and-impersonation/ba-p/3562938

4. Anti-malware, Safe Attachments, and Quarantine: https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/email-protection-basics-in-microsoft-365-anti-malware-safe/ba-p/3791516

#mdo #emailsecurity #email #collaboration #spoofing #impersonation #malware #attachments #safeattachments #xdr #microsoft #microsoftsecurity #microsoft365 #exchangeonline #spam #bulkemail #quarantine #office365 #azure #cloud #cloudsecurity #soc #analyst

#mdo #emailsecurity #email #collaboration #spoofing #impersonation

ReadingFaithfully.org☸📗 @[email protected] · 2025-01-21 · 00:03 UTC

🌱 Today’s #DailySutta:

Ud 2.4 Sakkārasutta: Esteem

“Contacts strike because of attachment…”

Read the sutta
📖 https://daily.readingfaithfully.org/ud-2-4-sakkarasutta-esteem/?=MDS

Get these by email
✉ https://daily.readingfaithfully.org?=MSUDS

#attachments #inspiring #patience #Udana #Theravada #PaliCanon #RealBuddhaQuotes #Suttas #Dhamma #Buddhism #Buddha

#dailysutta #attachments #inspiring #patience #udana #theravada

Karl Voit :emacs: :orgmode: @[email protected] · 2024-12-10 · 14:02 UTC

Offenbar ist es seit Jahren immer mehr Usus, dass Firmen Informationen in Form von "nichtssagende E-Mails mit wesentlichen Informationen nur in #PDF-Anhängen" verschicken anstatt die Information direkt in der E-Mail als normalen Text zu schreiben.

Was hältst du davon? 🤔

#email #PIM #attachments #Anhänge

#pdf #email #pim #attachments #anhange

razzlom is always sad @[email protected] · 2024-09-28 · 11:44 UTC

Here @razzlom share his wisdom! :blobfoxwitch:

If you have video file like this (pic 1) and you want video file like that (pic 2) just run this command:

ffmpeg -i INPUT.mkv -map 0:v -c:v copy -disposition:v default -map 0:a:m:language:jpn -c:a libopus -b:a 128k -q:a 0 -disposition:a default -map 0:s:m:language:rus -c:s copy -disposition:s default -map 0:t -c:t copy OUTPUT.mkv

What does this command do?

-i INPUT.mkv - original file.

-map 0:v -c:v copy -disposition:v default - copy video track without change and add "default" flag.

-map 0:a:m:language:jpn -c:a libopus -b:a 128k -q:a 0 -disposition:a default - take audio track with "Japanese" language flag, convert it to opus file format and add "default" flag.

-map 0:s:m:language:rus -c:s copy -disposition:s default - take subtitle track with "Russian" language flag and add "default" flag.

-map 0:t -c:t copy - copy all attachments without change.

OUTPUT.mkv - result file.

Now your video files are beautiful! :blobfoxaww:

#ffmpeg #video #audio #subtitles #attachments #mkv #opus

#ffmpeg #video #audio #subtitles #attachments #mkv

César Pinto Castillo @[email protected] · 2024-02-23 · 11:10 UTC

I'm sure there's a good reason, but it's unfortunate that we can't present alerts in #SwiftUI #RealityView #Attachments

```
Presentations are not permitted within volumetric window scenes
```

#realityKit #appleVisionPro #visionOS

#swiftui #realityview #attachments #realitykit #applevisionpro #visionos

Zee @[email protected] · 2024-01-30 · 00:32 UTC

It looks like the #UK wants to have a look into everyone’s #data.

This mustn’t be allowed to happen.

#Security #privacy #dragnet #harvesting #chat #messages #messenger #posts #email #entertainment #music #attachments #AroundTheWorld

#Apple warns proposed UK #law will affect #software #updates around the world | Ars Technica

https://arstechnica.com/tech-policy/2024/01/apple-accuses-uk-of-power-grab-enabling-secret-veto-over-security-updates/

#updates #software #law #apple #aroundtheworld #attachments

Dr. Juande Santander-Vela @[email protected] · 2023-11-21 · 14:13 UTC

Public Service Announcement: when you upload spreadsheets to Confluence, if you want them to display properly, please set up a printing area, and the relevant zoom information. Most of the time, setting them up to fit into 1 by 1 page is enough to make them massively more readable than the default setup…

(This is a note for future me as much as for yourselves 😉)

#PSA #Confluence #Attachments #Excel #ExcelAttachments

#psa #confluence #attachments #excel #excelattachments

HRH ginsterbusch @[email protected] · 2023-10-30 · 16:13 UTC

Today: What #dremel #attachments do I want to aquire next (aside of just having ordered my first Dremel) :D

Background: Currently preparing to modify a 10L computer case for AIO / liquid cooling and more.

#sffpc #SmallFormFactor #10l

#10l #smallformfactor #sffpc #attachments #dremel

Tigase @tigase · 2023-08-31 · 17:42 UTC

Were you aware that in the #BeagleIM, you can open, share, save, or delete all of the #attachments shared throughout a conversation? By simply clicking on the "i" icon, marked by the red rectangle in the screenshot, you can conveniently navigate through and interact with these attachments, enhancing your communication experience.

#beagleim #attachments

Petr Lynx Balák @[email protected] · 2023-08-26 · 18:17 UTC

Dnes jsem si dal mini pěší výpravu, na louku uprostřed lesa (asi 5km od domova), aby jsem seřídil novou airsoftovou zbraň M4 Keymode od CA (ARS4-8.5), trochu otestoval výstroj a udělal nějaké fotky 😸. Vystřílel jsem cca 800 kulí (0.25g), ale seřídil jsem to tak, že na 40 metrů trefím A4 papír 😼. Což mě docela překvapilo, vzhledem ke krátké hlavni (260mm), ale je o průměru 6.3mm a 125 m/s tomu také pomohlo 😺

https://photos.app.goo.gl/NEdUq1XiaYVnkfip6
https://www.instagram.com/p/Cwat87VMUxB/?img_index=1
#airsoft #gun #M4 #attachments #cz

#airsoft #gun #m4 #attachments #cz

Petr Lynx Balák @[email protected] · 2023-08-20 · 12:29 UTC

ENG: I've gone a bit crazy, and after 17 years I want to get back into airsoft 😹 Gun (short M4 Keymod from CA) and equipment is still on the way, but I'm pretty tight on budget so I had to make some stuff 😼

CZE: Jsem se trochu zbláznil, a po 17 letech se chci vrátit k airsoftu 😹 Zbraň (krátká M4 Keymod od CA) a výstroj je ještě na cestě, ale dost jsem si omezil rozpočet a tak jsem si nějaké věci musel vyrobit 😼

https://www.printables.com/cs/@LynxBaal/collections/794828

#3dprinting #Airsoft #Attachments #M4 #Guns #equipment

#3dprinting #airsoft #attachments #m4 #guns #equipment

EINGFOAN :donor: @[email protected] · 2023-07-29 · 19:55 UTC

is there a good "App" for #Email #security #testing. basically testing if #attachments / #links for attachment downloads are getting to an enduser

I may think of:

#zip files, #Macro enabled #doc, #iso, ....

#email #security #testing #attachments #links #zip

Patrick Stewart @[email protected] · 2023-05-01 · 17:57 UTC

I didn't make this phrase up, but I love it. I've said it over and over again to anyone who will listen.

You are a #walking, #talking #miracle of #nature.

You are the universe talking back to itself and there is nothing inherently wrong with that.

I wrote about it over the weekend, and I wanted to share it.

How to Break Free from Your #Attachments and Embrace #Change

https://www.thetaoistonline.org/post/how-to-break-free-from-your-attachments-and-embrace-change

#writer #writing @writing #blog #blogging

#walking #talking #miracle #nature #attachments #change

The Taoist Online on Medium @[email protected] · 2023-05-01 · 17:53 UTC

You are a walking, talking #miracle of #nature. Just ask the chief editor @Patrickstewart

How to Break Free from Your #Attachments and Embrace #Change

https://www.thetaoistonline.org/post/how-to-break-free-from-your-attachments-and-embrace-change

#blog #writing #writers @writing @writingcommunity

#miracle #nature #attachments #change #blog #writing

SteamDeckHQ @[email protected] · 2022-12-19 · 10:43 UTC

So #JSAUX announced their new #modular #SteamDeck case today and man, it looks like an amazing one! We break down each of the #attachments and #specifics about them and man, it looks like it could easily rival the #Killswitch with that #price point!

https://steamdeckhq.com/news/the-jsaux-modular-case-is-officially-on-the-way/

#jsaux #modular #steamdeck #attachments #specifics #killswitch

Karl Voit :emacs: :orgmode: @[email protected] · 2022-11-25 · 15:34 UTC

@rkbk @sachac @bzg To be honest, so far I haven't grasped #orgmode #attachments either.

I rarely use org-attach-set-directory for adding a dir property headings but mostly, I'm using links: my-dired-insert-lfile-link-list-to-other-org-window() from https://github.com/novoid/dot-emacs/blob/master/config.org

#orgmode #attachments