Rums
182 posts

Rums
@rumscsgo
Doing browser extension stuff at https://t.co/KR1X5uQibt.
Katılım Kasım 2012
111 Takip Edilen333 Takipçiler

@HKPhooey__ @skinscom We don’t seriously assume that a site owned by an online casino plans to adhere to any laws?
English

@skinscom You’ll owe VAT when selling to any European users your spread is nowhere near high enough to cover this. You’re creating a time bomb without knowing it.
GIF
English

@Eton_64 Not quite, the account gets a 30d trade ban, the items itself would be tradable again in 7 days.
If these items now were permanently untradeable, that would completely remove any way of abusing the system. And it would basically lower the existing supply, another huge plus.
English

@oranges0401 @Erroden_ Update: You were right. I reverted it back to individual sites
x.com/rumscsgo/statu…
Rums@rumscsgo
Thank you, the community, for you involvement in BetterFloat. I read lots of justified concerns about our new permissions today. I heard you and changed the "all" permission back to individual sites to provide additional transparency (v.3.2.2). Thank you for your support 🖤
English

@SpectralOwl I totally understand the purpose of minimum required permission.
I didn't really think this decision through enough, given how requesting the "all" permission has become the default for extensions.
You guys reminded me and you were absolutely right to do so.
English

@rumscsgo Totally understand why you made the decision to change the permissions to begin with, but this is the "proper" way. Lots of people are fairly nervous when it comes to security, especially in the skins community where the security of their browser can be worth thousands of $
English

@_pedantic_dev We did include a few more markets in the list, which we are going to support in the near future (including Youpin). So yeah, this is the approach we should have taken from the beginning.
English

@_pedantic_dev That's what we tried to do with the "all" permission. There's really no in-between solution.
Nevertheless, we will now just continue as before and update permissions every ~6 months now to add new markets.
English

@netstatcs2 @Erroden_ I very much acknowledge that extensions are always a security concern. And I am very much a fan of verify over trust, which is why we are open-source.
In this scene (see SIH) I am surprised this is such a big deal given our transparency (betterfloat.com/permissions).
English

@netstatcs2 @Erroden_ Changing requests requires a special permission called "webrequest", which we DONT request. Also MV3 heavily limits what extensions are able to do. Without your Steam Guard or 2FA, we still can't do those things if you setup your account correctly.
English

@netstatcs2 @Erroden_ Of course, that it s well in your right to limit the permissions you grant.
Doesn't change anything about the fact that we CANNOT do the things you talked about like replacing responses or randomly taking your skins. Please do not talk about stuff you got no idea about.
English

@oranges0401 @Erroden_ You realise that extensions don't just "work" forever? I would have to maintain two separate code bases and update both of them on the regular to stay up-to-date with CSFloat's website changes.
English

@oranges0401 @Erroden_ Because it costs time and money. I don't see how punishing our paying users makes sense here.
I'd rather spend the little time I can into developing cool stuff for the people that are willing to support the project.
English

@MDLcsgo @Erroden_ You aren't wrong.
That would mean that every time we add a new market, the extension would get disabled for every single user and you would have to manually accept this single permission for the new market.
Please read my article about it: betterfloat.com/permissions
English

@rumscsgo @Erroden_ ..?
It's literally just a manifest change to add each new website without operating on a dangerous wildcard - max. 72h delay from commit -> live.
I don't want to call this being lazy, but it's just unnecessary when Extensions support multiple forms of wildcard host entries.
English

@DrexCS2 @kirincs Of course, check out Pricempire's API prices, which we've been using from the beginning: pricempire.com/api
English

@rumscsgo @DrexCS2 Yep thx for the clarification, tool is awesome still
and I understand the permission thing even though as you say probably understand I’m not loving the idea of it 🙏
kirin@kirincs
@DrexCS2 @wucksao I will say though I rudimentarily went through the git and couldn’t find anything particularly concerning + now also only allowed it to work on float so I am back onboard for now (also didn’t require me to log in like with my friend)
English











