textlog
join
500 chars / 20 lines max · use #hashtags, @mentions and more
😀😃😄😁😆😅😂🤣😊😇🙂🙃😉😌😍🥰😘😋😛😜🤪🤨🧐🤓😎🤩🥳😏😒😞😔😟😕🙁☹️😣😖😫😩🥺😢😭😤😠😡🤬🤯😳🥵🥶😱😨😰😥😓🤗🤔🫣🤭🫢🤫🤥😶😐😑😬🙄😯😦😧😮😲🥱😴🤤😪😵🤐🥴🤢🤮🤧😷🤒🤕🤑🤠😈👿👻💀☠️👽🤖🎃😺😸😹😻😼😽🙀😿😾❤️🧡💛💚💙💜🖤🤍🤎💔❣️💕💞💓💗💖💘💝💟👍👎👌🤌✌️🤞🤟🤘🤙👈👉👆👇☝️🤚🖐️🖖👋🤝👏🙌🫶👐🤲🙏✍️💪👀👁️🧠🫀🫁🌱🌿☘️🍀🌸🌺🌻🌞🌙🔥🌈☀️☁️❄️🍕🍎🎉🎊🎈🎁🎵🎶🎨📚💡⚠️🚀🌍💻📱🔒🔑
example.com or
https://example.com
Regular links
[title](example.com) or
[title](https://example.com)
Markdown links
~text~ or ~~text~~
Strikethrough
*text* or **text**
Bold
_text_ or __text__
Underline
/text/
Italics
> text
Quote
:smile
Emoji autocomplete
1. first
2. second
3. third
Numbered lists
- first
- second
- third
Bulleted lists
Name  | Status | Count
----- | :----- | ----:
notes | ready  |     3
Tables
|redacted|
Redacted
`code`
Inline code
``````
Code fences
$inline$
Inline LaTeX
$$block$$
Block LaTeX
Which one? #poll
First option
Second option
PollsUse 2–8 unique options.
Which one? #quiz
Wrong answer
> Correct answer

Explanation revealed after answering
QuizzesMark exactly one of 2–8 unique answers with >. Text after a blank line is revealed after answering.
Visible text #spoiler
Hidden text
SpoilersText after #spoiler is hidden until revealed. Aliases: #tldr, #sensitive, #contentwarning, #cw, and #triggerwarning.
Going hiking #map
Kallikratis, Crete
MapsShows a map preview for the first location line. Alias: #location.
#flying Heraklion to Berlin
FlightsHover over the itinerary to see a map connecting the airports. The next three words form the itinerary: airport, to (or → or ->), airport. Use single-word airport names or IATA/ICAO codes.
Today #todo
[ ] First task
[x] Finished task
TodosOnly [ ] and [x] lines become items. Click your items to toggle them.
Run this #exec
```js
console.log(6 * 7)
```
Executable codeRuns the next language-tagged code fence and shows its output beneath the note.
Keep this visible #pin
Pinned notesYour latest #pin is shown first on your profile, independently for notes and replies.
No more replies #lock
Locked conversationsPrevents new replies to this note and every reply beneath it.
About textlog #meta
Meta conversationsKeeps this note and its replies out of public discovery feeds. Aliases: #tlog and #textlog.
Continue quietly #whisper
Whisper conversationsKeeps the branch out of all and hot. Participants, mentions, and tag followers can receive it in my feed. It remains public elsewhere.
For @someone and @another #private
Private conversationsOnly the author and mentioned users can read this branch.
Answer before reading #HiddenReplies
Hidden repliesHides all replies until you reply.

Any conversation

profilefollow#Emacsnotesfollow, dev, life, random stuff. the netherlands.wrote:
Returned after a ride on bikes around the lake with the boy. Did stop for workout, 🏋️‍♂️ did pull-ups, push-ups and squats. Love the place we live in.
profilefollowOld school metallian, hobbyist developer writing things mostly in Rust…mostlywrote:
Changed my theme to dracula! Love it. This site is such a blessing.
🤸profilefollowcreative technologist creator of textlogreplied toprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:
Yeah it's happening to people. It's because the email contains a link and we don't have the reputation yet. Not sure what to do, have you tried reporting it as 'Not spam' in your client? Maybe if enough people do that it will fix. Gmail works ok.
profilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to🤸profilefollowcreative technologist creator of textlog:
Yup, I am moving them out of it. It might take a while, but eventually should be OK. All good, hopefully now with a password I will not have much use for them any more.
profilefollowhallucinating with llms...wrote:
in a hackathon rn. building a cloud platform for agents on my homelab.
profilefollowfather, cyclist, #haskellnotesfollow, #emacsnotesfollowwrote:
Really glad to be using Haskell for work - especially in today's climate with agentic coding. Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself. We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker. #haskellnotesfollow #ainotesfollow
... because letting the agent run docker gives them a too-easy escape hatch from their sandbox. So we're currently stuck with using VMs. This turns out to be tricky but seems do-able. My current approach is to provision a VM image and use Incus for the execution. My main goal is to keep my current workflow of local/non-agent dev working seamlessly and share the source with the VM/agent.
This means sharing my working dirs with the agent VM but overlaying artifact dirs from VM-owned block devices so we don't take too big of an IO perf hit. I also don't want the agent to be able to git push so that means we need some quirky git config to rewrite origin paths and thread through some agent specific PATs ("thanks" GitHub) for read-only repo access. These ALSO need to be threaded through to the development containers - they need to clone private repos.
... in the end, this seems to work but I haven't lived with it for long. There are still some quality of life issues to work out, but I think it'll work out. At this point, I've removed all coding agents from my host - and that's nice.
It's tangential to the sandboxing topic, really. I started the first post with a broader intent in mind and then elaborated on the sandboxing setup I'm working on. For AI-assisted coding, though, it's nice because Haskell provides a lot of feedback earlier in the development process compared to lots of other languages. It tends to work once it compiles (obviously not all the time).
🤸profilefollowcreative technologist creator of textlogwrote:
I hate crawlers that don’t advertise they’re crawlers. ’n badly written. They don’t respect the canonical URLs so they keep getting themselves into a loop instead of actually crawling the site properly. They make the logs really hard to read. Can’t block them they’re distributed.
For this particular problem though, I feel like if the crawlers are coming from domestic / residential IP addresses and they lack a distinctive http header or user agent, it is indistinguishable from a denial of service attack and must be treated as such.
It would require permaban on IPs which would require permalogging of IPs in order to track them, and we are currently obfuscating them before hitting the DB with daily rotating salt so an anonymous user can’t be tracked. So we’d have to give up privacy/security :/
profilefollowlate is the hour in which this conjuror chooses to appearreplied to🤔profilefollowHai I am ku:
But as long as people can still use the site it's OK, right? Seems like the problem is often self-inflicted, either because the site is so bloated that answering even GET-requests is burdensome, or because they're trying to monetize the data and so must block non-paying scrapers.
profilefollowlate is the hour in which this conjuror chooses to appearwrote:
The rise of postmodern cuisine: "The beverage's photogenic bright green color proved particularly well-suited to social media platforms like Instagram and TikTok, helping it gain viral popularity among wellness enthusiasts and influencers." (Wikipedia, "Matcha") #teanotesfollow #philosophynotesfollow
آپ کے دیئے گئے #جملےnotesfollow کی درست اور معیاری #اردوnotesfollow اصلاح "کوئی #نذرانہnotesfollow لے کر آیا ہوں، میں دیوانہ تیرے لیے" ہے۔ اس جملے میں 'نجراجہ' کی جگہ درست لفظ نذرانہ (تحفہ) ہے، 'لیکر' کو الگ الگ لے کر لکھا جاتا ہے، اور 'لئے' کی درست املا لیے ہے۔ #Grammarnotesfollow #Urdunotesfollow #Languagenotesfollow #Learningnotesfollow
The correct and standard #Urdunotesfollow correction of your given #sentencenotesfollow is "I have brought a #giftnotesfollow, I am crazy for you". In this sentence, the correct word for 'najraja' is 'nazran' (gift), 'lekar' is written separately, and 'lay' is spelled correctly. #Grammarnotesfollow #Urdunotesfollow #Languagenotesfollow #Learningnotesfollow
看到其他文章有自動翻譯,我覺得很酷
I think it's really cool to see other articles with automatic translation.
所以我來嘗試一下自動翻譯的文章功能,但發現自動翻譯只有在瀏覽器上,行動裝置要自己手動按翻譯功能。
So I tried the automatic article translation feature, but found that automatic translation only works in the browser; on mobile devices, you have to manually press the translation button.