ailaptop

"374995c91abf4369a78002f7caeef48141910a329610a856614f887aad49f107c7dba329403cf7d4b443bddc9b85166c807c97fc6836e7ea227cc1afe5082e31"

Last Notes

2026-05-03 16:42:32 UTC

- reply

Ya this is more me figuring out the current state of things with auctions. Would love to summarize it for you with a pen and paper next time we meet in person...

2026-05-02 18:17:35 UTC

- reply

@nprofile…gu0q here are some thoughts on the bidding feature for plebeian market that I recently mentioned. We are actively exploring what our options are and I suspect that you might have some ideas for us.
This approach to achieving a moving end time came out of a weekly plebeian call. @nprofile…t5pj is the architect and maintainer of the auctions feature.

2026-04-02 16:21:13 UTC

- reply

Thanks for making this amazing browser @npub1g53…drvk , I look forward to using it as my daily driver!

2026-04-02 16:20:21 UTC

- reply

/home/c03rad0r/hashtree/apps/iris/WEBVIEW_LOWER_HALF_DEBUG_REPORT.md
# Iris Linux child-webview renders in lower half only
## Summary for maintainers
On Linux, Iris child webviews (external pages like `https://google.com`) render only in the lower half of the available content area. The upper half is black/empty. This persists across resize and across Wayland/X11. Frontend bounds math is internally correct, but Linux-native applied geometry appears inconsistent with requested bounds.
This report is intended to be pasted directly into a GitHub issue.
## Repro steps
1. Start Iris dev shell:
```bash
cd /home/c03rad0r/hashtree/apps/iris
pnpm run tauri:dev
```
2. Open a site such as `https://google.com`.
3. Observe: web content appears in the lower half only; upper half is black/empty.
4. Resize window; symptom persists.
## Environment and context
- Platform: Linux (Ubuntu 25.10)
- Session: Wayland (`XDG_SESSION_TYPE=wayland`)
- Also tested with X11 backend (`GDK_BACKEND=x11`) with same symptom
- Rust toolchain and GTK/WebKit build dependencies installed successfully
- App compiles and runs; issue is runtime rendering/layout in child webview
## Late discovery: clean restart is required for valid runs
Late in debugging we discovered that stale `tauri dev` / `vite` / `target/debug/iris` processes can invalidate results.
Required cleanup before each validation run:
```bash
pkill -f "pnpm run tauri:dev|target/debug/iris|vite" || true
```
Without this cleanup, subsequent runs can fail or attach to stale state (for example: Vite port conflicts and inconsistent runtime behavior), producing false negatives.
Important timeline note:
- This clean-restart requirement was introduced relatively late in the investigation.
- Therefore, some earlier "no fix" observations may have been confounded by stale process state.
- Even after adopting this cleanup step, the split-screen issue still reproduces on the debug branch.
## What we confirmed with instrumentation
### Frontend state is consistent
Automation state repeatedly reported expected layout values:
- `windowInnerHeight: 364`
- `toolbarHeight: 48`
- `childBoundsTop: 48`
- `childBoundsHeight: 316`
`48 + 316 = 364`, so frontend computes child bounds correctly.
### Native geometry did not match intent on Linux
During debugging, native readback often showed behavior like:
- requested `y=48`, but applied position read as `y=0`
- requested `height=316`, but applied logical height around `363`
- physical size examples around `2400x726` at DPR 2
This points away from frontend inset math and toward Linux child-webview geometry/compositor behavior.
## Important clarification: URL bar is not the cause
We explicitly checked whether the URL bar/toolbar might be consuming half the height.
- The URL bar is rendered in the main Svelte shell, not as a second child webview.
- Toolbar height is ~48 px in the failing case, not half the window.
- Child bounds reported by frontend still fill the entire remaining area.
So this is not simply an oversized URL bar.
## Attempted fixes (all unsuccessful)
### Runtime/backend env experiments
1. `GDK_BACKEND=x11`
2. `WINIT_UNIX_BACKEND=x11 GDK_SCALE=1 GDK_DPI_SCALE=1`
3. `WEBKIT_DISABLE_DMABUF_RENDERER=1 WEBKIT_DISABLE_COMPOSITING_MODE=1`
4. Added mandatory pre-run cleanup:
- `pkill -f "pnpm run tauri:dev|target/debug/iris|vite" || true`
Result for all: no fix.
### `src-tauri/src/nip07.rs` geometry strategy changes
1. Linux bounds mode switched between physical-scaled and logical paths
2. Removed `.auto_resize()` from builder path
3. Forced `set_auto_resize(false)` + explicit `set_bounds(...)`
4. Alternative explicit `set_position(...) + set_size(...)`
5. Added hide/apply/show patterns
6. Added delayed bounds reapply retries
- immediate + 80ms + 220ms
7. Reused retry logic in both create and update paths (`set_webview_bounds`)
8. Added and removed zoom workarounds
- `set_zoom(scale)`
- `set_zoom(1/scale)`
9. Added and removed scroll reset workaround on page finish
- `window.scrollTo(0, 0)` via eval
Result: still no fix.
### Frontend-side checks
1. Verified `browserViewportInsets()` / toolbar values
2. Verified automation state updates are coherent and stable
3. Verified symptom persists even when computed child bounds are correct
Result: no frontend math bug identified.
## Current best hypothesis
Linux child-webview composition/geometry handling in Tauri/WRY/WebKitGTK is overriding or misapplying child bounds in this app setup (or in current runtime/library versions), causing persistent top-offset/height mismatch and the visible half-screen rendering artifact.
## Current code status
- Multiple Linux-specific mitigation patches were tried in `apps/iris/src-tauri/src/nip07.rs`.
- Test suite remains green after changes (`cargo test` passes).
- Behavior still reproduces visually.
## What we need from upstream guidance
1. Known matching issues for Linux child webviews with black top/half-height rendering.
2. Canonical Linux-safe pattern for child webview attach/resize on HiDPI.
3. Whether this is a known WebKitGTK regression window and recommended version pin.
4. Whether Linux should use a fallback architecture (single-webview + iframe) for stability.
---
## Search prompt (next round)
I need a root-cause-level diagnosis for a Linux-only Tauri v2 child webview rendering bug.
Context:
- App: Tauri v2 + Rust backend + Svelte frontend
- Uses `window.add_child(...)` child webviews on Linux (WebKitGTK)
- Symptom: child page renders only in lower half; top half black/empty
- Frontend layout math is correct (`childBoundsTop + childBoundsHeight == windowInnerHeight`)
- Native behavior inconsistent: requested y/height differs from applied runtime geometry
- Reproduces on Wayland and X11 (`GDK_BACKEND=x11`)
- Tried and failed:
- logical vs physical bounds strategies
- `set_auto_resize(false)` + manual bounds
- `set_position + set_size`
- delayed bounds reapply (0ms, 80ms, 220ms)
- hide/show around initial bounds
- zoom adjustments (`scale`, `1/scale`)
- `WEBKIT_DISABLE_DMABUF_RENDERER=1`
- `WEBKIT_DISABLE_COMPOSITING_MODE=1`
Please provide:
1) exact matching upstream issues/PRs in `tauri-apps/tauri`, `tauri-apps/wry`, `tauri-apps/tao`, and WebKitGTK trackers,
2) ranked next experiments with expected pass/fail signals,
3) concrete workaround patches with minimal code snippets,
4) version-specific regression guidance (especially WebKitGTK versions),
5) production fallback recommendation (Linux single-webview+iframe mode) with security tradeoffs.
Output format:
- Section A: matching evidence + links
- Section B: prioritized experiments + interpretation
- Section C: immediate workaround patch
- Section D: long-term architecture recommendation

2026-03-05 20:05:51 UTC

https://npub12m5exm2uk3xa674cc5r0hlyvccs5xxn7qv83ezuteefv5972nquq4j4szl.blossom.band/796fbca49910abccd28d7e2fef0bab8d0526d875f951b2769796b24f02c8c8e2.png
https://npub12m5exm2uk3xa674cc5r0hlyvccs5xxn7qv83ezuteefv5972nquq4j4szl.blossom.band/796fbca49910abccd28d7e2fef0bab8d0526d875f951b2769796b24f02c8c8e2.png

2026-03-05 20:05:09 UTC

https://npub12m5exm2uk3xa674cc5r0hlyvccs5xxn7qv83ezuteefv5972nquq4j4szl.blossom.band/796fbca49910abccd28d7e2fef0bab8d0526d875f951b2769796b24f02c8c8e2.png

2026-02-24 14:41:44 UTC

https://meshtastic.org/docs/configuration/module/audio/

2026-02-24 14:41:25 UTC

https://github.com/greenart7c3/Citrine/releases/tag/v1.0.2

2026-02-01 12:20:09 UTC

# Summary: Starting a White-Label ISP in Madeira
This document summarizes the key steps, requirements, and considerations for starting a white-label Internet Service Provider (ISP) in Madeira, Portugal, based on our conversation.
## 1. The Basics of Being an ISP
- **Technical Independence**: An individual can become an Autonomous System (AS) by getting an ASN and IP addresses, but this is complex and expensive, requiring payment for transit and data center space.
- **Community ISP (Reselling)**: To provide internet to others, you must register as a company, handle billing, and comply with regulators (like ANACOM in Portugal).
- **Home Network**: Simply using an ISP's service does not make you an ISP.
### Relevant Links:
- [Can you become your own ISP? (Network Engineering Stack Exchange)](https://networkengineering.stackexchange.com/questions/62247/can-you-become-your-own-isp)
- [How to become my own internet provider (Quora)](https://www.quora.com/Can-you-explain-step-by-step-how-I-can-become-my-own-internet-service-provider)
- [Ofcom (UK Regulator Example)](https://www.ofcom.org.uk/phones-telecoms-and-internet/information-for-industry/internet-service-providers)
## 2. Mandatory Steps for an ISP in Madeira
To operate legally, you must establish a formal business and register with the appropriate authorities.
- **Business Structure**: You must register a company (e.g., Lda. or S.A.). You can leverage the **International Business Centre of Madeira (IBCM)** for a reduced corporate tax rate of 5%, which requires creating at least one job and investing €75,000 in assets within two years.
- **Telecommunications Registration**: You must notify the national regulator, **ANACOM**, of your intent to provide electronic communication services before you begin operations.
### Relevant Links:
- [International Business Centre of Madeira (Wikipedia)](https://en.wikipedia.org/wiki/International_Business_Centre_of_Madeira)
- [The New Portuguese Electronic Communications Law (Lexology)](https://www.lexology.com/library/detail.aspx?g=0f8e6d4c-7a4f-4d2b-8b7c-0e3f3d1a1b1e)
- [ANACOM (Wikipedia)](https://en.wikipedia.org/wiki/Autoridade_Nacional_de_Comunica%C3%A7%C3%B5es)
## 3. Operating as a White-Label Virtual ISP (VISP)
This model involves reselling an existing provider's service under your own brand.
- **Wholesale Partners**: Your main partners for infrastructure in Madeira will be **MEO (Altice Portugal)**, **NOS**, or **Vodafone**.
- **Business Model**: As a **White Label Reseller**, you manage all branding, billing, and customer support. The customer only sees your brand.
- **Legal & Regulatory**: Even as a reseller, you must incorporate in Madeira, notify ANACOM, and have a clear Service Level Agreement (SLA) with your wholesale partner defining support responsibilities.
### Relevant Links:
- [What Is A 'White Label' Telecoms Reseller?](https://www.sysconfig.cloud/blog/what-is-a-white-label-telecoms-reseller/)
- [Become a reseller - Brdy Telecom](https://brdy.com/become-a-reseller/)
- [ISP Reseller Discussion (Reddit)](https://www.reddit.com/r/msp/comments/11e9c3j/isp_reseller_worth_considering/)
## 4. Minimum Commitments and Entry Paths
- **Direct Wholesale (MEO, NOS)**: Requires a significant monthly spend, estimated at **€5,000 - €10,000**, suitable for businesses targeting 500+ users.
- **Platform Partner/Aggregator**: A more accessible entry point for startups, with minimums as low as **10-50 subscribers** and lower setup costs.
- **Regulatory (IBCM)**: To maintain the 5% tax rate, you must create **1-2 jobs** and invest **€75,000** in assets.
### Relevant Links:
- [PriTelecom Whitelabel](https://pritelecom.com/whitelabel-reseller/)
- [Regulator imposes obligations on Altice Portugal (Broadband TV News)](https://www.broadbandtvnews.com/2023/11/28/anacom-imposes-obligations-on-altice-portugal/)
- [NOS Wholesale Solutions](https://www.nos.pt/institucional/EN/business/wholesale/pages/home.aspx)
## 5. White-Label Platforms & Technology in Portugal
While some Pan-European companies exist, you need a partner with access to Portuguese fiber networks for broadband.
- **Broadband Platforms**:
- **MEO Wholesale (Altice)**: The primary infrastructure owner.
- **Vpartner**: A major Vodafone distributor.
- **Brdy**: Offers white-label satellite broadband for rural areas.
- **Savasaachi Portugal**: An agency that helps package and rebrand telecom services.
- **PTisp**: A hosting provider that can supply complementary back-end infrastructure.
- **Madeira's Advantage**: The **EllaLink submarine cable** offers a unique marketing opportunity for low-latency services.
### Relevant Links:
- [White Label Services – Savasaachi Portugal](https://savasaachi.pt/services/white-label-services-in-the-portugal/)
- [Top Reseller Companies in Portugal (ensun)](https://ensun.co/companies/reseller/portugal)
- [EllaLink and Madeira (IBC Madeira)](https://www.ibc-madeira.com/e-business-and-technology.html)
## 6. BSS/OSS: The "Brain" of Your ISP
Business Support Systems (BSS) and Operations Support Systems (OSS) are the software interfaces provided by your white-label partner to manage your business. You do not need to build them yourself.
- **BSS (Business Support Systems)**: Handles customer-facing functions.
- **Customer Portal**: For sign-ups and account management.
- **Billing & Payments**: Automates invoicing.
- **Product Catalogue**: Where you define your service plans.
- **OSS (Operations Support Systems)**: Handles network-facing functions.
- **Automated Provisioning**: Activates a customer's service automatically.
- **Fault Management**: Monitors the network for outages.
- **Inventory Tracking**: Manages hardware like routers.
The workflow is automated: a customer signs up on the BSS, which sends an order to the OSS to activate the service on the physical network.
### Relevant Links:
- [OSS/BSS Overview (Ericsson)](https://www.ericsson.com/en/portfolio/digital-services/automated-operations/oss-bss)
- [Telenabler White Label Platform](https://www.telenabler.com/solutions)
- [What is OSS and BSS? (Gigs)](https://gigs.com/docs/glossary/oss-and-bss-in-telecom)
- [BSS vs OSS (Cerillion)](https://www.cerillion.com/insights/articles/bss-vs-oss-what-is-the-difference/)