Conversation
The UI of my video chat thing is going to look like a desktop GUI, because I understand that metaphor
2
0
2
@sun windows 3.1 beloved

needs bevels tho
1
0
0
@hj I actually have a project to completely imitate windows 3.1 in the browser but for video chat I radically simplified the code so I didn't have to fight CSS as much.
1
0
1
@sun hm. I recently installed Windows Me on 86Box so that I can implement the style more accurately and support different palettes in Themes 3
0
0
0
@lucy you can resize and drag all the windows around
1
0
1
@sun @lucy i should add "resize and drag around" feature to PleromaFE as an april fools gag
1
2
3
@hj @lucy my intent with the windows 3.1 theme was in fact to make a pleroma frontend.
1
0
2
@sun @lucy can I convince you to contribute to existing frontend instead?
1
0
0
@hj @lucy I want to do things you don't want to do
1
1
1
@sun @lucy we already support TLS, can you elaborate?
1
0
1
@hj @lucy mitra has tipping using monero for ex and is close to pleroma-fe compatible
2
0
1
@sun @hj i wish people would tip me xmr for my low effort shitposting
1
1
4
@sun @lucy having a generalized "tip this user" feature could be nice, as long as it's generalized and user gets to choose how they want it to be paypal/monero/liberapay/bitcoin/etc
1
1
1
@lucy @sun XMR? Is that new WebMoney currency?
1
0
0
@hj @sun xmr is monero
1
0
0
@sun @lucy the two unspoken rules that are pretty much only in my head

- optional/configurable opt-in or opt-out is up to discussion
- no centralization/no local-only features
- nothing that can be seen like brand/service promotion in codebase
- user must be able to override admin defaults

that's just me though, everything is up to discussion.
image.png
2
0
5
@hj @lucy it would necessarily involve supporting a limited set of services explicitly in the codebase. some things could be abstracted, for example every ethereum L2 and Ethereum work EXACTLY the same.
1
0
0
@sun @lucy yeah I think having abstracted away and multiple choices would work well and acceptable.
1
0
0
@hj @lucy @sun Well at least for Monero/Paypal/… just putting the ID/URL/… in bio field could be enough.
1
1
1
@hj @lucy supporting bitcoin, square and paypal will all take coding specific integrations for those
1
0
0
@sun @lucy it can be that whatever has proper integration can be integrated, everything else can be a link. I'd put my liberapay account there.
1
0
0
@hj @lucy I would have to make specific code to integrate ethereum and ethereum layer2s, but it could not even be loaded until someone wants to tip, would that be okay
1
0
0
@asa @hj @lucy most of the Eth L2s are extremely cheap and fast
0
0
1
@sun @lucy i think so. We'll need to discuss the details because I don't know what everything is. Last time I checked you needed to download Google-approved Chrome™️ Manifest v3 Extension™️ from centralized Chrome™️ WebStore™️ to access your """"""""""decentralized"""""""""" wallet.

Interacting with browser extensions is a no-no from me at least.
1
0
0
@asa @hj @lucy when it came out it fucking sucked bad, the entire ecosystem was ungodly bad. if you persevered you'd have made a ton of money but it was MISERABLE
0
0
1
@asa Crytocurrencies can be trivially split into fractions much smaller than one coin you know?

There even used to be a smaller unit than the yen, although that was no longer used when the yen's value decreased.
0
0
0
@lanodan @lucy @sun I mean having a separate "tip this user" button in profile page would be nice.
3
0
0
@hj @lucy all of them use an extension because you need a barrier between the website and the thing that stores your private key. it injects an object into the page that mediates the transaction
2
0
0
@hj @lucy @lanodan @sun well meme'd my friend! enjoy your pleroma gold
1
0
4
@hj @lucy @sun Yeah, just seems like a good way to at least store the info so other fedi software doesn't needs anything special and would still benefit from it.
1
0
1
@sun @lucy >you need a barrier between the website and the thing that stores your private key

it's called "separate application"
1
0
0
@lanodan @lucy @sun do we have machine-readable-only fields in Pleroma? So that we can implement cat ears and stuff?
1
0
0
@hj @lucy you can do that with bitcoin because all it is is "transfer x units" but interaction with ethereum can be a smart contract that has 2-way communication.
1
0
0
@sun @lucy english, please.

this is getting off-topic but,

KeePassXC is a separate application for password management. It has browser extension, doesn't require integration from website to work, has 2-way communication, browser extension isn't required since you can either do autotype or copy-paste stuff back and forth.
.gif
1
0
0
@hj @lucy keepassxc detects an input field and fills in the form with its data, if it were doing challenge-response cryptography it would require the extension and integration code.
1
0
0
@sun @lucy you could copy-paste challenge and copy-paste response. You could support U2F FIDO or whatever.
0
0
0
@lanodan @lucy @sun we could have machine-only field that contains object that stores a type and id so that we could i.e. xdg-open://bitcoin-qt?id=XXXXXX or something and also display a button for it on profile.
2
1
0
@hj @lucy @lanodan Let's do payment URLs then, that won't require any interaction with an extension. I think they work with Eth L2s.
0
0
1
@hj @lucy @sun Well the field name is already a type and I don't think any crypto-assets has URLs.
1
1
1
@lanodan @lucy @sun i'm talking about machine-readable-only fields. Those that are part of profile but not visible, intended to be used by frontend to do something cool like "tip me" button or cat ears avatar and such. Can't find the issue for it
1
0
0
@hj @lucy @sun Yeah but for the payment thing I think it would be kind of stupid because then it wouldn't federate outside of pleroma.
Like it would effectively only be useful for gadgets like cat ears and other things where it doesn't matters if non-pleroma doesn't displays it.
2
0
0
@lanodan @lucy @sun i mean, other software might or might not implement it. I stopped caring about that. As long as we expose in a neat way it it's fine.
0
0
1
@lanodan @lucy @hj I envision two components:

1. you can enter a bitcoin or eth payment URL into a user-defined field and pleroma will make it a real link.

2. you can enter a payment URL in a post and it will be made into a real link.

Literally all that has to be implemented is, recognition of bitcoin and ETH payment URLs, and linkifying it. No integration, no nothing, just recognizing standard links for payments. I think there is a similar mechanism to forward someoen to a Square or Paypal payment page with an amount. Maybe for Liberapay too.
2
1
2
@sun @lucy @lanodan that is the sanest and best solution so far.
1
0
1
@hj @lucy @lanodan my work day is done let me look at it.
0
0
0

@sun @lucy @hj Examples of the linkification would be neat because I have literally never seen it outside of the horror that is Paypal.

Like everytime I see something like monero/bitcoin/… or whatever it's just Bitcoin/XMR: $public_key_or_fingerprint even on things like blogs.

2
0
1
@lanodan @lucy @hj I just checked and Liberapay has payment deep links too that can be detected.
0
0
2
@asa @hj @lanodan @lucy that is what I want tbh is be able to pay with an emoji or something but that's not possible without specialized code.
0
0
1