Searching We Love Privacy Club

Twts matching #writing
Sort by: Newest, Oldest, Most Relevant

**(#cmttsmq) Note for reference I was trying to write and fix this rule (fixed version below):

# Ignore Content-Type restrictions for Git
S ...**
Note for reference I was trying to write and fix this rule ( _fixed version below_):

Ignore Content-Type restrictions for Git

SecRule REQUEST_HEADERS:Host ā€œ@streq git.mills.ioā€ ā€œid:101,phase:1,t:none,nolog,ctl:ruleRemoveById=920420ā€

⌘ [Read more](https://twtxt.net/twt/n4ipixa)

⤋ Read More

(#f26jg3a) @kat Haha 🤣 If someone figures this out, please let me know šŸ™šŸ™ – In the meantime, I’m going to very soonā„¢ write a daemon …
@kat @yarn.girlonthemoon.xyz Haha 🤣 If someone figures this out, please let me know šŸ™šŸ™ – In the meantime, I’m going to very soonā„¢ write a daemon that will watch the audit log for repeated violations and add to the network firewall. ⌘ Read more

⤋ Read More

**(#7xqzija) I’m just basically learning now how ModSecurity rules work and how to write my own.

The builtin OWASP rules are already working nice …**
I’m just basically learning now how ModSecurity rules work and how to write my own.

The builtin OWASP rules are already working nicely šŸ‘Œ – And yeah I won’t include the WAF on every site block, probably just my main/primary domain where I tend to run demo services and other things. ⌘ Read more

⤋ Read More

everoddandeven proposes bounty for monero-cpp Python bindings module
everoddandeven1 has proposed a bounty2 for creating a Python module that exposes the core functionalities of the monero-cpp library 3:

This module should enable Python developers to interact with monero-cpp API using a Pythonic interface without needing to write or interact with C++ code directly.

Total Bounty: 0 XMR (to date)

Payout criteria overview

⤋ Read More

** Year in review, 2024 **
As a treat, I figured I could write a year in review kinda thing, too. In no particular order here are some reflections organized into some mostly sensical categories.

Health

Since recovering from my brain bleed and the subsequent repair procedures, this year I’ve enjoyed getting back into a routine of exercising. I’ve never been one to track numbers, or reps, or distances — I mostly exercise because I enjoy doing it. This year I got back into going for regular short runs, very long walks (sorry aging d … ⌘ Read more

⤋ Read More

we talk about programming like it is about writing code, but the code ends up being less important than the architecture, and the architecture ends up being less important than social issues. The success and failure of Ninja (2020) | Hacker News

⤋ Read More

One thing I’ve learned over the many years now (approaching a decade and a half now) about self-hosting is two things; 1) There are many ā€œassh …
One thing I’ve learned over the many years now ( approaching a decade and a half now) about self-hosting is two things; 1) There are many ā€œassholesā€ on the open Internet that will either attack your stuff or are incompetent and write stupid shitā„¢ that goes crazy on your stuff 2) You have to be careful about resources, especially memory and disk i/o. Especially disk i/o. this can kill your … ⌘ Read more

⤋ Read More

(#ywl4paq) Okay. Going to Settings -> Applications and creating a new Application Token with Repository Read/Write access works just fine. You c …
Okay. Going to Settings -> Applications and creating a new Application Token with Repository Read/Write access works just fine. You clone over https and push over https and user your username and token as creds. ⌘ Read more

⤋ Read More

(#ah5h6mq) @andros See – There isn’t really anythign specific about avatars or how big they should be, etc. The spec mostly talks about what’s …
@andros @twtxt.andros.dev See https://twtxt.dev – There isn’t really anythign specific about avatars or how big they should be, etc. The spec mostly talks about what’s possible and supported by clients and publishers of twtxt feeds. We have yet to write specific client/server recommendations. ⌘ Read more

⤋ Read More

The Node Resource Interface saysĀ ā€œhiā€Ā to WebAssembly
Community blog post by Sascha Grunert, CRI-O maintainer TheĀ Node Resource Interface (NRI)Ā allows users to write plugins forĀ Open Container Initiative (OCI)Ā compatible runtimes likeĀ CRI-OĀ andĀ containerd. These plugins are capable of making controlled changes to containers at dedicated points in… ⌘ Read more

⤋ Read More
In-reply-to » One benefit with bluesky is your username is also a website. And not a clunky URL with slashes and such. I wish twtxt adopted that. I have advocated for webfinger to for twtxt to let us do something like it with usernames. Nostr has something like it

@eapl.me@eapl.me why not https://domain.com/.well-known/twtxt/:domain/:user ?

the business card test is this can you write it on your business card and have someone you give it to be able to figure it out without added context?

  • phone number: yes because everyone knows what a phone number is.
  • email address: yes, everyone knows an email and their aol or prodigy will let them email.
  • twitter/x/insta/pintrest handle: no, whats a twitter? do i need to sign up?
  • domain name: yes its simple and you just type it in a browser right?
  • twtxt url: kinda? its a bit long and is that a forward slash? or a backward slash?

⤋ Read More

You know what’s amazing about programming? The power to automate boring or repetitive tasks effortlessly. Renaming hundreds of files, downloading GPX files from Komoot, or updating the visibility of countless statuses on Traewelling – sure, you could do it manually, but why would you, when you can write a quick script to handle it for you? It’s hands down the best life hack I’ve ever discovered! Big thanks to my parents for putting me on this path! ⌘ Read more

⤋ Read More

MacOS Sequoia 15.2 Update Released with ChatGPT Siri, Image Playground, Bug Fixes, & More
Apple has released MacOS Sequoia 15.2 as an update for Mac users running the Sequoia operating system. The software update includes new Apple Intelligence features including ChatGPT support for Siri, Image Playground image generation tools, along with some improvements to writing tools AI. Aside from AI, you’ll also find new abilities to share items in … [Read More](https://osxdaily.com/2024/12/11/macos-s … ⌘ Read more

⤋ Read More

Did I write here already that the reason why I love Twtxt so much is that it works without having to compile, install anything extra. Just the bin applications that come with 95% of all operating systems and you’re good to read and participate, giving you have a domain name somewhere to host the twtxt.txt file.

⤋ Read More

ā€œNo NAT November: My Month Without IPv4ā€
In his post ā€œNo NAT November: My Month Without IPv4ā€ security engineer Alex Haydock writes about the challenges of IPv6-only networks and explains techniques like DNS64, NAT64 and CLAT. An interesting read for someone like me, who doesn’t know much more about IPv6 than that support is still lacking in many places (like GitHub). ⌘ Read more

⤋ Read More

XMR registers 2.5-year high of $218 after ~31% surge
Monero (XMR/USD1) bulls have managed to essentially wipe all bear progress since May 2022 with an impressive under 9-hour ~31% surge yesterday from $166 to ~$218.

As I am writing this report, the reds are trying to force the price back under the 200 psychological level.

Provided bulls manage to reinforce the 175-185 support zone, we could see another attempt to break the local top. This could leave the next resistance around … ⌘ Read more

⤋ Read More

How to Instantly Write a Business Plan with AI on Mac, iPhone, iPad
While there are plenty of paid options to get a business plan, from business plan software, to books, to working with a consultant, or even outsourcing the entire thing, another option is available for iPhone, iPad, and Mac users, and it uses the magic of Apple Intelligence features and ChatGPT to instantly create a business … Read More ⌘ Read more

⤋ Read More

How to Find a Lost Apple Pencil
The Apple Pencil is a great accessory for iPad users, but obviously you can’t use an Apple Pencil if it’s lost, and it’s not particularly useful if it’s missing. Fortunately there are a few tricks that you can employ to help you find a lost Apple Pencil, so you can be back to your writing, … Read More ⌘ Read more

⤋ Read More
In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@eapl.me@eapl.me here are my replies (somewhat similar to Lyse’s and James’)

  1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

  2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

  3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

  4. Discovery: User-agent for discovery can become better. I’m working on a wrapper script in PHP, so you don’t need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that’s the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

  5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

  6. Languages: If the need is big then make a separate feed. I don’t mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it’s about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

  7. Emojis: I’m not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

⤋ Read More

**(#w7qc4ra) @eapl.me Regarding supporting languages:

That said, coming from platforms like X and Masto, where switching languages is easy, I n …**
@eapl.me @eapl.me Regarding supporting languages:

That said, coming from platforms like X and Masto, where switching languages is easy, I naturally read content and write into my timeline in at least three languages. Changing my ā€œaccountā€ is not a simple as switching languages, and in those platforms have another m … ⌘ Read more

⤋ Read More

Beta 2 of iOS 18.2, MacOS Sequoia 15.2, & iPadOS 18.2 Available for Testing
The second beta versions of iOS 18.2, MacOS Sequoia 15.2, and iPadOS 18.2 are now available for users participating in the beta testing programs for Apple system software. The new betas continue to focus on additional Apple Intelligence features, expanding beyond the writing tools, smart replies, and summary features what was initially introduced in iOS … [Read More](https://osxdail … ⌘ Read more

⤋ Read More

how to have fun while doing personal programming

how to have fun while doing personal programming

2024-11-02 02:23

well, just like the title says, i’m gonna show you how to have fun while doing
personal programming, at least, how i have fun while doing it. i also think
these things were crucial towards me learning to program as well.

don’t worry about:

  • writing nice code

  • writing repetitive code

  • hard-coded strings

  • optimization

  • about how idiomatic your code is

  • error chec … ⌘ Read more

⤋ Read More
In-reply-to » Three days from today, towards the end of the day, we in the US will have an idea of who the nation's presiding person will be for the next four years. In the 32 years I have lived here, I have never been more worried about an election outcome.

@quark@ferengi.one Yeah i’m in deep red here. the governor race is getting split between a red and a maga that is running a write in.. but even if they split the vote 50-50% they will still be greater than what the blue will get.

⤋ Read More

(#gctrz4q) > Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don�� …

Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don’t need to change anything. My ¼ -> ¼ thing is nothing more than a minor irritation which probably isn’t worth overthinking.

Yeah I’ve closed the PR, I just wanted to write it up and see what we all thought. Much easier to talk to a concrete spec proposal sometimes. … ⌘ Read more

⤋ Read More

(#gctrz4q) > What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic, I think …

What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic, I think it would achieve what you are trying to achieve with this content-type thing: if someone writes ¼ on a yarnd instance or any other client that wants to do this, it would get transformed, and other clients simply wouldn’t do the transformation. Every client that sup … ⌘ Read more

⤋ Read More
In-reply-to » @bender @prologic I'm not exactly asking yarnd to change. If you are okay with the way it displayed my twts, then by all means, leave it as is. I hope you won't mind if I continue to write things like 1/4 to mean "first out of four".

@bender@twtxt.net I try to avoid editing. I guess I would write 5/4, 6/4, etc, and hopefully my audience would be sympathetic to my failing.

Anyway, I don’t think my eccentric decision to number my twts in the style of other social media platforms is the only context where someone might write ¼ not meaning a quarter. E.g. January 4, to Americans.

I’m happy to keep overthinking this for as long as you are :-P

⤋ Read More
In-reply-to » @prologic I'm not a yarnd user, so it doesn't matter a whole lot to me, but FWIW I'm not especially keen on changing how I format my twts to work around yarnd's quirks.

@bender@twtxt.net @prologic@twtxt.net I’m not exactly asking yarnd to change. If you are okay with the way it displayed my twts, then by all means, leave it as is. I hope you won’t mind if I continue to write things like 1/4 to mean ā€œfirst out of fourā€.

What has text/markdown got to do with this? I don’t think Markdown says anything about replacing 1/4 with ¼, or other similar transformations. It’s not needed, because ¼ is already a unicode character that can simply be directly inserted into the text file.

What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic@twtxt.net, I think it would achieve what you are trying to achieve with this content-type thing: if someone writes 1/4 on a yarnd instance or any other client that wants to do this, it would get transformed, and other clients simply wouldn’t do the transformation. Every client that supports displaying unicode characters, including Jenny, would then display ¼ as ¼.

Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don’t need to change anything. My 1/4 -> ¼ thing is nothing more than a minor irritation which probably isn’t worth overthinking.

⤋ Read More

iOS 18.1 with Apple Intelligence Now Available to Download
Apple has released iOS 18.1 and iPadOS 18.1 to bring Apple Intelligence features to iPhone and iPad. The initial set of Apple Intelligence AI features include writing tools, summaries for messages and emails, and other handy capabilities. Apple Intelligence has strict system requirements however and is not available on all devices. Aside from Apple Intelligence, … [Read More](https://osxdaily.com/2024/10/28/ios-18-1- … ⌘ Read more

⤋ Read More

Simplified twtxt - I want to suggest some dogmas or commandments for twtxt, from where we can work our way back to how to implement different feature like replies/treads:

  1. It’s a text file, so you must be able to write it by hand (ie. no app logic) and read by eye. If you edit a post you change the content not the timestamp. Otherwise it will be considered a new post.

  2. The order of lines in a twtxt.txt must not hold any significant. The file is a container and each line an atomic piece of information. You should be able to run sort on a twtxt.txt and it should still work.

  3. Transport protocol should not matter, as long as the file served is the same. Http and https are preferred, so it is suggested that feed served via Gopher or Gemini also provide http(s).

  4. Do we need more commandments?

⤋ Read More

Release Candidates of iOS 18.1, MacOS Sequoia 15.1, & iPadOS 18.1 Available
Apple has issued release candidate builds of iOS 18.1, macOS Sequoia 15.1, and iPadOS 18.1, making them available for users enrolled in the beta testing programs for Apple system software. These versions are the first to include Apple Intelligence support on compatible devices. Initial Apple Intelligence features include functionality for summarizing data, writing tools, and … [Read … ⌘ Read more

⤋ Read More

Minix Z300 0DB Fanless Mini PC with 2.5GbE LAN and Dual 4K Display Support
The Minix Z300-0dB delivers efficient, quiet performance with a fanless passive cooling design that eliminates the need for traditional fans. Powered by the Intel Alder Lake-N N300 octa-core processor, it features Kimtigo premium RAM and a PCIe 3.0 x4 NVMe SSD for fast read and write speeds, enhancing productivity and response times. According to the […] ⌘ Read more

⤋ Read More

jeffro256 submits CCS proposal to get ā€˜Carrot’ reviewed by CypherStack
jeffro2561 has submitted a CCS proposal2 looking to get the Carrot 3 spec document peer reviewed by CypherStack4:

This CCS will provide funding for the first step towards a Carrot implementation in Monero. [..] The deliverable is a write-up which will include security proofs for all properties listed in section 9. [..] In the case that CypherStack requires more funds to com … ⌘ Read more

⤋ Read More

escapethe3RA: Looking for funding to maintain Monero Observer until 2026

Funding goal (24Q4+2025): 240 XMR

11 successful CCS proposals, 3500+ work hours, thousands of reports in over 3 years of thinking about, writing about, and dreaming about Monero.

That has been my sometimes rough yet always exciting secret life since 2021 and I wouldn’t change it for anything. More importantly, I owe it all to you. Thank you for supporting me since day 1 via the CCS.

Now, I am ready to skip the system and seek dire … ⌘ Read more

⤋ Read More
In-reply-to » @doesnm Agree. salty.im should allow the user to post multiple brokers on their webfinger so the client can find a working path.

Honestly… not much. Have abandon two projects (both private) on Golang and one related to cryptography. My mostly languages are Python and Javascript (also can PHP). After writing code on Go i spend same time on fixing dumb errors

⤋ Read More
In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

I share I did write up an algorithm for it at some point I think it is lost in a git comment someplace. I’ll put together a pseudo/go code this week.

Super simple:

Making a reply:

  1. If yarn has one use that. (Maybe do collision check?)
  2. Make hash of twt raw no truncation.
  3. Check local cache for shortest without collision
    • in SQL: select len(subject) where head_full_hash like subject || '%'

Threading:

  1. Get full hash of head twt
  2. Search for twts
    • in SQL: head_full_hash like subject || '%' and created_on > head_timestamp

The assumption being replies will be for the most recent head. If replying to an older one it will use a longer hash.

⤋ Read More

Recent #fiction #scifi #reading:

  • The Memory Police by Yōko Ogawa. Lovely writing. Very understated; reminded me of Kazuo Ishiguro. Sort of like Nineteen Eighty-Four but not. (I first heard it recommended in comparison to that work.)

  • Subcutanean by Aaron Reed; https://subcutanean.textories.com/ . Every copy of the book is different, which is a cool idea. I read two of them (one from the library, actually not different from the other printed copies, and one personalized e-book). I don’t read much horror so managed to be a little creeped out by it, which was fun.

  • The Wind from Nowhere, a 1962 novel by J. G. Ballard. A random pick from the sci-fi section; I think I picked it up because it made me imagine some weird 4-dimensional effect (ā€œfrom nowhereā€ meaning not in a normal direction) but actually (spoiler) it was just about a lot of wind for no reason. The book was moderately entertaining but there was nothing special about it.

Currently reading Scale by Greg Egan and Inversion by Aric McBay.

⤋ Read More

More thoughts about changes to twtxt (as if we haven’t had enough thoughts):

  1. There are lots of great ideas here! Is there a benefit to putting them all into one document? Seems to me this could more easily be a bunch of separate efforts that can progress at their own pace:

1a. Better and longer hashes.

1b. New possibly-controversial ideas like edit: and delete: and location-based references as an alternative to hashes.

1c. Best practices, e.g. Content-Type: text/plain; charset=utf-8

1d. Stuff already described at dev.twtxt.net that doesn’t need any changes.

  1. We won’t know what will and won’t work until we try them. So I’m inclined to think of this as a bunch of draft ideas. Maybe later when we’ve seen it play out it could make sense to define a group of recommended twtxt extensions and give them a name.

  2. Another reason for 1 (above) is: I like the current situation where all you need to get started is these two short and simple documents:
    https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html
    https://twtxt.readthedocs.io/en/latest/user/discoverability.html
    and everything else is an extension for anyone interested. (Deprecating non-UTC times seems reasonable to me, though.) Having a big long ā€œtwtxt v2ā€ document seems less inviting to people looking for something simple. (@prologic@twtxt.net you mentioned an anonymous comment ā€œyou’ve ruined twtxtā€ and while I don’t completely agree with that commenter’s sentiment, I would feel like twtxt had lost something if it moved away from having a super-simple core.)

  3. All that being said, these are just my opinions, and I’m not doing the work of writing software or drafting proposals. Maybe I will at some point, but until then, if you’re actually implementing things, you’re in charge of what you decide to make, and I’m grateful for the work.

⤋ Read More

5th Beta of iOS 18.1, MacOS Sequoia 15.1, iPadOS 18.1 with Apple Intelligence, Available for Testing
Apple has released the 5th beta versions of iOS 18.1, macOS Sequoia 15.1, and iPadOS 18.1, with Apple Intelligence support. The Apple Intelligence features that are included with these releases are mostly Writing Tools, summaries, and new Siri features, which allow you to do things like summarize emails, offer Smart Replies in Mail and Mes … ⌘ Read more

⤋ Read More
In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@prologic@twtxt.net Thanks for writing that up!

I hope it can remain a living document (or sequence of draft revisions) for a good long time while we figure out how this stuff works in practice.

I am not sure how I feel about all this being done at once, vs. letting conventions arise.

For example, even today I could reply to twt abc1234 with ā€œ(#abc1234) Edit: ā€¦ā€ and I think all you humans would understand it as an edit to (#abc1234). Maybe eventually it would become a common enough convention that clients would start to support it explicitly.

Similarly we could just start using 11-digit hashes. We should iron out whether it’s sha256 or whatever but there’s no need get all the other stuff right at the same time.

I have similar thoughts about how some users could try out location-based replies in a backward-compatible way (append the replyto: stuff after the legacy (#hash) style).

However I recognize that I’m not the one implementing this stuff, and it’s less work to just have everything determined up front.

Misc comments (I haven’t read the whole thing):

  • Did you mean to make hashes hexadecimal? You lose 11 bits that way compared to base32. I’d suggest gaining 11 bits with base64 instead.

  • ā€œClients MUST preserve the original hashā€ — do you mean they MUST preserve the original twt?

  • Thanks for phrasing the bit about deletions so neutrally.

  • I don’t like the MUST in ā€œClients MUST follow the chain of reply-to referencesā€¦ā€. If someone writes a client as a 40-line shell script that requires the user to piece together the threading themselves, IMO we shouldn’t declare the client non-conforming just because they didn’t get to all the bells and whistles.

  • Similarly I don’t like the MUST for user agents. For one thing, you might want to fetch a feed without revealing your identty. Also, it raises the bar for a minimal implementation (I’m again thinking again of the 40-line shell script).

  • For ā€œwho followsā€ lists: why must the long, random tokens be only valid for a limited time? Do you have a scenario in mind where they could leak?

  • Why can’t feeds be served over HTTP/1.0? Again, thinking about simple software. I recently tried implementing HTTP/1.1 and it wasn’t too bad, but 1.0 would have been slightly simpler.

  • Why get into the nitty-gritty about caching headers? This seems like generic advice for HTTP servers and clients.

  • I’m a little sad about other protocols being not recommended.

  • I don’t know how I feel about including markdown. I don’t mind too much that yarn users emit twts full of markdown, but I’m more of a plain text kind of person. Also it adds to the length. I wonder if putting a separate document would make more sense; that would also help with the length.

⤋ Read More

I wrote some code to try out non-hash reply subjects formatted as (replyto ), while keeping the ability to use the existing hash style.

I don’t think we need to decide all at once. If clients add support for a new method then people can use it if they like. The downside of course is that this costs developer time, so I decided to invest a few hours of my own time into a proof of concept.

With apologies to @movq@www.uninformativ.de for corrupting jenny’s beautiful code. I don’t write this expecting you to incorporate the patch, because it does complicate things and might not be a direction you want to go in. But if you like any part of this approach feel free to use bits of it; I release the patch under jenny’s current LICENCE.

Supporting both kinds of reply in jenny was complicated because each email can only have one Message-Id, and because it’s possible the target twt will not be seen until after the twt referencing it. The following patch uses an sqlite database to keep track of known (url, timestamp) pairs, as well as a separate table of (url, timestamp) pairs that haven’t been seen yet but are wanted. When one of those ā€œwantedā€ twts is finally seen, the mail file gets rewritten to include the appropriate In-Reply-To header.

Patch based on jenny commit 73a5ea81.

https://www.falsifian.org/a/oDtr/patch0.txt

Not implemented:

  • Composing twts using the (replyto …) format.
  • Probably other important things I’m forgetting.

⤋ Read More