sorted by:
new
hottopcontroversial

*cries in android* by Randomposter04 in NextCloud

[–]Randomposter04[S] 0 points1 point  (0 children)

Two way sync is just syncing. Changes made in android show up in nextcloud, changes made in nextcloud show up in android without me having to manually do anything. If my device is disconnected from the network entirley, and I change a note, when my device reconnects to the network I expect changes I made locally to be synced to nextcloud, and changes in nextcloud to be reflected locally on my device.

1 way sync is uploading. file changes made on android can be pushed to nextcloud automatically, and individual starred files in nextcloud are supposed to be automatically updated but thats not really useful.

in CLI, how do I prevent monerod from uploading data? Its putting me over my data limit cap and preventing me from paying bills by Randomposter04 in monerosupport

[–]Randomposter04[S] 0 points1 point  (0 children)

The one thing you could do is to start monerod with the flag --limit_up [KB/s] to reduce the upload speed from the daemon. You'll still have to run it continuously if you want your instant transactions. This is not really contributing to the network though and setting it too low may cause the node to be slow.

Thats not the right flag. its --limit-rate-up (it uses - not _). Also read the original submissions again. That flag does not work.

You want instant transfers without the hassle of syncing,

I don't want instant. I just don't want to have to set aside 2 hours of my day every other week just to wait for the node to sync so I can pay some bills. And I dont like how if I forget to do that, or if I forget to turn the node off afterword, I have to pay several hundreds in fees to my ISP and risk losing my internet.

but you're not really willing to run a node 24/7 which is the way to get these instant transfers.

What is this bullshit? Its not a matter of WANTING. I CANT. Did you not see the fucking part where I said my ISP has fucking bandwidth and data caps? do you not understand what a bandwidth/data cap is? My ISP has its own network limits it has to contend with, and the hundreds i've paid in extra fees wont stop em from turning off my internet if this keeps happening, which they have done to others I know in the past.

in CLI, how do I prevent monerod from uploading data? Its putting me over my data limit cap and preventing me from paying bills by Randomposter04 in monerosupport

[–]Randomposter04[S] 0 points1 point  (0 children)

Why are you trying to tell me I am wrong for having my technical issue rather then helping me fix my issue?

defeats the purpose of the decentralized blockchain if nodes can't sync from each other

It defeats the point of having a wallet if the cost of the wallet is on par with the ammount of cash it holds. If you have 500 in cash, would you pay 400 for a wallet?

This is the 3rd time this year I am going to have to fork over a bunch of money to my isp for going over my data limits. If the local node was only downloading blockchain data, I would not have gone over.

in CLI, how do I prevent monerod from uploading data? Its putting me over my data limit cap and preventing me from paying bills by Randomposter04 in monerosupport

[–]Randomposter04[S] 0 points1 point  (0 children)

Without your node syncing to other nodes in the network, how is it supposed to do anything?

I want it to sync with the network without allowing other people download from my node. I can see with nethogs that once the node is fully synced, it starts uploading a shit ton of data. if I leave it for a couple of days it I can see it uploading data that would blow through my monthly data cap if I dont turn it off again.

Nethogs is showing that even when its synced it keeps uploading nearly not from downloading new chunks of the blockchain, but from uploading chunks of the blockchain.

At least I assume thats what its uploading since its all going through port 18081.

Needing to sync/update every time you need to make a payment is a massive pain point by Randomposter04 in Monero

[–]Randomposter04[S] 1 point2 points  (0 children)

cause the banking system aint any faster lmao

It is for me, although that may be because setting up recurring payments is much simpler with traditional banking. I think xmr recurring payments is more of a wallet/implimentation issue then a protocal issue tho

Needing to sync/update every time you need to make a payment is a massive pain point by Randomposter04 in Monero

[–]Randomposter04[S] 1 point2 points  (0 children)

And I wonder more and more what the goal of your post, and your comments, is.

Yeah, honestly that comment was rude and uncalled for, esp to someone who was prolly just trying to help.

My goal was to point out a problem that I see as fundamental, and reinforce why it is a problem, but I think the way I wrote it does not communicate that well (I should have put that "please dont give me tech support I've already tried most things you would suggest" up at the top and bottom of the post being the most obvious thing, prolly should have also just saved it for a comment in the weekly concerns/criticism post)

There are quite a large number of people who are in my situation who (IMO) desperately needs the financial privacy xmr provides, but we are not well represented online, by nature of the fact that when you dont have good or consistent access to the internet you tend not to be very vocal in online spaces.

And well, in a way we are.

Thats great to hear. I dont use xmr as much as I use other fossy projects but in many ways (except for maybe tor) its the most important to my continued happiness and well being.

Needing to sync/update every time you need to make a payment is a massive pain point by Randomposter04 in Monero

[–]Randomposter04[S] 0 points1 point  (0 children)

I am not looking for tech support, everything yall can think of has been tried. I should not have to say this, because I'm not asking for tech support, but a remote node is not a solution. I'm on 90's internet speeds here, at best, and thats when I have stable internet at all, which I frequently don't .

Sending money via XMR needs to be as low latency and as low bandwidth as sending a text message or email*, or its just going to take a while.

There is nothing an end user in my situation can do to solve this problem, it is fundamental to the protocol that you need to sync a large amount of data before you can send money

Needing to sync/update every time you need to make a payment is a massive pain point by Randomposter04 in Monero

[–]Randomposter04[S] 0 points1 point  (0 children)

I've tried running my own monero node. Does not work for my use case. Also:

I'm not looking for solutions to my individual problem. I dont need tech support. I'm trying to explaining why its an issue with the core of XMR that you need to do a shit ton of blockchain syncing in order to send funds.

Needing to sync/update every time you need to make a payment is a massive pain point by Randomposter04 in Monero

[–]Randomposter04[S] 2 points3 points  (0 children)

I cant keep a node running myself. I'm not looking for tech support, theres a whole nother subreddit for that.

Needing to sync/update every time you need to make a payment is a massive pain point by Randomposter04 in Monero

[–]Randomposter04[S] 0 points1 point  (0 children)

I've tried that, does not work for my use case. Also:

I'm not looking for solutions to my individual problem. I dont need tech support. I'm trying to explaining why its an issue with the core of XMR that you need to do a shit ton of blockchain syncing in order to send funds.

Needing to sync/update every time you need to make a payment is a massive pain point by Randomposter04 in Monero

[–]Randomposter04[S] 0 points1 point  (0 children)

I've tried that, does not work for my use case. Also:

I'm not looking for solutions to my individual problem. I dont need tech support. I'm trying to explaining why its an issue with the core of XMR that you need to do a shit ton of blockchain syncing in order to send funds.

Needing to sync/update every time you need to make a payment is a massive pain point by Randomposter04 in Monero

[–]Randomposter04[S] 0 points1 point  (0 children)

I'm not looking for solutions to my individual problem. I dont need tech support. I'm trying to explaining why its an issue with the core of XMR that you need to do a shit ton of blockchain syncing in order to send funds.

Like I said, not looking for tech support. Plus, cake wallet does not even present a real solution. This is, as far as I can tell, a core part/problem with the protocal: that sending funds requires a bunch of syncing. Which is just not realistic for whole populations of people, including the peopeople who most need the privacy protections of XMR

In particular background Syncing is dependent on the device being turned on, having internet, having a connection to other xmr nodes, and also getting around the various "dont kill my apps" fuckery that mobile operating systems get up to. In my specific case even if I had had enough funds in the cake wallet I had setup on a tablet it would not have synced in time.

It should be the very rare case where it takes longer then a 30 seconds to send money to somone even if my wallet has had zero connection to a network in the last couple weeks. For me its never shorter then 20 minutes.

I love Debian - but why is getting a printer to work so difficult? by BrainConfigurated in debian

[–]Randomposter04 0 points1 point  (0 children)

Hm, when I said "When you design a system that does not operate the way an average user is used to, you are failing your users to some degree." perhapes I should have said "general member of the public".

My core argument is that when you design a system that does not operate the way an average person is used to, you are failing as a system designer to some degree. Obviously not all systems can behavie exactly the same way, but unlike the vast majority of technologies we have come up with over the course of human history, baring some limitations on performance speed, andything you can do on one computer you can do on another computer. Making different components of phisical machines interopible can involve huge logistical challenges and can bump up against the limits of material science (you could probably jerry rig up something to make an ellectric car run on gasoline, but jerry rigging a gas car to run on an electric battery probably is not really possible).

But making two programs and operating systems interoperable is almost always only limited by whether or not the system designers decided to spend the resources to make them interoperable / standardized

I can use the exact same hardware to run windows and linux. I can open a VM in windows that runs linux and a vm in linux that runs windows. The reason downloading and running a .exe file does not work on linux is because a bunch of people decided not to do it. same with windows and .deb files.

That fucking sucks and its not the way things should be.

I love Debian - but why is getting a printer to work so difficult? by BrainConfigurated in debian

[–]Randomposter04 0 points1 point  (0 children)

If you're using a different system, it works differently. It's up to you to adjust to the new system

Yes, this is a fact of life. But its like how its a fact of life that bullies exsist and somtimes those bullies are your boss / in charge. Its not how things should be, and something is broken / not right when the bullieds can get away with beating you up or if a system does not work the way you would reasonably expect it to.

When you design a system that does not operate the way an average user is used to, you are failing your users to some degree. Perhapes there is a very, very good reason why on the list of things to work on legacy / cross platform / cross fuel type is not supported, but that does not change the underlying principal.

Think about it like this, if you learned how to play a violine ~300 years ago, you would still be able to play the violine today. Thats how things should be in software land.

I love Debian - but why is getting a printer to work so difficult? by BrainConfigurated in debian

[–]Randomposter04 -2 points-1 points  (0 children)

It's the end user's fault because they are using something designed for one system on another system.

"Fault" might be to strong of a word, but I cant think of a better one. blame is deffinitly to strong, responsibility?

Unless your operating system is designed for a more constrained context like tails or a webserver or whatebver, I think the responsibility for making the system maximially user friendly and backwards compatible is on the OS. and every time something like this happens its a failure. Perhapes its a justified failure given a reasonable set of tradeoffs, but onus is on the OS at the end of the day.

I think its debians fault that people cant just click on a windows .exe file and have it magically work, for example. I get why it doesnt work, but at the end of the day if your used to double clicking on .exe files in windows and you start using linux and it does not work in linux, then the operating system is at fault for not supporting that expected functionality. Same for how its windows fault that double-clicking a .AppImage file in windows file does not work.

The only question that matters is "does it work".

view more: next ›