@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?

Righto, @eapl.me@eapl.me, ta for the writeup. Here we go. :-)

Metadata on individual twts are too much for me. I do like the simplicity of the current spec. But I understand where you’re coming from.

Numbering twts in a feed is basically the attempt of generating message IDs. It’s an interesting idea, but I reckon it is not even needed. I’d simply use location based addressing (feed URL + ‘#’ + timestamp) instead of content addressing. If one really wanted to, one could hash the feed URL and timestamp, but the raw form would actually improve disoverability and would not even require a richer client. But the majority of twtxt users in the last poll wanted to stick with content addressing.

yarnd actually sends If-Modified-Since request headers. Not only can I observe heaps of 304 responses for yarnds in my access log, but in Cache.FetchFeeds(…) we can actually see If-Modified-Since being deployed when the feed has been retrieved with a Last-Modified response header before: https://git.mills.io/yarnsocial/yarn/src/commit/98eee5124ae425deb825fb5f8788a0773ec5bdd0/internal/cache.go#L1278

Turns out etags with If-None-Match are only supported when yarnd serves avatars (https://git.mills.io/yarnsocial/yarn/src/commit/98eee5124ae425deb825fb5f8788a0773ec5bdd0/internal/handlers.go#L158) and media uploads (https://git.mills.io/yarnsocial/yarn/src/commit/98eee5124ae425deb825fb5f8788a0773ec5bdd0/internal/media_handlers.go#L71). However, it ignores possible etags when fetching feeds.

I don’t understand how the discovery URLs should work to replace the User-Agent header in HTTP(S) requests. Do you mind to elaborate?

Different protocols are basically just a client thing.

I reckon it’s best to just avoid mixing several languages in one feed in the first place. Personally, I find it okay to occasionally write messages in other languages, but if that happens on a more regularly basis, I’d definitely create a different feed for other languages.

Isn’t the emoji thing “just” a client feature? So, feed do not even have to state any emojis. As a user I’d configure my client to use a certain symbol for feed ABC. Currently, I can do a similar thing in tt where I assign colors to feeds. On the other hand, what if a user wants to control what symbol should be displayed, similar to the feed’s nick? Hmm. But still, my terminal font doesn’t even render most of emojis. So, Unicode boxes everywhere. This makes me think it should actually be a only client feature.

How to ace the Prometheus Certified Associate (PCA) exam
Community post originally published on Medium by Giorgi Keratishvili Introduction If you have worked on Kubernetes production systems at any time during the last 10 years and needed to check your pods or application uptime, resource consumption, HTTP error rates,… ⌘ Read more

[47°09′15″S, 126°43′18″W] Storm recedes – back to normal work

‘The Aloha Project’ announces new Haveno mainnet instance with zero fees
alohamarkus1 from The Aloha Project 2 has announced3 the launch of Haveno Aloha 4, a new public Haveno instance running on Monero’s main network that apparently doesn’t charge any fees:

So I have been working on an ‘alternate’ network [..] it’s out now on mainnet but should require some testing, if anyone wants to help? [..] we have generous sponsors, that means haveno-aloh … ⌘ Read more

Monero Research Lab meeting scheduled for 13 November 2024 1700 UTC
The next Monero Research Lab1 meeting is scheduled to take place on Wednesday, November 13th 2024 at 17:00 UTC on IRC-Libera/Matrix2 in the #monero-research-lab channels.

• Updates. What is everyone working on?
  
• Monero Research Computing Server hardware needs
  
• FCMP++ tx size and compute cost and MAX_INPUTS/MAX_OUTPUTS3
  
• FCMP++ Optimization Competition4
  
• R … ⌘ Read more

Cuprate Meeting scheduled for 12 November 2024 1800 UTC
The next Cuprate Meeting is scheduled1 to take place on Tuesday, November 12 2024 at 18:00 UTC on IRC-Libera/Matrix2 in the #cuprate channels.

Cuprate is an effort to create an alternative Monero node implementation.

Greetings
Updates: What is everyone working on?
Project: What is next for Cuprate?
Any other business

The meeting’s moderator should be Boog9003. Consult the Cuprate co … ⌘ Read more

hinto-janai completes third milestone for Cuprate CCS proposal
hinto-janai1 has completed2 the third milestone for their latest CCS proposal3 to work full-time on Cuprate 4 development:

Completing milestone 1 & 2 will likely take longer than expected. I am conservatively estimating this CCS will take ~30 days longer than originally expected to complete, ETA end of December.

Lints: integrated for all of Cuprate's librarie ... ⌘ [Read more](https://monero.observer/hinto-janai-completes-third-milestone-cuprate-ccs-proposal/)

@Codebuzz@www.codebuzz.nl I have separate mail boxes for private and work, but flattened both to have a simpler structure. For work, where we use Outlook, I am using categories for organising the mails and privately I am using Vivaldi’s labels system. The main idea is to use search and grouping through dynamic saved searches instead of static folders.

Hah, seems i cant connect to plain because irc+insecure://irc.mills.io also not work (my bouncer powered by soju)

** Broughlike dev log **
I’ve been working on the broughlike pretty steadily since my last update. The gameplay loop is pretty much unchanged, but I’ve added a fair bit of polish, and fixed a lot of bugs. I think it is honestly sort of boring to play, but I am excited to have this as the starting point for future projects…can you smell the roguelike!? I can!

The major fixes and improvements that I’ve made since my last update include:

• better way finding … ⌘ Read more

@prologic@twtxt.net hahahaha! If only was that easy. Wife is pretty stressed out at work with new duties. At the same time people are getting laid off. So, it truly is a dilemma, and something that must be done carefully. I can wait. I waited this long, I can wait a bit more. Maybe and end-of-year gift for both of us?

Both links work for me.

VostoEmisio’s animated videos CCS proposal fully funded
VostoEmisio1’s CCS proposal2 to create an animated video explaining Full-Chain Membership Proofs 3 is now fully funded:

20 XMR raised in 31 contributions (100%)

To learn more about VostoEmisio’s work, consult the previous Monero Observer report4.

1. https://repo.getmonero.org/VOSTOEMISIO/ [↩](#fnref:1)

2. [https://ccs.getmonero.org/proposals/VOSTOEMISIO-FCMP-Animated-Explai … ⌘ Read more

Wouldn’t you rather have work and private seperated? Any thought behind this decission? I like tags, like Gmail does it. I still think mail needs a big rethink. It’s too prominent in life, to be this archaic.

PSA: Apple’s New USB-C Accessories Require macOS Sequoia, Don’t Work Properly With macOS 15.2 Beta
With the launch of new M4 Macs this week, Apple introduced USB-C versions of the Magic Mouse, Magic Trackpad, and Magic Keyboard to continue on with phasing out the Lightning port. Apple users who plan to buy these new accessories should be aware that there are some software limitations currently.

Image

The new … ⌘ Read more

So I’ve flattened my work and private email inboxes to single inbox folders and I don’t even know anymore what I was thinking before trying frantically to organise everything in sub folders. Labels and search filters are the way forward.

[47°09′52″S, 126°43′54″W] Storm recedes – back to normal work

Monero Research Lab meeting scheduled for 6 November 2024 1700 UTC
The next Monero Research Lab1 meeting is scheduled to take place on Wednesday, November 6th 2024 at 17:00 UTC on IRC-Libera/Matrix2 in the #monero-research-lab channels.

• Updates. What is everyone working on?
  
• Monero Research Computing Server hardware needs
  
• FCMP++ tx size and compute cost and MAX_INPUTS/MAX_OUTPUTS3
  
• FCMP++ Optimization Competition4
  
• Revi … ⌘ Read more

Boog900 posts second progress report for Cuprate CCS proposal
Boog9001 has posted the second progress report2 for their latest CCS proposal3 to continue full-time development work on the Cuprate 4 project:

I also found 1900+ IP addresses running “nodes” that have different behaviour to monerod and are almost certainly proxies to other nodes. [..] From the data I have it looks like 40% of the IPs running Monero nodes are not real nodes and ~75% o … ⌘ Read more

selsta posts October 2024 Monero dev report
selsta1 has posted a monthly CCS progress report2 for October 2024, which includes several Monero dev updates.

Milestone 3:
-Continued working on preparing the next release [..] v0.18.4.0 with multiple larger changes.
-Work on resolving HackerOne reports also continued [..]
-Investigated bugs and did some work on repository organization. [..]

Note that misc work is not explicitly mentioned in these updates. The full list of c … ⌘ Read more

I installed GrapheneOS for the first time on Wednesday last week on a used Pixel 7a, and I’m impressed. Installation was almost seamless, and I was able to do it from another Android phone. I’ve run into very few wrinkles, even using Google’s proprietary apps with GrapheneOS’s “sandboxed” version of Google Play Services. The main problems I’ve noticed: I can’t cast, and Google Timeline doesn’t seem to work (though I imagine the intersection between people keen to use GrapheneOS and keen to have Google log their location history is pretty small).

@prologic@twtxt.net 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.

I wonder if this kind of postprocessing would fit better between composing (via yarnd’s UI) and publishing. So, if a yarnd user types ¼, it could get changed to ¼ in the twtxt.txt file for everyone to see, not just people reading through yarnd. But when I type ¼, meaning first out of four, as a non-yarnd user, the meaning wouldn’t get corrupted. I can always type ¼ directly if that’s what I really intend.

(This twt might be easier to understand if you read it without any transformations :-P)

Anyway, again, I’m not a yarnd user, so do what you will, just know you might not be seeing exactly what I meant.

The last week I’ve been playing around with https://github.com/comfyanonymous/ComfyUI , dang good tool for testing ai models and such. I really like the node based workflow.
And makes it super easy to test any AI model.
Only thing I miss now - is one of those image to video setup’s, that’s what I’m working on fixing now. So that I can generate images, and then automatically make them into short videos as well.
Fun to play around with.

[47°09′35″S, 126°43′36″W] Working impossible due to thunderstorm

@sorenpeter@darch.dk I run Weechat headless on a VM and mostly connect via mobile or dwsktop. I use the android client or gliwing bear. Work blocks all comms on their always on MitM VPN so I cant in office anymore. So I just use mobile.

This works !

Cuprate Meeting scheduled for 5 November 2024 1800 UTC
The next Cuprate Meeting is scheduled1 to take place on Tuesday, November 5 2024 at 18:00 UTC on IRC-Libera/Matrix2 in the #cuprate channels.

Cuprate is an effort to create an alternative Monero node implementation.

Greetings
Updates: What is everyone working on?
Project: What is next for Cuprate?
branch protection
Any other business

The meeting’s moderator should be Boog9003. Consult … ⌘ Read more

mainnet-pat submits CCS proposal to complete XMR-BCH atomic swaps project
mainnet-pat1 has submitted a CCS proposal2 looking to finalize the effort to create the web platform for XMR-BCH atomic swap utilizing the adaptor signatures:

The work on server-side is mostly done and being tested, funded by generous donors from BCH Flipstarter campaign3. As we have initially underestimated (in the framework of BCH flipstarter) the effort to finish the task, … ⌘ Read more

m-a-x-c creates Monero churn timing tool
m-a-x-c1 has created Monero Churn Timer 2 - a Python script that generates randomized wait times for XMR transactions and can potentially help users increase their privacy by scheduling churns:

The way it works is as follows: after receiving Monero, you would use the Monero Churn Timer to generate a random wait time. You would then set a reminder to “churn” (i.e., send that transaction to yourself at a new address) after the specified … ⌘ Read more

[47°09′46″S, 126°43′29″W] Storm recedes – back to normal work

[47°09′23″S, 126°43′48″W] Working impossible due to blizzard

[ANN] Looking for intermediate/advanced Django/Python developer to fix and maintain moneroj.net!

Please reach out as soon as possible so we can bring the website back up, after looking at what broke and fixing it, plus optionally we can keep working together for the foreseeable future so we implement new features or refactor things around.

Links:

• https://moneroj.net/
  
• Contact
  

rottenwheel.com ⌘ 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?

How to ace (KCNA) Kubernetes and Cloud Native Associate exam
Community post originally published on Medium by Giorgi Keratishvili Introduction Most probably if you have been working in IT over last decate you would heared such words as containers, docker, cloud native, maybe even kubernetes, but wonder what does all those buzz words mean… ⌘ Read more

Apple Releases First Betas of iOS 18.2 and More With Genmoji, Image Playground and ChatGPT Integration
Apple today seeded the first betas of upcoming iOS 18.2, iPadOS 18.2, and macOS Sequoia 15.2 updates to developers for testing purposes. The betas have been released while Apple is still working on iOS 18.1, iPadOS 18.1, and ‌macOS Sequoia‌ 15.1, updates that are set to be released next week.

![](https://images.macrumors.com/article-new/2024/10/Generic- … ⌘ Read more

[ANN] Haveno-reto tails haveno-install script now working
Link: https://lemmy.cafe/post/9002281

u/oliver_twisted@monero.town ⌘ Read more

Monero Research Lab meeting scheduled for 30 October 2024 1700 UTC
The next Monero Research Lab1 meeting is scheduled to take place on Wednesday, October 30th 2024 at 17:00 UTC on IRC-Libera/Matrix2 in the #monero-research-lab channels.

• Updates. What is everyone working on?
  
• Research Pre-Seraphis Full-Chain Membership Proofs3. Reviews for Carrot.4
  
• CCS proposal: Audit monero-serai and monero-wallet5
  
• Monero Researc … ⌘ Read more

RNAWorld
⌘ Read more

Cuprate Meeting scheduled for 29 October 2024 1800 UTC
The next Cuprate Meeting is scheduled1 to take place on Tuesday, October 29 2024 at 18:00 UTC on IRC-Libera/Matrix2 in the #cuprate channels.

Cuprate is an effort to create an alternative Monero node implementation.

Greetings
Updates: What is everyone working on?
Project: What is next for Cuprate?
Any other business

The meeting’s moderator should be Boog9003. Consult the Cuprate code … ⌘ Read more

Testing the New iOS 18.1 Hearing Aid Functionality
With iOS 18.1, Apple is adding a new set of hearing health features to the AirPods Pro 2. The iOS 18.1 release candidate for developers and public beta testers includes the full hearing aid functionality, so we thought we’d give it a try to see just how it works.

_Subscribe to the MacRumors YouTube channel for more videos._

To use the new … ⌘ Read more

Data Protection Working Group deep dive at KubeCon + CloudNativeCon Salt Lake City
Community post by Dave Smith-Uchida, Technical Leader, Veeam (Linkedin, GitHub) Data on Kubernetes is growing with databases, object stores, and other stateful applications moving to the platform. The Data Protection Working Group (DPWG) focuses on data… ⌘ Read more

Tesla Plans to Release Apple Watch App That Will Work as a Digital Key
Tesla last week updated its iPhone app with new Control Center controls on iOS 18. In addition, the latest version of the app added hidden code references to an upcoming Apple Watch version of the app, according to MacRumors contributor Aaron Perris.

Image

The … ⌘ Read more

** Broughlike **
The Roguelike Celebration happened this weekend. Every year I think about participating, and every year I let it slip me by. In honor of it, though, this weekend I made a Broughlike…which I’ve creatively named “Eli’s Broughlike.”

It runs in the browser. It should work on most anything with a keyboard, or with a touchscreen — the about page ha … ⌘ Read more

ESP32-C61-DevKitC-1 with RISC-V Single Core Processor and Wi-Fi 6/Bluetooth LE 5
The ESP32-C61-DevKitC-1 is an upcoming entry-level development board that integrates Wi-Fi 6 in the 2.4 GHz band and Bluetooth LE 5 capabilities. The board is designed to support a variety of applications and offers multiple peripheral interfaces for developers to work with. The ESP32-C61 features a 32-bit RISC-V single-core processor running at 160 MHz. It […] ⌘ Read more

[47°09′37″S, 126°43′26″W] Storm recedes – back to normal work

ofrnxmr completes first milestone for BasicSwapDEX CCS proposal
ofrnxmr1 has completed2 the first milestone (M1-O/M1-F/M1-B) for their CCS proposal3 to empower and steward BasicSwapDex4 to production quality software:

”`
Core v0.13.4 > v0.14.1:

• Update coincurve fork and rebase onto v20
  
• Include coincurve as a basicswap dependency
  
• Fix remote (local) node handling
  
• Started integration of the novel BCH <>XMR swap protocol
  … ⌘ Read more”`

Apple Secretly Developed Long-Range EV Battery Tech with China’s BYD
Apple secretly collaborated with Chinese automaker BYD to develop long-range electric vehicle battery technology as part of its now-nixed Apple Car project, according to Bloomberg.

Image

Beginning around 2017, the partnership … ⌘ Read more

There’s this rumor that you can create a WhatsApp account with a burner phone, then link the phone to a browser on your desktop PC (web.whatsapp.com) and never have to use the phone again. This just doesn’t work. Every ~2 weeks, the session in the browser will time out and you have to re-link again. 🙄

Monero Research Lab meeting scheduled for 23 October 2024 1700 UTC
The next Monero Research Lab1 meeting is scheduled to take place on Wednesday, October 23rd 2024 at 17:00 UTC on IRC-Libera/Matrix2 in the #monero-research-lab channels.

• Updates. What is everyone working on?
  
• Research Pre-Seraphis Full-Chain Membership Proofs3. Reviews for Carrot.4
  
• CCS proposal: Audit monero-serai and monero-wallet5
  
• Monero Researc … ⌘ Read more

[47°09′33″S, 126°43′53″W] Storm recedes – back to normal work

Cuprate Meeting scheduled for 22 October 2024 1800 UTC
The next Cuprate Meeting is scheduled to take place on Tuesday, October 22 2024 at 18:00 UTC on IRC-Libera/Matrix1 in the #cuprate channels.

Cuprate is an effort to create an alternative Monero node implementation.

Greetings
Updates: What is everyone working on?
Project: What is next for Cuprate?
Any other business

The meeting’s moderator should be Boog9002. Consult the Cuprate code repository … ⌘ Read more

Justin Berman posts CCS progress report after 195 hours of dev work
Justin Berman1 has published the first progress report2 for his full-time 2024 (part 8) Monero/Seraphis dev work CCS proposal3:

I’m currently waiting on @kayabaNerve to complete work on the prove/verify API before I continue on to construct/verify/make consensus changes for fcmp++ txs (deliverables 4/5/6 of this CCS). To maintain forward progress on the fcmp++ integration, and since dang … ⌘ Read more

Apple Planning Smart Glasses and AirPods With Cameras for 2027
Apple is working on smart glasses and AirPods with built-in cameras for a potential release in 2027, according to Bloomberg’s Mark Gurman. The devices are said to be part of Apple’s efforts to expand its augmented reality product lineup beyond the Vision Pro headset with something that h … ⌘ Read more

v1docq47 posts August-September 2024 CCS progress report
v1docq471 has posted a second progress report (August-September 2024)1 for his latest CCS proposal2 to do Russian voice-over work and transcribe Monero content:

This is my August + September CCS progress report with voiceover and works on XMR.RU. [..] If you have suggestions or advice about my work, I will be glad to listen to them. Thanks for your support!

(A) Monero Russian Co ... ⌘ [Read more](https://monero.observer/v1docq47-posts-ccs-progress-report-august-september-2024/)

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

@2024-10-08T19:36:38-07:00@a.9srv.net Thanks for the followup. I agrees with most of it - especially:

Please nobody suggest sticking the content type in more metadata. 🙄

Yes, URL can be considered ugly, but they work and are understandable by both humans and machines. And its trivial for any client to hide the URLs used as reference in replies/treading.

Webfinger can be an add-on to help lookup people, and it can be made independent of the nick by just serving the same json regardless of the nick as people do with static sites and a as I implemented it on darch.dk (wf endpoint). Try RANDOMSTRING@darch.dk on http://darch.dk/wf-lookup.php (wf lookup) or RANDOMSTRING@garrido.io on https://webfinger.net

Monero Research Lab meeting scheduled for 16 October 2024 1700 UTC
The next Monero Research Lab1 meeting is scheduled to take place on Wednesday, October 16th 2024 at 17:00 UTC on IRC-Libera/Matrix2 in the #monero-research-lab channels.

• Updates. What is everyone working on?
  
• Stress testing monerod3
  
• Research Pre-Seraphis Full-Chain Membership Proofs4. Reviews for Carrot.5
  
• AOB.
  

This meeting’s chairperson should be … ⌘ Read more

[47°09′03″S, 126°43′17″W] Storm recedes – back to normal work

midipoet submits CCS proposal for ‘policy and regulatory framework’ research
midipoet1 has submitted a new CCS proposal2 looking to work part-time on policy and regulatory framework research within the Monero Policy Working Group 3 for 6 months:

I think its relevant to Monero currently and might allow the broader ecosystem to understand better how regulatory pressure is impacting privacy and data protection rights.

Total funding: 332 XMR  ... ⌘ [Read more](https://monero.observer/midipoet-submits-ccs-proposal-policy-regulatory-framework-research/)

vtnerd posts September 2024 Monero dev report
vtnerd1 has posted a second progress report2 for his full-time Q3 2024 Monero dev work CCS proposal3:

I rolled over the hours for a month last week. I was hoping to get another PR out before this merge request, but it looks like some of the work will have to wait. Reviewers can decide whether they trust additional (not yet posted) work has been done.

”`

• converting LWS REST server from an epee http se … ⌘ Read more”`

Cuprate Meeting scheduled for 15 October 2024 1800 UTC
The next Cuprate Meeting is scheduled1 to take place on Tuesday, October 15 2024 at 18:00 UTC on IRC-Libera/Matrix2 in the #cuprate channels.

Cuprate is an effort to create an alternative Monero node implementation.

Greetings
Updates: What is everyone working on?
Project: What is next for Cuprate?
Any other business

The meeting’s moderator should be Boog9003. Consult the Cuprate code … ⌘ Read more

@doesnm@doesnm.p.psf.lt Agree. salty.im should allow the user to post multiple brokers on their webfinger so the client can find a working path.

@doesnm@doesnm.p.psf.lt salty.im needs a lot more work 🤞it is however designed to be 1000% decentralized 👌

selsta posts September 2024 Monero dev report
selsta1 has posted a monthly CCS progress report2 for September 2024, which includes several Monero dev updates.

Milestone 2:
-Initial work started on the next release [..] v0.18.3.5 or v0.18.4.0.
-Continue to work HackerOne reports.
-Smaller bug fixes, including work on fixing CI again after multiple build issues. [..]

Note that misc work is not explicitly mentioned in these updates. The full list of changes can be found … ⌘ Read more

ki9 starts work on XMR price API with data from Bisq, Haveno-reto
Keith Irwin (ki91) has apparently started working on XMR Price F.Y.I. 2 - a new Monero price API with unbiased street price data from multiple sources, including Haveno-reto 3 and Bisq 4:

[X] Domain name service
[X] TLS certs
[X] Nginx proxy
[X] Basic 11ty site
[ ] Basic http API
[ ] Haveno-reto data
[ ] Bisq data
[ ] Coingecko data
[ ] Forex data
[ ] API
[ ]  ... ⌘ [Read more](https://monero.observer/ki9-starts-work-xmr-price-api-data-haveno-bisq/)

[47°09′18″S, 126°43′59″W] Storm recedes – back to normal work

[47°09′57″S, 126°43′56″W] Working impossible due to blizzard

SNeedlewoods submits CCS proposal for 1 month of part-time Monero dev work
SNeedlewoods1 has submitted their first CCS proposal2 to work part-time on Monero development for 1 month:

For this proposal the focus of work will be on the new wallet API [..] The work is already ongoing since May 2024 [..] This is a “pilot” proposal to see how things work out. [..] Hopefully I will become a long term contributor for general development.

Funding proposed: 2.15 XMR (10-15 hour ... ⌘ [Read more](https://monero.observer/sneedlewoods-submits-monero-dev-work-ccs-proposal/)

How to Fix Cellular Data Not Working on iOS 18 with Apps or iPhone
Some iPhone users have discovered that cellular data is not working on many apps after they have updated to iOS 18. For example, you might be driving and discover that you can no longer stream music from Music app, or can’t listen to podcasts from Spotify, or load reels on Instagram, or watch TikTok, but … Read More ⌘ Read more

@aelaraji@aelaraji.com Yep seems alright! Really fast too. I’m still using my main Firefox in general cos.. well it’s set up so much and it’s hardened, profile running in RAM, all that crazy stuff that got it working the way I want 😂

But keeping a good eye on Zen Browser’s progress.

HardenedSteel, spirobel CCS proposals ready for funding
Two CCS proposals have been moved to the funding stage and are now looking for community support:

• HardenedSteel’s!502 1: Part-time Work on getmonero.org (2 Month) 2
  
• spirobel’s!501 3: Robust and modular wallet-rpc library 4
  

To support the above proposals you can donate to the XMR addresses listed on the Funding Required 5 page.

_This is an ongoing story and the report will … ⌘ Read more

Cuprate Meeting scheduled for 8 October 2024 1800 UTC
The next Cuprate Meeting is scheduled1 to take place on Tuesday, October 8 2024 at 18:00 UTC on IRC-Libera/Matrix2 in the #cuprate channels.

Cuprate is an effort to create an alternative Monero node implementation.

Greetings
Updates: What is everyone working on?
Project: What is next for Cuprate?
Any other business

The meeting’s moderator should be Boog9003. Consult the Cuprate code rep … ⌘ Read more

Monero Research Lab meeting scheduled for 9 October 2024 1700 UTC
The next Monero Research Lab1 meeting is scheduled to take place on Wednesday, October 9th 2024 at 17:00 UTC on IRC-Libera/Matrix2 in the #monero-research-lab channels.

• Updates. What is everyone working on?
  
• Stress testing monerod3
  
• Research Pre-Seraphis Full-Chain Membership Proofs4. Reviews for Carrot.5
  
• 10 block lock discussion6
  

This meet … ⌘ Read more

Oh boy, I’m looking for trapezoidal (like ACME thread) screws and nuts in left hand form. The rods are already expensive, but nuts feel like a total ripoff. A hex nut for Tr20x2 being 30mm long and 30mm in “diameter” costs me 22 bucks! O_o Just a single one, made of regular steel. A meter of rod is 21€. The more common Tr20x4 hex nut is just 7€ and the rod 17€, but 4mm pitch is a bit much for a leadscrew for semi-precision work I reckon.

Well, maybe I just use metric threads. I will sleep on this.

Exploring Docker for DevOps: What It Is and How It Works
We explore the use of Docker for DevOps and explain how the combination can help developers create more efficient and powerful workflows. ⌘ Read more

Ok, i know how to command working (not sure), but seems it only grab from cache. Maybe make fetch from twtxt.net if hash not found?

@doesnm@doesnm.p.psf.lt I’ve just given it a try on android/termux and got it to work, I can’t promise it won’t break something else (because i definitely don’t know what I’m doing) but here’s what I broke 😅:

~/src/jenny $ git diff
diff --git a/jenny b/jenny
index ada8da2..8ae9a06 100755
--- a/jenny
+++ b/jenny
@@ -1194,7 +1194,7 @@ if __name__ == '__main__':
     if args.edit:
	edit_twt_file(app)
     elif args.fetch:
-        with DirectoryLock(f'/tmp/jenny-{getuser()}.run'):
+        with DirectoryLock(expanduser('~/tmp/jenny-{getuser()}.run')):
             retrieve_all(app)
     elif args.last_seen:
	 print('Feeds last seen at (times are local time), oldest first:')

and of course make sure you mkdir ~/tmp

👋 Thanks for joining us on our Sept monthly Yarn.social meetup today y’all 🙇‍♂️ We had @david@collantes.us @sorenpeter@darch.dk @doesnm@doesnm.p.psf.lt @falsifian@www.falsifian.org and @xuu@txt.sour.is 💪 Nice turn out! (not all at once of course, as we normally run this over 4 hours as we span many time zones!)

Things we talked about:

• Decentralised vs. Distributed
  
• Use of SHA256 for Twt Hash(es)
  
• We solved Edits! 🥳
  
• UUID(s) probably won’t work! (susceptible to sppofing)
  
• Helped @sorenpeter@darch.dk write some PHP to process/parse User-Agent and service his feed via a custom PHP script 😅
  
• @falsifian@www.falsifian.org introduced himself 👌
  
• Talked about Merkle Trees 🌳
  

Did I miss anything? 🤔

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.

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.

Hurricane Helene is passing by. Close enough to give us a day off tomorrow, but not that close to cause major harm. Well, we think. Hurricanes often have a mind of their own, and decide changes on their path. Either way, I shall be back at work on Friday 😩. LOL.

Good writeup, @anth@a.9srv.net! I agree to most of your points.

3.2 Timestamps: I feel no need to mandate UTC. Timezones are fine with me. But I could also live with this new restriction. I fail to see, though, how this change would make things any easier compared to the original format.

3.4 Multi-Line Twts: What exactly do you think are bad things with multi-lines?

4.1 Hash Generation: I do like the idea with with a new uuid metadata field! Any thoughts on two feeds selecting the same UUID for whatever reason? Well, the same could happen today with url.

5.1 Reply to last & 5.2 More work to backtrack: I do not understand anything you’re saying. Can you rephrase that?

8.1 Metadata should be collected up front: I generally agree, but if the uuid metadata field were a feed URL and no real UUID, there should be probably an exception to change the feed URL mid-file after relocation.

yes that works

(#2024-09-24T12:34:31Z) WebMentions does would work if we agreed to implement it correctly. I never figured out how yarnd’s WebMentions work, so I decide to make my own, which I’m the only one using…

I had a look at WebSub, witch looks way more complex than WebMentions, and seem to need a lot more overhead. We don’t need near realtime. We just need a way to notify someone that someone they don’t know about mentioned or replied to their post.

Kubestronaut in Orbit: Camila Soares Câmara
Get to know Camila This week’s Kubestronaut in Orbit, Camila Soares Câmara, is a Senior Cloud Engineer at Wellhub in Brazil with experience in Cloud and DevOps, working with technologies such as Kubernetes, CI/CD, AWS, and Infrastructure as… ⌘ Read more

@aelaraji@aelaraji.com I think all replies are missing the fact that your auto-completion isn’t working. LOL. Or did I misunderstood?

Finally pubnix is alive! That’s im missing? Im only reading twtxt.net timeline because twtxt-v2.sh works slowly for displaying timeline…

[47°09′03″S, 126°43′42″W] Storm recedes – back to normal work

10 Reasons to Wait for Next Year’s iPhone 17
Apple’s iPhone development roadmap runs several years into the future and the company is continually working with suppliers on several successive iPhone models simultaneously, which is why we sometimes get rumored feature leaks so far ahead of launch. The iPhone 17 series is no different – already we have some idea of what to expect from Apple’s 2025 smartphone lineup.

![](https://images.macrumors.com/article-new/2024/08/iPhone-17-Slim-Feature-Single-Camer … ⌘ Read more

@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.

I ended up installing Headscale on my little VPS. Just in case the collide, I turned off WireGuard. Turning that one off (which ran on a container) also frees some memory. Headscale is running quite well! Indeed, I have struggled getting any web management console to work, but it really isn’t needed. Everything needed to commandeer the server is available through the CLI.

Seems to be working OK 🤔

Apple’s First 5G Chip for iPhones Reportedly Won’t Support mmWave
Apple is rumored to have been working on its own 5G modem for iPhones since 2018, but the first version of the chip might lack mmWave support.

Image

Taiwanese industry publication DigiTimes today reported that Apple’s in-house 5G modem has yet to incorporate mmWave technolo … ⌘ Read more

@prologic@twtxt.net Wikipedia claims sha1 is vulnerable to a “chosen-prefix attack”, which I gather means I can write any two twts I like, and then cause them to have the exact same sha1 hash by appending something. I guess a twt ending in random junk might look suspcious, but perhaps the junk could be worked into an image URL like

Image

git only uses sha1 because they’re stuck with it: migrating is very hard. There was an effort to move git to sha256 but I don’t know its status. I think there is progress being made with Game Of Trees, a git clone that uses the same on-disk format.

I can’t imagine any benefit to using sha1, except that maybe some very old software might support sha1 but not sha256.

I have configured my twtxt.txt as simple as possible. I have setup a publish_command on jenny. Hopefully all works fine, and I am good to go. Next will be setting the announce_me to true. Here we go!

I’m not advocating in either direction, btw. I haven’t made up my mind yet. 😅 Just braindumping here.

The (replyto:…) proposal is definitely more in the spirit of twtxt, I’d say. It’s much simpler, anyone can use it even with the simplest tools, no need for any client code. That is certainly a great property, if you ask me, and it’s things like that that brought me to twtxt in the first place.

I’d also say that in our tiny little community, message integrity simply doesn’t matter. Signed feeds don’t matter. I signed my feed for a while using GPG, someone else did the same, but in the end, nobody cares. The community is so tiny, there’s enough “implicit trust” or whatever you want to call it.

If twtxt/Yarn was to grow bigger, then this would become a concern again. But even Mastodon allows editing, so how much of a problem can it really be? 😅

I do have to “admit”, though, that hashes feel better. It feels good to know that we can clearly identify a certain twt. It feels more correct and stable.

Hm.

I suspect that the (replyto:…) proposal would work just as well in practice.

@movq@www.uninformativ.de alright, fair, and interesting. I was expecting them to be all the same (format wise), but it doesn’t matter, for sure, as it works just fine. Thanks!

Software as a public good
Open source software underpins all sectors of the economy, public services and even international organizations like the United Nations. How can all its beneficiaries work together to make the open source ecosystem more sustainable?

The post Software as a public good appeared first on The GitHub Blog. ⌘ Read more

@prologic@twtxt.net yes, that would work, except there is no debug command on my local yarnc. Are you talking about a potential future implementation here?