𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍

       🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆. 
 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍 
  • 1 Post
  • 25 Comments
Joined 2 years ago
cake
Cake day: August 26th, 2022

help-circle

  • Yeah, despite the strong anti-crypto sentiment on Lemmy, this is exactly the problem that projects like Nostr is trying to solve by integrating Lighting as a first-class payment system in the ecosystem.

    Services get paid for by one of four ways:

    • Harvesting and reselling of user data. Which is wildly unpopular, and why a lot of people are on Lemmy and not Reddit or Facebook.
    • Ads. Which is also unpopular and again why people come to services like Lemmy
    • Pay-for-service, which is what you’re suggesting, only via crypto, which is easier than accepting credit card transactions, and safer for users.
    • The hosted paying for it out of the goodness of their hearts. So, charity. Sometimes there’s corporate charity, and that’s nice, except for the potential for money coming with strings attached, now or eventually.

    Someone always pays; its expensive to host a popular instance. People suggesting you should host for free are selfish freeloaders, so know that some people understand that hosting costs, and sympathize with with your desire to offset that cost.

    I like the volunteer micro-transaction model. Those who can afford to pay some amount for good service, and hopefully this provides welfare for those who can’t afford to pay. But the cryptocurrency space is a mess at the moment, and an economical currency (probably proof-of-stake rather than proof-of-work) needs to gain some traction, and overcome a lot of ignorant bigotry.



  • There are some excellent apps out there, and by and large they look and work better than commercial apps, IME. So I disagree with the assertion that I have to stay with commercial software.

    What I was asking for, in my post, was not which apps have better UX than Facebook, but rather which of the very many OSS, federated (although, not necessary for my use case), self-hosted platforms fit the specific use, and ideally with a straightforward iOS mobile app. Doesn’t have to be pretty; just has to be able to quickly take and post photos to a private channel/community/wall.

    Circles really is quite nice in all respects. I think they’re hindered by their choice of backend. I’ve been using Matrix for years, and key management has always been a hot mess. I wouldn’t be surprised if the issues we encountered were related to Matrix’s god-awful and buggy PK negotiation & management process.




  • I’m designing off the top of my head, but I think you could do it with a DHT, or even just steal some distributed ledger algorithm from a blockchain. Or, you develop a distributed skip tree – but you’re right, any sort of distributed query is going to have a possibly unacceptable latency. So you might – like Bitcoin – distributed the index itself to participants (which could be large), but federate the indexing operation s.t. rather than a dozen different search engine crawlers hitting each web site, you’d have one or two crawlers per site feeding the shared index.

    Distributed search engines have existed for over a decade. Several solutions for distributed Lucene clusters exist (SOLR, katta, ElasticSearch, O2) and while they’re mostly designed to be run in a LAN where the latencies between nodes is small, I don’t think it’s impossible to imagine a fairly low-latency distributed, replicated index where the nodes have a small subset of peer nodes which, together, encompass the entire index. No instance has the same set of peer nodes, but the combined index is eventually consistent.

    Again, I’m thinking more about federating and distributing the index-building, to reduce web sites being hammered by search engines which constitute 80% of their traffic. Federating and distributing the query mechanism is a harder problem, but there’s a lot of existing R&D in this area, and technologies that could be borrowed from other domains (the aforementioned DHT and distributed ledger algorithms).


  • let me know if you have questions.

    I have all the questions. I’m peripherally aware of ESP32; my experience with it, and its capabilities, is severely limited, and IME interface changes require recompiling and re-flashing things. Many of my questions stem from that ignorance.

    1. Integration support. I assume GadgetBridge on Android is how you’d do it? Or is there another app?
    2. How is the battery life IRL?
    3. What does the watch face & app space look like? The FAQ mentions a “gallery”, and instructions for contributions describe the github PR process. Is the gallery just the list of watch faces on the sqfmi website?
    4. What’s the process for changing faces, and installing additional functionality? From the docs, it looks as if this must be done over a serial cable, despite the device having WiFi capability. I assume that’s because adding faces is basically re-flashing the firmware, which is not supported over wireless? So, to get a new face, you clone the repo, compile a new firmware, and flash the device over a serial cable?
    5. The FAQ verbiage is confusing regarding the display technology, but I think it’s saying the display isn’t reflective LCD like the Pebble.
    6. Can you have multiple faces on the device, or do you have to re-flash it to change the face? The FAQ says the face is the entire firmware, implying only one face on the device at a time.
    7. If you’re part of the community: have there been any discussions about future development to add, e.g. health monitor hardware?
    8. Is there any integration with a phone, such as notifications? This is sort of the GadgetBridge question, but more about what integrations - if any - are supported. Vibrate on phone ringing? Quick responses to texts? Phone calls over the watch - yeah, I know it’s not that advanced, but for example.
    9. What’s your opinion of the device? Do you use it as a daily driver?

    At under $70, I’m not expecting much, but it’d be nice to know what you expect. The sqfmi site is pretty sparse on details. If there’s an additional, deeper FAQ or Wiki, a link to that would be great.

    Thanks!



  • But control of the protocol - the definition and development - is still controlled by the for-profit company, right? It hasn’t been handed over to a nonprofit governance committee, has it?

    Federation or not, if Bluesky dominates the protocol, they can decide to stop federating and essentially kill the independent servers. Much like what Signal did. Sure, you can run your own Signal server, but without access to the dominant player’s market, and using a protocol that’s controlled monopolistically, it’s practically useless to do so - which is why almost nobody does it anymore.


  • I really like the Nostr protocol, though. It’s too bad the network is so inundated by cryptocurrency topics.

    It’s simple, it has a nice extension process (standing on the shoulders of giants), and it’s super easy and lightweight to self-host. It reminds me a lot of the early days of http, when it was more common (as a developer) to telnet to port 80 and just type in a couple of lines of header and get a response.

    Sadly, Nostr’s association with cryptocurrency, and the fact that 90% of the traffic on it is cryptocurrency created posts, has been a severe handicap.






  • I know E Ink is a company, but for most of us it’s become a de-facto term referring to the technology, like kleenex, or q-tips.

    I have every Pebble model, and used them until the last one’s battery finally gave out. I’ve been using various e-ink (e-paper) readers, from the first Sony to my current Kobo & reMarkable (one for leisure reading, t’other for PDFs and writing). Are those displays different technologies than E Ink’s? Does the display process E Ink uses differ from other e-paper technologies? Are they not all based on polarized, bi-colored balls?

    I have nothing against pedantry, but I also think E Ink has lost (or won, depending on how you look at it) the identity game; I suspect the majority of people - if surveyed - would neither realize E Ink is a specific company, nor that the correct generic term is “e-paper.” Everyone I know (with whom the topic comes up) just call it “e-ink,” whether or not it comes from that company. Similarly, I’ve never heard anyone call it “e-paper” IRL.

    P.S. I just did a search for “e-paper watches”, and most results call them “e-ink.” Maybe they all use E Ink-brand displays, but I can’t really tell since none seem to capitalize or ™ the term. There’s a bunch of cheap watches on Alibaba which are called “e-ink” watches - are those all really using E Ink brand displays?



  • Mine is 3-pronged:

    1. btrfs + snapper takes care of most level-1 situations, and I take a snapshot of every /root change, plus one nightly /home snapshot. but it’s pretty demanding on disk space, and doesn’t handle drive failure; so I also do
    2. restic + USB drive, which I can cram way more snapshots onto, so I keep a couple of weeks of daily snapshots, one monthly snapshot for a year, and one snapshot per year, going back several years. I currently have snapshots from my past 3 computers on one giant drive. However, these drives can also fail, and won’t protect me from burglary or house fire, so I also do
    3. restic + BackBlaze. I just take a nightly snapshot for every computer and VM I manage. My monthly B2 bill is around $10. The VMs don’t change much, and I only snapshot data and config directories (only stuff I can’t spin up fairly quickly in a container, or via a simple install command), so most of the charge comes from a couple of decades of amateur digital photography, and an archive of all our digital music (because I’ll be damned if I’m going to spend weeks re-digitizing all those CDs).

    The only “restore entire system b/c of screwing up the OS” is #1. I could - and probably should, make a whole disk snapshot to a backup drive via #2, but I’m waiting until bcachefs is more mature, then I’ll migrate to that, for the interesting replication options it allows which would make real-time disk replication to slow USB drives practical; I’d only need to snapshot /efi after kernel upgrades, and if I had that set up and a spare NVME on hand, I could probably be back up and running within a half hour.



  • This is a great question, in that it made me wonder why the Fediverse hasn’t come up with a distributed search engine yet. I can see the general shape of a system, and it’d require some novel solutions to keep it scalable while still allowing reasonably complex queries. The biggest problems with search engines is that they’re all scanning the entire internet and generating a huge percent of all internet traffic; they’re all creating their own indexes, which is computationally expensive; their indexes are huge, which is space-expensive; and quality query results require a fair amount of computing resources.

    A distributed search engine, with something like a DHT for the index, with partitioning and replication, and a moderation system to control bad actors and trojan nodes. DDG and SearX are sort of front ends for a system like this, except that they just hand off the queries to one (or two) of the big monolithic engines.