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:
Work summaryThis 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/)🧮 USERS:1 FEEDS:2 TWTS:1118 ARCHIVED:79884 CACHE:2512 FOLLOWERS:17 FOLLOWING:14
(Updated) Sipeed Showcases Tang Mega 138K Dock with GOWIN Series FPGA
The Sipeed Tang Mega 138K Dock is an advanced and compact FPGA development platform designed to meet both high-performance requirements and cost-effective solutions. Featuring the GOWIN GW5AST RISC-V FPGA, this platform includes a development board with key features such as PCIe x4, a GbE port, and multiple I/Os. The Tang Mega 138K features the GW5AST-LV138PG484A […] ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1117 ARCHIVED:79878 CACHE:2526 FOLLOWERS:17 FOLLOWING:14
[WTS] [US] [$95] ThinkPad T560
ThinkPad T560 - i7-6600U @ 2.60GHz - 8GB DDR3 RAM - 256GB SSD. Pop_OS! is installed, but I can put whatever distro you’d like. I can also load the Monero Blockchain on it if you wish. Comes with charger.
Link: https://xmrbazaar.com/listing/gHpx/
xmrRedux (XMRBazaar) ⌘ Read more
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
The 10 Best Apple Deals Under $100 for Prime Day
As Prime Day continues today, we’re highlighting all of the best Apple deals you can get for under $100 on Amazon. This includes Apple Pencil, AirTags, iPhone cases, USB-C chargers, and more.
MacBook Pro With M4 Chip May Support Up to Two External Displays
Apple’s upcoming entry-level M4 14-inch MacBook Pro may be capable of supporting up to two external displays, up from one display supported in the current M3 model, if recent leaks are anything to go by.
Apple’s existing M3 14-inch MacBook Pro comes with two Thunderbolt 3 USB-C ports, not three Thunderbolt 4 … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1116 ARCHIVED:79864 CACHE:2542 FOLLOWERS:17 FOLLOWING:14
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/)Community Workgroup Meeting scheduled for 12 October 2024 1500 UTC
The next Monero Community Workgroup Meeting is scheduled1 to take place on Saturday, 12th of October 2024 at 15:00 UTC, in the #monero-community 2’3 channels.
Discussions should be focused on community highlights, CCS updates and workgroup reports. plowsof4 will moderate the meeting.
Logs and summary for the previous meeting are available on Monero Observer5.
_This is an ongoin … ⌘ Read more
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:
Work overviewI 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”`
tobtoht releases Feather Wallet v2.7.0
tobtoht1 has released Feather Wallet2 version 2.7.03’4 with various fixes, updates, and improvements:
history: always show the integrated address in the destinations table if an outgoing transaction has a payment id - this issue could lead to a potential loss of funds if a repeat payment was made to a service and the address was copied from the dialog without verifying it; a report of this issue was rewarded with … ⌘ 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.
Agenda overviewCuprate 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
BrandyJSon releases Feather Atomic v1.2
BrandyJSon1 has released Feather Atomic 2 version 1.23 with a temporary fix for the dead rendezvous points issue4:
[..] lets a user force a swaptool to query rendezvous points over clearnet. Does not completely solve the issue as it stems from comit xmr<->btc using an outdated libp2p version.
The full changelog, sources and SHA256sums can be found on Github3.
Highlights from Git 2.47
Git 2.47 is here, with features like incremental multi-pack indexes and more. Check out our coverage of some of the highlights here.
The post Highlights from Git 2.47 appeared first on The GitHub Blog. ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1115 ARCHIVED:79710 CACHE:2585 FOLLOWERS:17 FOLLOWING:14
rehrar releases Stack Wallet v2.1.7, Stack Duo v1.2.3
rehrar1 has released Stack Wallet2 version 2.1.73 and Stack Duo version 1.2.34 with Monero coin control, other changes and updates.
Stack Wallet:
* Added Monero/WOW coin control
* Added Cardano
* Updated FROST with latest and greatest
Stack Duo:
* Monero coin control
* Frost tweaks and changes
* Tweaks to how Bitcoin connects to ElectrumX [..]
The release notes, binar … ⌘ Read more
Monero Tech meeting scheduled for 14 October 2024 1800 UTC
The next Monero Tech meeting is scheduled to take place on Monday, October 14 2024 at 18:00 UTC, in the #no-wallet-left-behind 1 IRC-Libera/Matrix channels:
Based on the opinions given here2 I decided to go back to the No Wallet Left Behind Matrix room and IRC channel for the next i.e. coming Monday’s meeting, and to not contiune to hold meetings like the last one in the -dev Matrix room and IRC channel.
This meeting’s chai … ⌘ Read more
Ultra Slim Fanless Box PC Builds on Intel IOTG Alder Lake-N Processors
The MS-1P17 Ultra Slim Fanless Box PC by MSI is powered by Intel Alder Lake-N processors, providing a low-power solution in three variants for different performance needs. Its fanless 25mm design is aimed at space-constrained installations, while two 2.5 GbE LAN ports deliver fast, reliable networking for demanding environments. Available processor options include the N97, […] ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1114 ARCHIVED:79694 CACHE:2581 FOLLOWERS:17 FOLLOWING:14
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
Monero Dev Activity Report - Week 40 2024: 28 PRs, 11 Issues
This weekly report aims to provide a big picture view of Monero development activity, increase community support for existing devs and, hopefully, encourage new contributions.
Opened (13)
monero-project/monero:
Gupaxx v1.5.0 released with monerod integration
Cyrix1261 has released Gupaxx 2 version 1.5.03 with monerod integration4, multiple other UI changes, bug fixes and updates:
UI:
-new big feature: integration of Monerod
-new button on p2pool simple tab to use the local node (default)
Internals:
-new big feature: integration of Monerod process
-put p2pool to synchronizing status if a node doesn't respond
Fixes:
-xmrig-proxy tab sim ... ⌘ [Read more](https://monero.observer/cyrix126-releases-gupaxx-v1.5.0-monerod-integration/)NanoPi Zero2 with Gigabit Ethernet and Optional Wi-Fi Connectivity via M.2 Slot
The NanoPi Zero2 is a compact single-board computer designed around the Rockchip RK3528A processor. This device is available with an optional metal case and provides a Gigabit Ethernet port, as well as optional Wi-Fi connectivity via an M.2 slot. Powered by a quad-core ARM Cortex-A53 CPU running up to 2.0 GHz, the NanoPi Zero2 is […] ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1113 ARCHIVED:79690 CACHE:2578 FOLLOWERS:17 FOLLOWING:14
RINO platform to close down on October 31 2024: ‘we have to cut our losses’
The RINO1 team has announced2 plans to shut down their enterprise-grade Monero multisig browser wallet3 project on October 31st 2024, due to failed attempts to monetize the product, after 2+ years of operation4:
[..] our attempts to monetize the product never bore fruit to a point where the product could sustain itself, and at some point we have to cut our losses. As a consequence, … ⌘ 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/)Monero Observer Artistic Saturday Top 5 - Week 40, 2024
Previous Artistic Saturday weekly reports can be found in the [art] 1 section.
![‘Privacy tools’ … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1112 ARCHIVED:79684 CACHE:2598 FOLLOWERS:17 FOLLOWING:14
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/)rottenwheel publishes ‘Revuo Monero’ Issue href=”https://txt.sour.is/search?q=%23212”>#212**
rottenwheel1 has published Issue #2122’3 of the weekly Revuo Monero audience-funded newsletter, which covers September 26-3 October 2024 news:
Recent News
Upcoming Events
CCS Proposals
Price & Blockchain Stats
Volunteer Opportunities
Support
To support Revuo Monero, you can contribute XMR to the address listed in the footer of each issue and on the Support 4 page.
Trick or Treat? Apple’s First Earnings Call Since iPhone 16 Launch Scheduled for Halloween
Apple today announced that its next quarterly earnings conference call will be held on Thursday, October 31 at 2 p.m. Pacific Time/5 p.m. Eastern Time.
On the call, Apple’s CEO Tim Cook and CFO Luca Maestri will discuss the company’s earnings results for the fourth quarter of the 2024 fiscal year. It will likely be Maestri’s final earnings call at … ⌘ Read more
How students teamed up to decode 2,000-year-old texts using AI
Students used GitHub Copilot to decode ancient texts buried in Mount Vesuvius, achieving a groundbreaking historical breakthrough. This is their journey, the technology behind it, and the power of collaboration.
The post How students teamed up to decode 2,000-year-old texts using AI ap … ⌘ Read more
↳
In-reply-to
»
@prologic I wanted to wait for things to settle down. It’s still unclear to me in which direction we’re going – and if that new/different stuff is even possible to implement in jenny. That said, I’ve been really busy with private stuff these last few days, I’ve lost track of most of what you’re discussing. 🥴
⤋ Read More
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:
- If yarn has one use that. (Maybe do collision check?)
- Make hash of twt raw no truncation.
- Check local cache for shortest without collision
- in SQL:
select len(subject) where head_full_hash like subject || '%'
- in SQL:
Threading:
- Get full hash of head twt
- Search for twts
- in SQL:
head_full_hash like subject || '%' and created_on > head_timestamp
- in SQL:
The assumption being replies will be for the most recent head. If replying to an older one it will use a longer hash.
↳
In-reply-to
»
@prologic I wanted to wait for things to settle down. It’s still unclear to me in which direction we’re going – and if that new/different stuff is even possible to implement in jenny. That said, I’ve been really busy with private stuff these last few days, I’ve lost track of most of what you’re discussing. 🥴
⤋ Read More
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:
- If yarn has one use that. (Maybe do collision check?)
- Make hash of twt raw no truncation.
- Check local cache for shortest without collision
- in SQL:
select len(subject) where head_full_hash like subject || '%'
- in SQL:
Threading:
- Get full hash of head twt
- Search for twts
- in SQL:
head_full_hash like subject || '%' and created_on > head_timestamp
- in SQL:
The assumption being replies will be for the most recent head. If replying to an older one it will use a longer hash.
🧮 USERS:1 FEEDS:2 TWTS:1111 ARCHIVED:79666 CACHE:2610 FOLLOWERS:17 FOLLOWING:14
pluja launches experimental ‘AI-driven’ weekly Monero podcast
pluja1 has announced2 the launch of XMR.FAN 3, an AI-driven experimental weekly podcast that aims to deliver the latest insights and news from the world of Monero and privacy:
I’ve been experimenting with Google’s NotebookLM, voice generation (elevenlabs/piper), and other AI tools (SD, flux…). I discovered that these are really useful to produce very decent weekly news overviews, so I made this websi … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1110 ARCHIVED:79632 CACHE:2622 FOLLOWERS:17 FOLLOWING:14
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.
Agenda overviewCuprate 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
Apple’s Next New iPhone to Debut in the Spring: What to Expect
Apple’s budget-friendly iPhone SE is set for a major overhaul with a fourth generation model expected to launch in spring 2025. The upcoming model will mark a significant departure from its predecessors, adopting several features from higher-end iPhones while maintaining its position as the most affordable new model in Apple’s lineup.
According to [ … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1109 ARCHIVED:79618 CACHE:2654 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1108 ARCHIVED:79604 CACHE:2650 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1107 ARCHIVED:79577 CACHE:2662 FOLLOWERS:17 FOLLOWING:14
Radxa E20C is a Compact Low-Cost Router with Dual Gigabit Ethernet and Up to 4GB RAM
The E20C Mini Network Titan from Radxa is powered by the Rockchip RK3528A System-on-Chip and features dual Gigabit Ethernet ports. Its ultra-compact form factor and aluminum case are designed to provide a space-efficient solution for various network applications. The system integrates a quad-core ARM Cortex-A53 CPU, clocked at 2.0GHz, and an Arm Mali G450 GPU, […] ⌘ Read more
NanoPi M6: High-Performance SBC with Gigabit Ethernet and M.2 SSD Expansion
The NanoPi M6 is a compact and open-source single-board computer (SBC) designed for high-performance applications, powered by the RK3588S System-on-Chip. Key features include an M.2 M-Key PCIe slot for SSD storage and an optional metal case with an integrated 3.5-inch LCD. The board is built around the Rockchip RK3588S SoC, which combines quad-core ARM Cortex-A76 […] ⌘ Read more
Pimoroni Pico Plus 2 W Enhanced RP2350 Microcontroller with Wireless Connectivity
The Pimoroni Pico Plus 2 W is an upgraded version of the RP2350 microcontroller, offering more memory and wireless connectivity while keeping the compact form factor of the original Raspberry Pi Pico. It is designed for developers seeking enhanced functionality while maintaining compatibility with the Raspberry Pi ecosystem. It features 16MB of QSPI flash and […] ⌘ Read more
More thoughts about changes to twtxt (as if we haven’t had enough thoughts):
- 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.
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.
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.)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.
🧮 USERS:1 FEEDS:2 TWTS:1106 ARCHIVED:79449 CACHE:2645 FOLLOWERS:17 FOLLOWING:14
↳
In-reply-to
»
I'd like to see them fine me 2% of zero dollars
⤋ Read More
83(4) GDPR sets forth fines of up to 10 million euros, or, in the case of an undertaking, up to 2% of its entire global turnover of the preceding fiscal year, whichever is higher.
Though I suppose it has to be the greater of the two. But I don’t even have one euro to start with.
↳
In-reply-to
»
I'd like to see them fine me 2% of zero dollars
⤋ Read More
83(4) GDPR sets forth fines of up to 10 million euros, or, in the case of an undertaking, up to 2% of its entire global turnover of the preceding fiscal year, whichever is higher.
Though I suppose it has to be the greater of the two. But I don’t even have one euro to start with.
🧮 USERS:1 FEEDS:2 TWTS:1105 ARCHIVED:79381 CACHE:2634 FOLLOWERS:17 FOLLOWING:14
** Guitar driven development **
I’ve found myself in possession of a guitar. Actually, the guitar that I had in middle school has come back to me after a decade’s long jaunt with someone else. I don’t really play guitar, but, I figured I should restring it and tune it.
I’m really very bad at tuning, so, rather than get good at that, or use any of the existing tools within reach of the internet to help me with that I made a thing. Tuner is a little web app that does 2 things: using a device’s … ⌘ Read more
↳
In-reply-to
»
I'd like to see them fine me 2% of zero dollars
⤋ Read More
@xuu@txt.sour.is was that 2% picked out randomly? I like it! LOL.
Apple Releases New AirPods Pro 2 Firmware
Apple today released a new firmware update for the AirPods Pro 2, with the software available for both the USB-C and Lightning models. The AirPods Pro 2 firmware has a build number of 7A305, up from the 7A302 firmware released earlier in September.
 – In fact I should just drop the feature entirely.
The use of WebSub OTOH is far more useful and is used by every single yarnd pod everywhere (no that there’s that many around these days) to subscribe to feed updates in ~near real-time without having the poll constantly.
Some more arguments for a local-based treading model over a content-based one:
The format:
(#<DATE URL>)or(@<DATE URL>)both makes sense: # as prefix is for a hashtag like we allredy got with the(#twthash)and @ as prefix denotes that this is mention of a specific post in a feed, and not just the feed in general. Using either can make implementation easier, since most clients already got this kind of filtering.Having something like
(#<DATE URL>)will also make mentions via webmetions for twtxt easier to implement, since there is no need for looking up the#twthash. This will also make it possible to make 3th part twt-mentions services.Supporting twt/webmentions will also increase discoverability as a way to know about both replies and feed mentions from feeds that you don’t follow.
Apple Releases Second iOS 18.1, iPadOS 18.1, and macOS Sequoia Public Betas With Apple Intelligence
Apple today released the second public betas of iOS 18.1, iPadOS 18.1, and macOS Sequoia 15.1, allowing non-developers to test the software ahead of its October launch. The second beta comes a day after Apple provided the software to developers.
Public beta t … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1102 ARCHIVED:79309 CACHE:2611 FOLLOWERS:17 FOLLOWING:14
Apple Seeds Fifth Developer Betas of iOS 18.1 and iPadOS 18.1 With Apple Intelligence
Apple today provided developers with the fourth betas of iOS 18.1 and iPadOS 18.1 to continue testing Apple Intelligence features. The fifth betas come two weeks after Apple seeded the fourth iOS 18.1 and iPadOS 18.1 betas.
The updates can be downloaded from the S … ⌘ Read more
BlueSCSI Wi-Fi Desk Accessory 1.2 Released ⌘ Read more
Wallops 2.1 Released ⌘ Read more
MS-CF16 Fanless Low-Power Pico-ITX SBC with Alder Lake-N and Amston Lake Processors
The MS-CF16 is a compact Pico-ITX single-board computer designed for fanless, low-power, high-performance applications in harsh environments. Powered by Intel Alder Lake-N or Amston Lake Series SoCs, the board features a 2.5GbE LAN port, a GbE LAN port, and SATA 3.0 for storage. Unlike the previously covered MS-CF17, this model offers configurable Intel processors, each […] ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1101 ARCHIVED:79243 CACHE:2591 FOLLOWERS:17 FOLLOWING:14
[47°09′40″S, 126°43′18″W] Raw reading: 0x66F06931, offset +/-2
Apple Intelligence Features Expected to Roll Out in This Order Between iOS 18.1 and iOS 18.4 [Updated]
iOS 18 was released to the public earlier this month, but the first Apple Intelligence features will not be available until iOS 18.1 is released in October.
Apple Intelligence features will continue to roll out in iOS 18.2 and beyond … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1100 ARCHIVED:79197 CACHE:2589 FOLLOWERS:17 FOLLOWING:14
Protectli Vault V1410: Fanless 4-Port 2.5GbE Network Appliance with Intel N5105
The Protectli Vault V1410 is a fanless network appliance designed for applications that demand robust performance and reliable connectivity. Key features include four 2.5GbE Ethernet ports and multiple expansion slots, making it a versatile solution for a wide range of networking environments. The device comes equipped with the Intel N5105 processor, a quad-core Celeron chip […] ⌘ Read more
Apple Begins Selling Refurbished AirPods Pro 2 With USB-C Case in U.S.
Apple today began selling refurbished second-generation AirPods Pro with a USB-C charging case on its online store in the U.S. for $209, compared to $249 brand new.
Apple updated the AirPods Pro with a USB-C cha … ⌘ Read more
↳
In-reply-to
»
@movq @falsifian @prologic Maybe I don't know what I'm talking about and You've probably already read this: Everything you need to know about the “Right to be forgotten” coming straight out of the EU's GDPR Website itself. It outlines the specific circumstances under which the right to be forgotten applies as well as reasons that trump the one's right to erasure ...etc.
⤋ Read More
@aelaraji@aelaraji.com This is one of the reasons why yarnd has a couple of settings with some sensible/sane defaults:
I could already imagine a couple of extreme cases where, somewhere, in this peaceful world one’s exercise of freedom of speech could get them in Real trouble (if not danger) if found out, it wouldn’t necessarily have to involve something to do with Law or legal authorities. So, If someone asks, and maybe fearing fearing for… let’s just say ‘Their well being’, would it heart if a pod just purged their content if it’s serving it publicly (maybe relay the info to other pods) and call it a day? It doesn’t have to be about some law/convention somewhere … 🤷 I know! Too extreme, but I’ve seen news of people who’d gone to jail or got their lives ruined for as little as a silly joke. And it doesn’t even have to be about any of this.
There are two settings:
$ ./yarnd --help 2>&1 | grep max-cache
--max-cache-fetchers int set maximum numnber of fetchers to use for feed cache updates (default 10)
-I, --max-cache-items int maximum cache items (per feed source) of cached twts in memory (default 150)
-C, --max-cache-ttl duration maximum cache ttl (time-to-live) of cached twts in memory (default 336h0m0s)
So yarnd pods by default are designed to only keep Twts around publicly visible on either the anonymous Frontpage or Discover View or your Timeline or the feed’s Timeline for up to 2 weeks with a maximum of 150 items, whichever get exceeded first. Any Twts over this are considered “old” and drop off the active cache.
It’s a feature that my old man @off_grid_living@twtxt.net was very strongly in support of, as was I back in the day of yarnd’s design (nothing particularly to do with Twtxt per se) that I’ve to this day stuck by – Even though there are some 😉 that have different views on this 🤣
Upcoming I-Pi SMARC Embedded Prototype Kit Adopts Intel Amston Lake CPU
The I-Pi SMARC Amston Lake is a prototyping kit built on Intel’s Amston Lake architecture, designed to accelerate embedded system development. Key features include dual 2.5GbE LAN ports with Time-Sensitive Networking support and CAN interfaces for industrial applications. This kit includes the I-Pi SMARC Plus carrier and the LEC-ASL SMARC module, which features an Intel […] ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1099 ARCHIVED:79147 CACHE:2577 FOLLOWERS:17 FOLLOWING:14
Halfbrick+ Lets You Play Popular iOS Games Like Fruit Ninja, Jetpack Joyride and Mega Jump for $2.99/Month
Halfbrick Studios is a game company best known for super popular iOS titles like Fruit Ninja and Jetpack Joyride, which have historically been freemium titles. Starting last year, Halfbrick decided to go with a different monetization model, offering all of its games for a low monthly fee.
[Halfb … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1098 ARCHIVED:79066 CACHE:2530 FOLLOWERS:17 FOLLOWING:14
the stem matching is the same as how GIT does its branch hashes. i think you can stem it down to 2 or 3 sha bytes.
if a client sees someone in a yarn using a byte longer hash it can lengthen to match since it can assume that maybe the other client has a collision that it doesnt know about.
the stem matching is the same as how GIT does its branch hashes. i think you can stem it down to 2 or 3 sha bytes.
if a client sees someone in a yarn using a byte longer hash it can lengthen to match since it can assume that maybe the other client has a collision that it doesnt know about.
🧮 USERS:1 FEEDS:2 TWTS:1097 ARCHIVED:79000 CACHE:2495 FOLLOWERS:17 FOLLOWING:14
↳
In-reply-to
»
Taking the last n characters of a base32 encoded hash instead of the first n can be problematic for several reasons:
⤋ Read More
There’s a simple reason all the current hashes end in a or q: the hash is 256 bits, the base32 encoding chops that into groups of 5 bits, and 256 isn’t divisible by 5. The last character of the base32 encoding just has that left-over single bit (256 mod 5 = 1).
So I agree with #3 below, but do you have a source for #1, #2 or #4? I would expect any lack of variability in any part of a hash function’s output would make it more vulnerable to attacks, so designers of hash functions would want to make the whole output vary as much as possible.
Other than the divisible-by-5 thing, my current intuition is it doesn’t matter what part you take.
Hash Structure: Hashes are typically designed so that their outputs have specific statistical properties. The first few characters often have more entropy or variability, meaning they are less likely to have patterns. The last characters may not maintain this randomness, especially if the encoding method has a tendency to produce less varied endings.
Collision Resistance: When using hashes, the goal is to minimize the risk of collisions (different inputs producing the same output). By using the first few characters, you leverage the full distribution of the hash. The last characters may not distribute in the same way, potentially increasing the likelihood of collisions.
Encoding Characteristics: Base32 encoding has a specific structure and padding that might influence the last characters more than the first. If the data being hashed is similar, the last characters may be more similar across different hashes.
Use Cases: In many applications (like generating unique identifiers), the beginning of the hash is often the most informative and varied. Relying on the end might reduce the uniqueness of generated identifiers, especially if a prefix has a specific context or meaning.
Taking the last n characters of a base32 encoded hash instead of the first n can be problematic for several reasons:
Hash Structure: Hashes are typically designed so that their outputs have specific statistical properties. The first few characters often have more entropy or variability, meaning they are less likely to have patterns. The last characters may not maintain this randomness, especially if the encoding method has a tendency to produce less varied endings.
Collision Resistance: When using hashes, the goal is to minimize the risk of collisions (different inputs producing the same output). By using the first few characters, you leverage the full distribution of the hash. The last characters may not distribute in the same way, potentially increasing the likelihood of collisions.
Encoding Characteristics: Base32 encoding has a specific structure and padding that might influence the last characters more than the first. If the data being hashed is similar, the last characters may be more similar across different hashes.
Use Cases: In many applications (like generating unique identifiers), the beginning of the hash is often the most informative and varied. Relying on the end might reduce the uniqueness of generated identifiers, especially if a prefix has a specific context or meaning.
In summary, using the first n characters generally preserves the intended randomness and collision resistance of the hash, making it a safer choice in most cases.
↳
In-reply-to
»
Could someone knowledgable reply with the steps a grandpa will take to calculate the hash of a twtxt from the CLI, using out-of-the-box tools? I swear I read about it somewhere, but can't find it.
⤋ Read More
@prologic@twtxt.net I saw those, yes. I tried using yarnc, and it would work for a simple twtxt. Now, for a more convoluted one it truly becomes a nightmare using that tool for the job. I know there are talks about changing this hash, so this might be a moot point right now, but it would be nice to have a tool that:
- Would calculate the hash of a twtxt in a file.
- Would calculate all hashes on a
twtxt.txt(local and remote).
Again, something lovely to have after any looming changes occur.
🧮 USERS:1 FEEDS:2 TWTS:1096 ARCHIVED:78954 CACHE:2471 FOLLOWERS:17 FOLLOWING:14
↳
In-reply-to
»
(replyto http://darch.dk/twtxt.txt 2024-09-15T12:50:17Z) Hmm, but yarnd also isn't showing these twts as being part of a thread. @prologic you said yarnd respects customs subjects. Shouldn't these twts count as having a custom subject, and get threaded together?
⤋ Read More
@falsifian@www.falsifian.org yes, that happened around 2 years ago, on commit 5923078ea5.
↳
In-reply-to
»
@quark At the moment, the twt in question exists in the sixth archive:
⤋ Read More
@movq@www.uninformativ.de I didn’t run the command as you recommended, but, I wiped things once more, and ran jenny -f, and this time got:
david@arrakis:~$ jenny -f
Fetching archived feed https://anthony.buc.ci/user/abucci/twtxt.txt/1 (configured as abucci, https://anthony.buc.ci/user/abucci/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2024-04.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://darch.dk/twtxt-archive.txt (configured as soren, https://darch.dk/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2024-04-21_6v47cua.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/1 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2024-03.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2022-12-21_2us6qbq.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/2 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2024-02.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2022-01-14_ew5gzca.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/3 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2024-01.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-12-23_f6y65bq.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/4 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-12.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-12-04_e4x7yba.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/5 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-11.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-11-18_42tjxba.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/6 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-10.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-11-08_i2wnvaa.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-09.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-10-23_kvwn5oa.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-08.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-10-11_mljudaa.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-07.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-09-22_5mkqwua.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-06.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-07-27_xcnzmlq.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-05.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-06-16_mtedqya.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-04.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-04-29_z7lvzja.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-03.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-03-19_xjabvhq.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-02.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-02-24_te4a6oa.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-01.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-01-26_qxgigma.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-12.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2020-12-13_igfnala.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-11.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-10.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-09.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-08.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-07.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-06.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-05.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-04.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-03.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-02.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-01.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-12.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-11.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-10.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-09.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-08.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-07.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-06.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-05.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-04.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-03.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-02.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-01.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2020-12.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Notice that @prologic@twtxt.net’s /6 is there. I found the twtxt then. Kind of odd it didn’t show before.
GENESYSM-ADN6: A 3.5″ SubCompact System with Triple 2.5GbE LAN Ports
GENESYSM-ADN6: A 3.5” SubCompact System with Triple 2.5GbE LAN Ports ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1095 ARCHIVED:78843 CACHE:2434 FOLLOWERS:17 FOLLOWING:14
Apple Releases visionOS 2 With 2D Spatial Photos Feature, Persona Updates, Improved Guest Mode and More
Apple today released visionOS 2, the newest version of the visionOS operating system that launched alongside the Vision Pro back in February.
visionOS 2 can be downloaded on all Vision Pro headsets by navigat … ⌘ Read more
↳
In-reply-to
»
Something odd just happened to my twtxt timeline... A bunch of twts dissapered, others were marked to be deleted in mutt. so I nuked my whole twtxt Maildir and deleted my ~/.cache/jenny in order to start with a fresh Pull. I pulled feed as usual. Now like HALF the twts aren't there 😂 even my my last replay. WTF IS GOING ON? 🤣🤣🤣
⤋ Read More
More:
Subject: The [tag URI scheme](https://en.wikipedia.org/wiki/Tag_URI_scheme) looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be
somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick? Instead of using `tag:` as the prefix/protocol, it would more it clear
what we are talking about by using `in-reply-to:` (https://indieweb.org/in-reply-to) or `replyto:` similar to `mailto:` 1. `(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)' 2.
`(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)' 2. `(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)' I know it's longer that 7-11 characters, but it's self-explaining when looking at the
twtxt.txt in the raw, and the cases above can all be caught with this regex: `\([\w-]*reply[\w-]*\:` Is this something that would work?
Subject: The [tag URI scheme](https://en.wikipedia.org/wiki/Tag_URI_scheme) looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be
somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick? Instead of using `tag:` as the prefix/protocol, it would more it clear
what we are talking about by using `in-reply-to:` (https://indieweb.org/in-reply-to) or `replyto:` similar to `mailto:` 1. `(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)` 2.
`(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)` 3. `(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)` I know it's longer that 7-11 characters, but it's self-explaining when looking at the
twtxt.txt in the raw, and the cases above can all be caught with this regex: `\([\w-]*reply[\w-]*\:` Is this something that would work?
Notice the difference? Soren edited, and broke everything.
🧮 USERS:1 FEEDS:2 TWTS:1094 ARCHIVED:78808 CACHE:2451 FOLLOWERS:17 FOLLOWING:14
↳
In-reply-to
»
The tag URI scheme looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick?
⤋ Read More
@mckinley@twtxt.net Thanks for the feedback.
- Yeah I agrees that nick sound not be part of syntax. Any valid URL to a twtxt.txt-file should be enough and is more clear, so it is not confused with a email (one of the the issues with webfinger and fedivese handles)
- I think any valid URL would work, since we are not bound to look for exact matches. Accepting both http and https as well as a gemni and gophe could all work as long as the path to the twtxt.txt is the same.
- My idea is that you quote the timestamp as it is in the original twtxt.txt that you are referring to, so you can do it by simply copy/pasting. Also what are the change that the same human will make two different posts within the same second?!
Regarding the whole cryptographic keys for identity, to me it seems like an unnecessary layer of complexity. If you move to a new house or city you tell people that you moved - you can do the same in a twtxt.txt. Just post something like “I move to this new URL, please follow me there!” I did that with my feeds at least twice, and you guys still seem to read my posts:)
↳
In-reply-to
»
@prologic Some criticisms and a possible alternative direction:
⤋ Read More
The tag URI scheme looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be somewhat trivial to parse. But there are still the issue with what the name/id should be… Maybe it doesn’t have to bee that stick?
Instead of using tag: as the prefix/protocol, it would more it clear what we are talking about by using in-reply-to: (https://indieweb.org/in-reply-to) or replyto: similar to mailto:
(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)
(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
I know it’s longer that 7-11 characters, but it’s self-explaining when looking at the twtxt.txt in the raw, and the cases above can all be caught with this regex: \([\w-]*reply[\w-]*\:
Is this something that would work?
🧮 USERS:1 FEEDS:2 TWTS:1093 ARCHIVED:78768 CACHE:2438 FOLLOWERS:17 FOLLOWING:14